@WillCodeForCats could you help me with your integration please, I’ve now got it working ok with two batteries, B1 & B2.
B1 Energy Import and Export is a little hit and miss, as it keeps loosing the following sensors, and they flip back to “unknown”
sensor.solaredge_b1_energy_import
sensor.solaredge_b1_energy_export
If I reboot Home Assistant it reconnects to both these sensors and B1 Energy Export starts to count up again from 0.00kWh when I think it should remember where it was and carry on counting up like it does for B2 (which works fine) come the morning after the battery has had imports then the other sensor starts to count up again from 0.00kWh and all is back to normal. (apart from low counts for B1)
Is this due to SolarEdge or the integration please?
Energy counters for batteries are often an unreliable source. It’s documented in the Known Issues wiki page. There’s nothing I can do about it since it’s either a battery hardware or firmware problem. You can turn on the Allow Battery Energy to Reset option which would avoid having to restart or reload.
Energy counters for meters and inverters are reliable sources. It’s just batteries that aren’t.
I know, this integration doesn’t show the production data, needed for the energy dashboard .
There is a SolarEdge integration for this function.
It requires API key.
But only the master is connected with internet.
The API from the slave inverter is not accepted.
Thus I can’t show the production from the slave in the energy dashboard.
Maybe you are using a different integration if you aren’t seeing these sensors, but this integration solaredge-modbus-multi absolutely does support energy dashboard (always has).
Just one question.
Total power today, this month, ect is not available via modbus.
For this data I need to use the other integration with API key.
But only the master is reachable.
How can I retrieve this data from the slave unit?
Quick update. I’ve had the same error, connection unexpectedly closed, a few times now and it would appear that restarting HA seems to fix it. Does this suggest it’s a HA issue rather than the inverter?
It’s possible. How long is your HA install running for without updates or restarts before the error appeared? With as fast as HA releases updates, mine are never running for more than a month before the next major update so it’s not something I’ve seen personally.