I’m observing on the “battery balance” day that the logic is too stupid to recongize that in previous days of sun it already reached 100% for several hours, and on the balance day again full sun was forecasted, yet it topped up in the morning from the grid. This costs me unnecessary EUR 1,50.
Can the “battery balance” logic be improved to include the sun forecast?
There is a related thread https://community.victronenergy.com/t/battery-balancing-is-scheduled-for-this-day with some suggestions.
WTF - why did DESS charge my battery at night?
My 40kWh battery was at 85% and the day PV forecast was 38 - 47 kW.
DESS now will be turned off for real. I will need to seek for a more sensible replacement (either EOS, own code, or EVCC with the upcoming optimizer). The logic I need in the winter is simple: charge between 0 and 5 AM the amount to fill the battery (limited to the daily consumption forecast) minus the PV forecast.
It would be useful to have:
Then perhaps someone can offer some help.
Even with DESS switched off, the ESS assistant still enforces the minimum SoC, so if the reported SoC dipped below that limit (a BMS recalculation or drift will do it), the MultiPlus pulls from the grid to bring it back up — DESS on or off. I’d check two things: first, whether any scheduled charging windows are still active in VRM or on the GX device, and second, what the ESS minimum SoC is set to versus the SoC shown at the moment the charging kicked in. A screenshot of the SoC curve around the charge event usually makes the trigger obvious.
Thanks @Buzzy and @mikaelkorhonen for your ideas. My minimum SOC is set to 20%, the battery had only reached 65% - see screenshot:
I had switched DESS off for more than 2 days, since as in this thread beginning I noticed such unexpected charging (first time it was during “battery balancing”, this time not).
No scheduled charging. NodeRed deactivated for months.
I have some connected services reading the GX modbus: EVCC and HomeAssistant, but no configuration there yet to command the battery.
So, I have no clue what triggered the charging, especially with the DESS off.
your active soc limit changed to 100% for that time. (You should be able to check that in the advanced graphs as well) Any script where you are changing the min soc that may have had a malfunction? 
Hi @dognose, my ESS is set to “Optimized without BatteryLife”, yet in the advance graphs I only found a hint that “BL Disabled (Auto-recharge)” was active, what could have triggered this? I have no scripts running.
