I set a force discharge each evening, with FD cutoff at 15% so I have 5% left to use which sees me into the cheap rate window. However, instead of reverting to battery use at the end of this schedule, I am pulling from grid. This seemed to change when I was upgraded to 1.09 as it worked as intended previously. Having had a further upgrade today by my installer, the issue still persists.
I am in contact with Fox head office tech support, who are not aware of this problem, and tell me firmware logic hasn't changed.
If anyone experiencing the same could reply to this thread with your firmware versions, it may help them track down the problem.
Many thanks
Russell
H1-5.0-E-G2
EP11
Master 1.47
Slave 1.02
Manager 1.66
Battery 1.011
If at the end of your schedule, the battery is too cold, then it will pull from the grid to maintain a certain min temperature.
So make sure to read your battery temperature at this time to rule this out.
So make sure to read your battery temperature at this time to rule this out.
Yes noted, but I dont think this is the issue
As long as you test this later, then as said it rules it out.
Just to clarify for myself and others.
It worked when it the BMS was below v1.009 (typo in above 1.09)
Stopped working correctly when upgraded to v1.009
And error remains on v1.011
It is an issue that has been extensively reported by users in
viewtopic.php?p=10811
viewtopic.php?t=2503
Should be pretty easy to fix:
If 'Force Discharge selected' AND time is between 'Start' and 'End' time AND "SOC>FDSOC", proceed to use 'Force Discharge', otherwise revert to 'Self Use' mode.
But for some reason Fox thinks it is "otherwise revert to import from grid".
It has been reported that mode scheduler is getting an upgrade in Jan/Feb this year so hopefully it will get fixed when this gets released. The issue is definitely holding back recommendations for the Fox Brand in Australia.
viewtopic.php?p=10811
viewtopic.php?t=2503
Should be pretty easy to fix:
If 'Force Discharge selected' AND time is between 'Start' and 'End' time AND "SOC>FDSOC", proceed to use 'Force Discharge', otherwise revert to 'Self Use' mode.
But for some reason Fox thinks it is "otherwise revert to import from grid".
It has been reported that mode scheduler is getting an upgrade in Jan/Feb this year so hopefully it will get fixed when this gets released. The issue is definitely holding back recommendations for the Fox Brand in Australia.
Confirming I am also having this issue. Feb 2026. FoxCloud 2.0 Android App.
I still have this issue with my kh10/ep11 setup.
As it's getting sunny now in the UK, this is a real problem as forced discharge can't be relied upon to return to self use when the FD soc is met.
Has anyone heard of a fix to this yet ? Other than to start using home assistant....
As it's getting sunny now in the UK, this is a real problem as forced discharge can't be relied upon to return to self use when the FD soc is met.
Has anyone heard of a fix to this yet ? Other than to start using home assistant....
I logged a support ticket with FoxESS more than a week ago but not had a reply. Very poor support.
I have just discovered this issue also and have emailed UK support as their online support ticket errors at the captcha
Do they realise how massive a problem this is??!!? There is literally no point in having a peak time discharge schedule if it doesnt revert to self use when the SOC is reached. Because during this period any saving you are making is more than being cancelled out by the input grid premium tariff
They need to fix it urgently
Do they realise how massive a problem this is??!!? There is literally no point in having a peak time discharge schedule if it doesnt revert to self use when the SOC is reached. Because during this period any saving you are making is more than being cancelled out by the input grid premium tariff
They need to fix it urgently
I have disabled my force discharge schedule until they resolve it
Swift positive update from Fox UK support
"Dear Nicholas,
You are absolutely right. The recent update altered the discharge logic, and we have confirmed this with our R&D team.
They are currently fixing the software to restore the previous "Self-Use" behavior. A new version will be released very shortly to rectify this. Please keep an eye on your app for the upcoming update.
We apologize for the inconvenience and the issues you had with our online form.
Best regards,
Tristan"
"Dear Nicholas,
You are absolutely right. The recent update altered the discharge logic, and we have confirmed this with our R&D team.
They are currently fixing the software to restore the previous "Self-Use" behavior. A new version will be released very shortly to rectify this. Please keep an eye on your app for the upcoming update.
We apologize for the inconvenience and the issues you had with our online form.
Best regards,
Tristan"
I call this the 99% SoC bug
I use a schedule (in app or the energy stats app) to do a forced discharge and after it does not revert to self use or feed in priority
Starts pulling from the grid.
I check my settings in Quick settings and the min Soc is on 99%
ANOYING
Recently it won’t even do a forced discharge.
It’s like if a set a schedule to force discharge it does the opposite and starts charging my battery.
Very broken at the moment.
Raised this bug 2 weeks ago with fox and had no reply yet.
Just looked at data logger and it’s offered the upgrade to 2.09
Master 1.51
Slave 1.04
Manager 1.35
H1 5.0 E G2 WL
4xEP6
It’s 4th April 2026 btw
Why can I never see date people post. Am I being stupid. ANOYING
I use a schedule (in app or the energy stats app) to do a forced discharge and after it does not revert to self use or feed in priority
Starts pulling from the grid.
I check my settings in Quick settings and the min Soc is on 99%
ANOYING
Recently it won’t even do a forced discharge.
It’s like if a set a schedule to force discharge it does the opposite and starts charging my battery.
Very broken at the moment.
Raised this bug 2 weeks ago with fox and had no reply yet.
Just looked at data logger and it’s offered the upgrade to 2.09
Master 1.51
Slave 1.04
Manager 1.35
H1 5.0 E G2 WL
4xEP6
It’s 4th April 2026 btw
Why can I never see date people post. Am I being stupid. ANOYING
Not sure about your exact issue but the issue we are reporting is that after it hits the min soc for forced discharge it does not revert to self use and uses the grid. Fox are aware and working on a fix. I had a recent update to say they are testing the fix prior to release
Put simply
I have min Soc at 20%. I don’t change it
It jumps to 99% all on its own if I run a schedule
I have min Soc at 20%. I don’t change it
It jumps to 99% all on its own if I run a schedule
Yeah sounds like a different additional problem
System not reverting to self use mode after forced discharge mode limit reached (e.g. 50% SOC). This is a issue that should be fixed easily and quickly by Fox Ess
Yes but it hasn't to date. As I said they know about it and are deploying an app fix shortly. The fix is going through test at the moment according to Fox UK support