Hi all, I have been using the app and the mode scheduler for a while and I could swear it wasn't working like today in force discharge mode.
Essentially, I do force discharge for around 40 minutes every night, cut at 30% with reserve on soc at 25%.
So it would normally go down fast to 30% unless very cold outside and then it would keep discharging up to 25%.
Noticed that now it does discharge up to 30% but then the battery goes idle and I import from the grid. As a test, I switched the mode to feedin and, as expected, it stopped importing from grid and discharging from the battery again.
I am not sure what is going at this point or how to resolve it without having to switch to something like home assistant.
Have you noticed the same in your systems?
Thank you!
Either you have had a recent firmware update, or Fox has changed some backend settings in the server that has actioned this change in system behaviour.
Several choices are available:
Stop doing the Force Discharges for now, test every few weeks to see if Fox has changed settings. (You may need a future FW update, but current FW's seem broken in this regard)
Monitor the system/add a Self-use/Feed-in schedule, might still draw some grid power if the timing is off.
Consider the Home Assistant route, but does cost a little money/time to setup.
Several choices are available:
Stop doing the Force Discharges for now, test every few weeks to see if Fox has changed settings. (You may need a future FW update, but current FW's seem broken in this regard)
Monitor the system/add a Self-use/Feed-in schedule, might still draw some grid power if the timing is off.
Consider the Home Assistant route, but does cost a little money/time to setup.
Same issues after latest fw upgrades.
Contacted Fox, the reply is
Hello, after our software upgrade, the logic has been optimized. During the force discharge period, once the SOC drops to the set minimum value, the system will no longer discharge.
If correct, this is a massive own goal. You export for revenue, then when you have charge left in the battery, you end up paying a premium price for import.
I will respond to them giving this view, but it needs users to respond to show them the negative impact it has.
This is the downside of no release notes, so users cannot make a valued judgement on upgrades.
Coming from a world of highly technical product development and implementation, these are complete schoolboy errors that drive user frustration and anger.
Contacted Fox, the reply is
Hello, after our software upgrade, the logic has been optimized. During the force discharge period, once the SOC drops to the set minimum value, the system will no longer discharge.
If correct, this is a massive own goal. You export for revenue, then when you have charge left in the battery, you end up paying a premium price for import.
I will respond to them giving this view, but it needs users to respond to show them the negative impact it has.
This is the downside of no release notes, so users cannot make a valued judgement on upgrades.
Coming from a world of highly technical product development and implementation, these are complete schoolboy errors that drive user frustration and anger.
Yes Fox appear to have changed the logic on KH and H1 (G2) in favour of taking from grid when FDSoC is met - I have heard there is a lot of push back on this in all markets - recommend that all affected email Fox service and ask for it to be returned to it's previous operation i.e. Self Use when FDSoC is met.CDubbs wrote: ↑Thu Jan 22, 2026 8:29 am Same issues after latest fw upgrades.
Contacted Fox, the reply is
Hello, after our software upgrade, the logic has been optimized. During the force discharge period, once the SOC drops to the set minimum value, the system will no longer discharge.
If correct, this is a massive own goal. You export for revenue, then when you have charge left in the battery, you end up paying a premium price for import.
I will respond to them giving this view, but it needs users to respond to show them the negative impact it has.
This is the downside of no release notes, so users cannot make a valued judgement on upgrades.
Coming from a world of highly technical product development and implementation, these are complete schoolboy errors that drive user frustration and anger.
Thanks Dave
Yes just responded to Fox, hopefully they will reverse the change
Yes just responded to Fox, hopefully they will reverse the change
Thank you for confirming, I believe this is a change in the software/backend, as I didn't have a firmware upgrade since last year and noticed this just a couple of weeks ago.
I raised a ticket to get the firmware(s) upgraded and I just got my datalogger upgraded, so that I can have updates every 5 seconds.
I will raise a new one as Dave suggested. Thanks all again.
I raised a ticket to get the firmware(s) upgraded and I just got my datalogger upgraded, so that I can have updates every 5 seconds.
I will raise a new one as Dave suggested. Thanks all again.
My FD and SOC was working fine until the upgrades for the 5 sec refresh this week
Then the issue occurred
My system was on install fw 1.47 from install in September 25
Then the issue occurred
My system was on install fw 1.47 from install in September 25
Interesting, I am now wondering if they did upgrade mine without me asking for it. I just checked and I am on 1.58 for Master and Manager but I thought I was on 1.4x prior than that. Also, I think that Master and Manager version were not exactly the same as they're now.
Battery is also on 1.011 now.
I asked to upgrade the datalogger and also the other firmwares today, they said that they put "on hold" my request for inverter and battery, but maybe that went through too. I will monitor tonight again!