Switched from cloud api integration to solaredge-modbus-multi integration #647
Answered
by
peterlindeman
peterlindeman
asked this question in
Q&A
Replies: 2 comments
-
You can change the units of the sensor, but internally it is native as watt-hours so there shouldn't be a difference in how the energy dashboard tracks it. ![]() |
Beta Was this translation helpful? Give feedback.
0 replies
-
I have fixed it by deleting the old cloud API integration and after that renamed the new modbus sensor to the name the old sensor of the cloud API was using. It’s working now including al history 👍🏻
|
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
peterlindeman
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Today I enabled modbus over tcp in my inverter and I have installed the latest release of this integration. So far so good. I get all necessary values in HA but I'm strugling with the Energy dashboard configuration.
For the cloud api integration I got the sensor sensor.solaredge_lifetime_energy which is configured in the energy dashboard for some years now so a lot of history I do not want to lose. With the modbus integration I will get the sensor sensor.solaredge_ac_energy_kwh which has the same info only in kWh where the cloud sensor is stored in Wh
When I replace the sensor in the energy dashboard configuration I lose my history.
What is the correct way to switch from the cloud integration to the modbus integration. Tried to find any information about it but cannot find it. Hopefully somebody knows the solution.
Thanks,
Peter
Beta Was this translation helpful? Give feedback.
All reactions