So, here is a quite nice example of the “OVERRIDE_SELFCONSUME_ACCEPT_CHARGE” - Behaviour:
This morning, the system concluded, that there will be a high consumption and little solar. So, according to the expectation it created a schedule to MAINTAIN the target soc throughout the day, with regards to expensive prices at the evening.
This is a totally fine “roadmap” with regards to the forecast:
However, we just had a “sunny moment”, lasting about 45 minutes. The target-Soc was scheduled for 34%, while there have been peaks upto 10kW solar:
The original implementation would have gone into “battery-idle-mode” because the targetsoc says 34% (or even discharge, when exceeded)!:
So, the OVERRIDE_SELFCONSUME_ACCEPT_CHARGE modification kicked in, just setting the system into regular ESS mode, causing it to do, what an ESS is supposed to do: Charge the Battery!:
After the 45 minute period, the DESS schedule was still sitting at 34%, while the override managed to push the battery upto 47% and quite ahead of plan:
finally, we absorbed a total of 3.75 kWh (13% SoC) that would have endet up beeing feed-in to the grid with the default behaviour:
The original behaviour is - just as I write - causing new posts over here:
The original implemention does not obey current solar and/or consumption values. If the roadmap says “targetSoc” - it sticks to that, wasting (selling) energy that could charge the battery. While this might be usefull for Trade-Mode to keep the soc precisely at the target_soc - I can’t see any benefits justifying this behaviour in Green Mode.