Hello all
The clocks went back in the UK at 2am on 25th October.
So at 2am the clocks go back to 1am.
I have a forced charge set for 2:01am until 4:59am to make use of the low rate Octopus tariff.
But Looking at my analysis chart online it looks like my system started charging at 1am. You can see how the SoC actually tracks back at 2am and then increases as my forced charge begins.
But why did it start an hour early if the clocks go back at 2am, one minute before it is due to force charge?
As you can see from my Octopus account they have charged me for the 1am to 2am forced charge!
Any help would be appreciated.
The key question is whether the inverter's own clock followed the change. If the unit doesn't apply the DST shift, a scheduled 02:01 start can fire at 01:00 local, which would explain both the early charging and the Octopus charge for that hour. Check the inverter display time against your phone at the same moment, and if it's an hour off, adjust the timezone or DST setting rather than the schedule. Worth confirming whether the forced-charge window is stored as local time or UTC in the portal too.
All clocks are correct.
The settings say the system uses London Time.
Screenshot below shows that the system recorded the SoC dropping to 30% at 1:54 am (British Summer Time).
The SoC also is also seen climbing to 59% at 1:54 am (Greenwhich Mean Time).
To me this shows that the system did change it's clock at 2am (BST) to 1am (GMT).
But . . .
If the clock did change as described above why did it start the force charge at 1am (GMT) when the schedule is set for 2:01am??
The settings say the system uses London Time.
Screenshot below shows that the system recorded the SoC dropping to 30% at 1:54 am (British Summer Time).
The SoC also is also seen climbing to 59% at 1:54 am (Greenwhich Mean Time).
To me this shows that the system did change it's clock at 2am (BST) to 1am (GMT).
But . . .
If the clock did change as described above why did it start the force charge at 1am (GMT) when the schedule is set for 2:01am??
Attachments:
Hi All
just an update following a conversation with Fox support.
basically they have said to avoid any planned schedules on or around 2am when the clocks change.
just an update following a conversation with Fox support.
basically they have said to avoid any planned schedules on or around 2am when the clocks change.
I do think this happens when the clocks change back and forth. Perhaps IIRC, it is down to when they process the schedules on their back end. Maybe they need to stagger it so that it is not swamped at 00:00 each day.
One thing I have seen, is Octopus Agile change rates usually at 4pm daily, but the Fox system doesn't query it until hours later.
One thing I have seen, is Octopus Agile change rates usually at 4pm daily, but the Fox system doesn't query it until hours later.