Hi,
I setup ESS
with a self-written python script to get the grid-powermeter via SML/IR-sensor from my gridmeter of the local power-supplier. I will provide this script as soon as the appropriate quality level is achieved.
I have question regarding the best DBUS-behaviour in case on gridmeter-communication failure during normal operation.
I saw that it's dangerous to keep the last known power-value, because ESS will escalate:
- in case of a last positive power-value, ESS will increasingly discharge the battery
- in case of a last negative power-value, ESS will increasingly charge the battery via grid-power
So I decided to erase the gridmeter vom DBUS via stoping the script.
But this causes, after about 1 min, the DC-PV-charger (Smartsolar) from producing power. Mulitpus changes to Passthru.
Why this? My understanding is.....
As long as the battery is not fully loaded, DC-PV-charger should load the battery regardless of the unknown AC-power-status. As soon as the battery is charged, the PV-charger-power could be transformed into AC-power, supplying the unknown AD-power-status.
Ater reestablishing the gridmeter-communication, ESS turns to probably behaviour within 30 seconds.
What could be the best behaviour of my gridmeter-script during communication-error?
Could anybody test the system-behaviour in case of an official victron powermeter? Please unplug it from the system and watch dbus-spy on the console.
Bye
Alex
