Hi all,
After running quite happily for about two weeks with forced charging between 11-2pm, and forced discharge from 6-8pm each night (I am on the ZeroHero Globird plan), the system suddenly decided to continue forced discharge after 8pm tonight!
I am at a complete loss as to how this could have changed, I definitely didn't do it, and it's not something that could be done by accident given the various series of key presses required to change the end time via the mobile app on my Android phone- which somehow had changed to 21:00 / 9pm.
Just calling this out in case someone else has a similar issue. I thought that maybe it could be related to some kind of time zone change or daylight saving adjustment (which obviously isn't applicable on this date), but the 18:00 / 6pm start time was the same, only the end time had shifted by an additional hour. Truly bizarre...
Perhaps a very poor April Fools joke...? But more likely just some weird bug...
The graphic on their website for this VPP shows export 6pm to 9pm, though I guess this is just for example purposes.
I can only assume that there was a need for power in the grid at this hour?
Given the VPP has control, this is probably why they demand the extra hour of export from you?
I can only assume that there was a need for power in the grid at this hour?
Given the VPP has control, this is probably why they demand the extra hour of export from you?
Hey MB48, I hadn't noticed their screen shot shows 6 to 9pm. That's interesting, I'll email them and see if they have expanded the timeframe.
However, I'm not signed up to their VPP and - as I understand it - they don't support my FoxESS inverter and/or battery systems anyhow. So 'vpp' updates by them seems to be very unlikely. Still, it's worth checking with them, I'll see what they say and report back. Cheers.
However, I'm not signed up to their VPP and - as I understand it - they don't support my FoxESS inverter and/or battery systems anyhow. So 'vpp' updates by them seems to be very unlikely. Still, it's worth checking with them, I'll see what they say and report back. Cheers.
The plot thickens then!
Well hopefully something can be found to solve why it changed.
Well hopefully something can be found to solve why it changed.
Just checked with Globird and A) I'm not part of their VPP, as I knew, and B) they don't have access to the FoxESS system to support it anyhow - both of which I was nearly 100% sure of prior to the call.
Simply impossible for me to have 'accidentally' pressed the series of buttons, etc., in some kind of 'pocket dial' situation, and I certainly didn't update it myself to 21:00, so...defect in that Android app version I guess, v2.2.5 - I think it was that version, as I just updated some apps this morning and it's now v2.2.6.
Simply impossible for me to have 'accidentally' pressed the series of buttons, etc., in some kind of 'pocket dial' situation, and I certainly didn't update it myself to 21:00, so...defect in that Android app version I guess, v2.2.5 - I think it was that version, as I just updated some apps this morning and it's now v2.2.6.
If you are just using one device, one version, then I have seen Fox change settings themselves.
Example, I have had force charge (KH7) change from 7000W to 6000W without input from me.
I can only guess the Fox database that stores/pushes these to your Inverter goes loopy from time to time.
It's a wait and see game for you, to just monitor it ahead of any significant event for a while.
Example, I have had force charge (KH7) change from 7000W to 6000W without input from me.
I can only guess the Fox database that stores/pushes these to your Inverter goes loopy from time to time.
It's a wait and see game for you, to just monitor it ahead of any significant event for a while.