Clocks went forward - or did they ?

[twowheelsgood]

My recharge time on Octopus is 0200 for an hour.

My discharge time is from 1600 until the battery hits its force discharge minimum.

The App confirms this - nothing has changed there.

The front panel of the inverter shows the time as 0807 so that appears to have changed

But I noticed this morning that the recharge started at 0300 instead of 0200 - luckily enough time to do its thing inside the cheap period.

Any ideas what is causing the recharge start time to be delayed by an hour ?

Update @ 1619hrs - the standard discharge to Octopus should have started at 1600hrs. It didnt start despite 1600hrs being passed on the App.

It started the discharge at 1700hrs - an hour later than it should. It terminated at the right force discharge minimum and started to charge againa s the sun was out.

Somewhere buried away in the system the clocks have not moved forward.

[reef]

This has caught me out before.

I usually force charge and then run from grid when the battery is full from 23:30 to 5:30 (Octopus Intelligent Go). I deliberately set this to 23:30 to 04:30 yesterday evening in anticipation of it not changing and sure enough it ran until 05:30 - an hour longer than it should have.

Hopefully tonight it'll start at 23:30 as it's supposed to and not 00:30!

[WyndStryke]

Somewhere buried away in the system the clocks have not moved forward.

I think (not 100% sure) that the mode scheduler is driven from the cloud, not locally on the inverter. So if the time on the Fox cloud hasn't been adjusted, then it'll be off, regardless of what the inverter's time is set to.

[twowheelsgood]

Thank you - it returned to normal this morning.