Force Discharge issue - reverting to grid not battery at end of schedule

[BigNickUK]

Since having this issue with grid import after a forced discharge period back in Jan/Feb time, seems my kh10 has stopped having this issue at some point in may 2026. I've noticed a few times over the last couple of weeks it hits the fdsoc % and whilst foxapp 2 still shows it's in force discharge mode, it starts to recharge the battery using solar just like it was in self use mode. Much as it always did last year before I updated the sw.
Has anyone else noticed this ?
I have a kh10 running master 1.60, slave 1.02 and manager 1.58.
I haven't updated it since Jan/Feb time but all of a sudden come may, it seems to be working again and no longer importing from grid once fdsoc % met.
Like some kind of bizarre magic ? Did anyone also experience this, and if so any idea what made it change ?

This post is about a different issue

[NickJH]

For the H1 Gen2, Master v1.55 and Manager 1.73 have now been released. I've installed them and when doing a forced discharge, when the FDSoC is reached, it still switches Home to Grid Import and Solar to Charging. Not good.

[BigNickUK]

I thought the issue was a Fox Cloud app issue. When they told me it was in testing

[NickJH]

When I described the issue to them, the reply I got was:

OK i got what you mean, for current logic ,it does not support like you described, but in the next firmware we will achieve this

The firmware will be released around mid of Apri

(and yes, the l is missing from April) Anyway, to me this is not an app issue, but who knows?

[mikeincairns]

[quote
But each schedule window should have the option "Mode When Complete Before Window End" - "Self Use" or Backup" Would fix this for every fox ess user
[/quote]

YES PLEASE PLEASE PLEASE.
Such a simple fix.

[NickJH]

Shouldn't it just revert to the default mode?

[FoxDownUnder]

To fix this for every and a day it should allow user to pick for the reminder of the window once soc is reached as some users may have different use cases where for the window they may want self use (ie solar->battery->grid), backup(ie grid->solar->battery) or feed in priority ( is this battery->solar->grid? for home load with solar prioritized for feed in) . Plus this would mean moving forward no developer could change it again on the entire user base and be in this situation again in a few years.

For example if default mode is self use, but user has selected force charge between 11am-2pm and it reaches 100%soc at midday they may wish for the rest of the window, midday to 2pm to draw from grid for home load (i assume this is how existing backup mode works) rather than self use, because they are on a free energy plan for 3hrs in middle of day and don't want to draw down on the battery.

For forced discharge most users want it to go to self use once soc is reached as they are discharging battery to get high feed in and not use grid power, Or they are getting rid of battery charge due to high solar forecast ahead. However having the option for end users means it cant be removed or changed by a developer in the future and users have clear control of this.

It is ridiculous this has been going on for almost 6 mths fox where are you with this????.

[mikeincairns]

You have articulated the problem and solution elegantly.
Yes - it is ridiculous that Fox have not listened to customers. I personally reached out to their global and Australian help desks and was fobbed off as a non-issue.
Meanwhile, I have been paying for grid electricity every day for a few hours, when the sun is shining brightly. Not happy.

[Markvreug69]

same happened to me last night at 8.30pm for last half hour as it hit bottom limit of feedin for battery it convered to grid and consumed average 45w up to 70w for half hour then went back to feeding in around 25w to keep line alive.Same happened to my son , his whole home system is designed by ai pro and persifically states not to during those three hours but still did tast two nights.

[zach]

It's now June, well over 6 months since this critical feature was broken, absolutely insane that this is still not fixed.

[StuFox]

Been following this issue, silently waiting for it to be fixed.
Finally decided to make an account just to add that this is bonkers for a large company to not have a fix for it yet.
Given this is how it used to work, and users have detailed perfect resolutions on here, there has to be a hidden reason why they have not implemented any fix yet.

[SoFather]

I don’t get this issue.
I’m on BMS 1.012