I’m using Octopus Agile in the BetaVRM. Last night DESS decided the battery needed a little boost. So around the overnight minimum pricing two blocks of 15min charge appeared to get scheduled. So far so good.
The curious part is the last 5min of each slot seemed to overlap into the next hourly slot. Feels like it shouldn’t overlap a price/hour slot like this.
It could be caused by your VRM log interval that is set to 5 minutes, not showing the graph correctly.
The schedules that DESS inserts schedules for either 30 or 60 minutes and those are running from the half or whole hour.
Thanks, I had thought that, but then my smartmeter readings display appears to correlate - 4kW for approx 5min ~ 0.3kWh. I’m showing around 0.2kWh for the 04:00-04:30 slot:
|2024-09-06 01:30:00+01:00|0.020|12.250|0.240|
|2024-09-06 02:00:00+01:00|0.020|11.320|0.230|
|2024-09-06 02:30:00+01:00|0.870|10.450|9.090|
|2024-09-06 03:00:00+01:00|0.220|11.000|2.420|
|2024-09-06 03:30:00+01:00|0.850|11.000|9.350|
|2024-09-06 04:00:00+01:00|0.210|14.460|3.040|
|2024-09-06 04:30:00+01:00|0.010|14.080|0.140|
|2024-09-06 05:00:00+01:00|0.020|16.720|0.330|
Also curious if the schedules are for a complete half hour slot, why both charging peaks appear to start around 45minutes past the hour:
We do a recalculation of the schedules every 15 minutes, If the situation (SOC, consumption, forecasting) changes, it might consider inserting an updated schedule, causing the system to alter its behaviour.
Thanks for the explanation.
I’m still curious about the run-over into the next slot corroborated by the smartmeter readings. But have updated my VRM config to 1min updates and will check it next time.
