Closed tuxianerDE closed 7 months ago
That is indeed a interesting case. A short drop in demand to below zero of course led to the decision to stop the hub from contributing. Thus the decision to provide 0 contribution at night will stop the inverter (no power input to inverter).
Though in your case 10s later the demand was back (rapid rise even) which immediately triggered output from battery again and turned on the inverter as well and normal operation continued?
I observed the inverter stall - was out of town - connected via VPN and quickly switched to stable to keep the night running.
When I checked the OpenDTU UI the system was stalling, so all I saw was the WR/Hub did not pick it up directly
Issue was not observed anymore
I observed that during a night run, and a drop in load (dryer finished). The skript determined the new limit.
It set the HUB to 0 and the INV to 40W. Problem is this switched off the inverter. Ideally if such a situation occurs (reason is why because there is still "ground" load). The minimum on battery should be 30W (as the hub requires these 30/60/90 steps) This should only be the case if it is not day or during the offset times, thus only during night time.
solarFlow-stalled.txt