Thanks for additional efforts on Venus-OS development.
Since the issue I like to report is already known since years, but still exists (also in this beta), I like to memorize it again. Maybe there is a chance to get it fixed once.
Issue:
In case Venos-OS went in ESS#1 state over night and in the morning hours battery gets recharged by PV again, ESS setpoint is ignored. In installations I maintain, there is typicially a setpoint during daytime at -40W and during night at -10W. When battery fell to defined SOC min value and ESS#1 got activated during night and in the morning PV is back, Venus-OS does not allow to let flow all available PV power into battery.
Instead >300W get fed into grid constantly. Defined setpoint gets active again, when either
a) ESS#1 state is left due to higher SOC or
b) when set an lower SOC min value for a few seconds and returned to actual value after.
Interesting in scenario b) for most test cases setpoint was considered properly, although Venus-OSS returned into ESS#1 state again. So there seems to be a difference, if PV is present during ESS#1 state activation or not!
My setups:
- 3-phase installations with Multiplus-II
- PV either Fronius-based on AC-Out or in a mixed setup with Victron MPPTs
- BYD LVL batteries
- Venus OS >3.60 and 3.70 beta
- ESS mode: optimized without battery life (SOC min is inherited by PV foreast and set externally)