Our KH7 inverter is set to Force Charge between 01:30 and 07:30.
Clearly a clock change is a significant event, and I monitor what happens. The change in the Autumn went fine, but the recent Spring change did not.
I checked and both yesterday and today the force charge started at 02:30 local time, and ended at 07:30. So, an odd mixture of behaviour.
Today I checked more thoroughly. The inverter clock time on the front panel is the correct (new) local time. The cloud web site shows the correct force charge start and end time - I believe those details are now no longer available in the "improved" app.
In an attempt to regain control, I have made a change to the force charge times to 01:45 to 07:15 in the cloud web site.
A post by Dave to explain what Fox do.
viewtopic.php?p=15300#p15300
viewtopic.php?p=15300#p15300
Sorry, but I don't think that explains what I am seeing.
The inverter clock is running Local Time. The force charge Start time is changed from the requested 01:30 to 02:30, but the end time is working as requested.
The inverter clock is running Local Time. The force charge Start time is changed from the requested 01:30 to 02:30, but the end time is working as requested.
Due to a quirk of fate, the time between 1am and 2am last Sunday morning did not exist. At 1am the clocks jump to 2am. Arguably the inverter should have kicked in at 2am BST, but I suspect this is a fallout of of how the change works. It could even be a display error in the app/browser.
Hi Nick,
I could buy that for Saturday night / Sunday morning. But it happened again last night Sunday night / Monday morning when there was most definitely a 01:30 a.m.!
Although curiously, looking more closely in response to your suggestion, it seems like the cloud wasn't recording from 00:56 to 02:07.
I don't think Fox have quite mastered the clock change.
I could buy that for Saturday night / Sunday morning. But it happened again last night Sunday night / Monday morning when there was most definitely a 01:30 a.m.!
Although curiously, looking more closely in response to your suggestion, it seems like the cloud wasn't recording from 00:56 to 02:07.
I don't think Fox have quite mastered the clock change.
I can only guess Fox didn't change your clock Sunday early hours. I have not even checked that mine has changed, and that my Home Assistant is aware also.
Best I take a look.
Best I take a look.
Latest update.
This morning (31st March), in response to a Force Charge setting of 01:45 - 07:15, our force charge actually started at 02:45 and ended at 07:15. Once more, there was a gap in the cloud recording from 00:55 to 01:55.
So, still odd behaviour. Why is the start time an hour late, but the end time honoured? Why is there a one hour gap in recording?
Is there actually anyone from Fox who can explain what is going on?
Why do we still not have the force charge settings in the App?
This morning (31st March), in response to a Force Charge setting of 01:45 - 07:15, our force charge actually started at 02:45 and ended at 07:15. Once more, there was a gap in the cloud recording from 00:55 to 01:55.
So, still odd behaviour. Why is the start time an hour late, but the end time honoured? Why is there a one hour gap in recording?
Is there actually anyone from Fox who can explain what is going on?
Why do we still not have the force charge settings in the App?
the only suggestion I have is for you to do a full shutdown / restart on your inverter in case the Manager has got stuck in a loop - a guide is listed here https://fox-ess.tech/hybrid-inverter-ac ... procedure/
As this is a community website, there are no Fox personnel that monitor these posts, the best way to get a response direct would be to email their service dept or raise a ticket for them to investogate.
As this is a community website, there are no Fox personnel that monitor these posts, the best way to get a response direct would be to email their service dept or raise a ticket for them to investogate.
I had a similar problem. Forced charge 00:30 to 05:30. Should have been only 4 hours at the clock change but ran for 5 hours to 06:30 BST (05:30 GMT) according to the cloud record and Octopus records. I have not dug any deeper yet.
Update on this.
I contacted the installer, who were stumped. They then raised a ticket with Fox, but nothing heard yet.
However, yesterday and today everything worked perfectly. This was the fist time since the clocks changed.
I contacted the installer, who were stumped. They then raised a ticket with Fox, but nothing heard yet.
However, yesterday and today everything worked perfectly. This was the fist time since the clocks changed.