Just had an Agile charge slot actioned with battery SOC = 90% and SOC test set to 75% It should have been skipped WW log [URL=https://imgapi.wonderwatt.com/i/B0iheek.png][IMG]https://imgapi.wonderwatt.com/i/B0iheek.png[/IMG][/URL] WW Active Agile Window [URL=https://imgapi.wonderwatt.com/i/bOThPuH.png][IMG]https://imgapi.wonderwatt.com/i/bOThPuHh.png[/IMG][/URL] neighboring-volume

@"johalareewi"#p9167 Ah, this is an edge case issue. Will look into this and get a fix out.

@"johalareewi"#p9169 This has been fixed now btw.

Charge slot fired off but SOC was above set limit

johalareewi

Just had an Agile charge slot actioned with battery SOC = 90% and SOC test set to 75%
It should have been skipped

WW log

WW Active Agile Window

neighboring-volume

admin

johalareewi Hmm. From the logs we can see that the SOC less than condition was 101, which is why it was sent.

johalareewi

admin
Strange because the 101% window was deactivated in the morning and replaced by the one with 75%.
When the 75% window was activated, I rechecked the Agile scheduler to make sure everything was in place and it looked fine.

admin

johalareewi Ah, this is an edge case issue. Will look into this and get a fix out.

johalareewi

I did wonder if there was some data carry over when I switched the windows.

I have 2 similar windows from 13:30 to 16:00 one has SOC test 75% and 2 slots required.
The other has SOC test 101% 0 slots required.

Usually, the 75% window is active to make sure there is enough battery to get through the peak slots into the evening. If Agile prices are low, I flip to the 101% window and manually select slots to do charge/export sequencing, or to stop a full battery discharging and force solar to export/use the grid.
Then next morning, if Agile prices are back up, I flip back to 75% window,

admin

johalareewi This has been fixed now btw.