H1-Gen2 Manager V1.61
It's been reported that force charging disappears from the mode scheduler after installing this update. Worth avoiding.
Site Admin
Community Admin / FoxESS Elite Professional
Did I help you? Feel free to leave me a tip
Book a zoom meeting for remote consultancy or help
Switch to Octopus and earn £50
Get a heatpump from Octopus and earn £100
Subscribe to my YouTube channel
Fox ESS Tri Inverter Installation
2 x KH Hybird Inverters (Parallel Mode)
1 x H1 Gen1
24 x HV2600 (62.4kWh)
32 x 490w across 4 arrays
Dual Tesla Household
Heatpump & Low Carbon Housebuild
Did I help you? Feel free to leave me a tip Book a zoom meeting for remote consultancy or help Switch to Octopus and earn £50 Get a heatpump from Octopus and earn £100 Subscribe to my YouTube channelFox ESS Tri Inverter Installation
2 x KH Hybird Inverters (Parallel Mode)
1 x H1 Gen1
24 x HV2600 (62.4kWh)
32 x 490w across 4 arrays
Dual Tesla Household
Heatpump & Low Carbon Housebuild
I just had the firmware updated yesterday when my installer came for some other work, and I'm somewhat disappointed that I can not set a force discharge.. and even the force charge doesn't show properly (even though, thankfully, it does charge). If it didn't, I'd be totally screwed as there's not enough solar right now to charge the battery fully.
Working Mode just shows a mess now?
Will there be a fix and how do I go about getting it installed? Do I have to get the installer to request it or can I? And if I can get it rolled back, does that introduce any issues?
I also get a 44098 Write Error if I try and adjust the two legacy force time charge times.
Working Mode just shows a mess now?
- Screenshot 2025-10-23 at 01.04.13.png (18.79 KiB) Viewed 23066 times
I also get a 44098 Write Error if I try and adjust the two legacy force time charge times.
Frustrating I know, there will be a fix (I would imagine soon as Fox are well aware of this) but at the moment the only option is to roll the firmware back to a previous version - your installer will be able to do that remotely as the old version is still available.
The old charge periods will still work but cannot be used at the same time with scheduler enabled, that’s what is causing the 44098 error - disable scheduler and they will work.
The old charge periods will still work but cannot be used at the same time with scheduler enabled, that’s what is causing the 44098 error - disable scheduler and they will work.
H1G2 Manager 1.62/ Master 1.45 still sees this issue using the web page BUT in the app the entry lines that show as "unknown" now show as ForceCharge(AC), ForceCharge(BAT), ForceDischarge(AC) and ForceDischarge(BAT). The settings page (but not the quick settings page) in the installer's web app show these as well.
There is no description of the difference between the AC and BAT settings but yesterday using ForceCharge(BAT) allowed solar to power the load once the battery charge reached 100% rather than shutting down as seen previously.
FoxESS really need to work harder at keeping the web app up to date with inverter firmware changes and providing meaningful user instructions rather than leaving us to work things out for ourselves.
There is no description of the difference between the AC and BAT settings but yesterday using ForceCharge(BAT) allowed solar to power the load once the battery charge reached 100% rather than shutting down as seen previously.
FoxESS really need to work harder at keeping the web app up to date with inverter firmware changes and providing meaningful user instructions rather than leaving us to work things out for ourselves.
H1-3.7-E-G2, EP11-H and 6Kw solar
55.5N 3.7W
55.5N 3.7W
"There is no description of the difference between the AC and BAT settings but yesterday using ForceCharge(BAT) allowed solar to power the load once the battery charge reached 100% rather than shutting down as seen previously."
This is good news at least - I've had this issue open with Fox ESS for some time - my post of Feb 11th 2025 in this thread refers.... viewtopic.php?t=917
An unsolicited "push" of 1.62 to my inverter 2 weeks ago "bricked" it though (warranty replacement being fitted today) : viewtopic.php?t=2386
It was previously on :
Fox ESS H1-5.0-E-G2 Firmware - Master: 1.31 Slave: 1.03 Manager: 1.48
Fox ESS ESC 2900-H4 Cube Battery - Master plus 3 Slaves - All V2 - 11.52kWh - Firmware - Master: 2.002 All Slaves : 1.13
I'll be asking my installer to push all of the updates to the new inverter and the existing battery stack before he leaves....
This is good news at least - I've had this issue open with Fox ESS for some time - my post of Feb 11th 2025 in this thread refers.... viewtopic.php?t=917
An unsolicited "push" of 1.62 to my inverter 2 weeks ago "bricked" it though (warranty replacement being fitted today) : viewtopic.php?t=2386
It was previously on :
Fox ESS H1-5.0-E-G2 Firmware - Master: 1.31 Slave: 1.03 Manager: 1.48
Fox ESS ESC 2900-H4 Cube Battery - Master plus 3 Slaves - All V2 - 11.52kWh - Firmware - Master: 2.002 All Slaves : 1.13
I'll be asking my installer to push all of the updates to the new inverter and the existing battery stack before he leaves....
Fox ESS H1-6.0-E-G2-WL Firmware - Master: 1.40 Slave: 1.04 Manager: 1.26 Datalogger (internal wifi) : 2.06
Fox ESS ESC 2900-H4 Cube Battery - Master plus 3 Slaves - All V2 - 11.52kWh Firmware - Master: 2.002 All Slaves : 1.13
430w Jinko JKM430N-54HL4R-B all black panels (2 strings of 6 - SW facing) - 5.16 kWp
Myenergi Zappi
Octopus Intelligent Go tariff
Fox ESS Inverter firmware as suppled with replacement inverter/awaiting update Nov 2025
Fox ESS Battery Firmware updates applied Feb 2025
Fox ESS ESC 2900-H4 Cube Battery - Master plus 3 Slaves - All V2 - 11.52kWh Firmware - Master: 2.002 All Slaves : 1.13
430w Jinko JKM430N-54HL4R-B all black panels (2 strings of 6 - SW facing) - 5.16 kWp
Myenergi Zappi
Octopus Intelligent Go tariff
Fox ESS Inverter firmware as suppled with replacement inverter/awaiting update Nov 2025
Fox ESS Battery Firmware updates applied Feb 2025
Is there any update on a new firmware? It seems V1.61 is still the latest so maybe 1.62 was pulled (if it bricked a device, I'm certainly glad that's the case). I did ask my installer and they said I had the latest.
I opted not to roll back the firmware as it seemed like that would also cause hassle, and I was hoping they'd have fixed things by now.
Right now I'm experiencing an issue with force discharging, which I am sure isn't working as it used to. I can at least change the settings now, so I wonder if some of the V1.61 issues have been fixed by way of the website and app being updated?
Anyway, I've set a discharge from around 2200 to 2330 (before my rates drop to 7p and I force charge the battery) to export at a rate of 2.5kWh from the battery - but to stop discharging at 25% (this way, if the battery was already low, it wouldn't discharge any more to reach 10% and make the house start to draw from the grid and defeat the whole object).
When it's actually discharging, it exports whatever remains after supplying the required house load - as I want.
But when it reaches the limit, it stops discharging the battery entirely. It doesn't end the schedule, but rather just makes the house draw from the grid until the scheduled time elapses.
I am fairly certain this didn't happen before? I thought it returned to self use, so the home still used the battery?
Am I setting something wrong? Is this down to the firmware or have I got the settings wrong?
Currently I've tried MinSoC on grid 25%, Max SoC 100%, FDSOC 25% but I've had MinSoC at 10% and FDSOC at 25% before with no difference.
The Work Mode settings seem to have changed again, with the drop down list now being:
Back Up
Feed-In Priority
Force Charge
--
Force Discharge
--
Self-Use
And, yes, the '--' options are each selectable!! Not that I dare try.
Am I right in that Feed-In Priority only applies to PV generation? Or would that be what I need to set?
Advice most appreciated.
I opted not to roll back the firmware as it seemed like that would also cause hassle, and I was hoping they'd have fixed things by now.
Right now I'm experiencing an issue with force discharging, which I am sure isn't working as it used to. I can at least change the settings now, so I wonder if some of the V1.61 issues have been fixed by way of the website and app being updated?
Anyway, I've set a discharge from around 2200 to 2330 (before my rates drop to 7p and I force charge the battery) to export at a rate of 2.5kWh from the battery - but to stop discharging at 25% (this way, if the battery was already low, it wouldn't discharge any more to reach 10% and make the house start to draw from the grid and defeat the whole object).
When it's actually discharging, it exports whatever remains after supplying the required house load - as I want.
But when it reaches the limit, it stops discharging the battery entirely. It doesn't end the schedule, but rather just makes the house draw from the grid until the scheduled time elapses.
I am fairly certain this didn't happen before? I thought it returned to self use, so the home still used the battery?
Am I setting something wrong? Is this down to the firmware or have I got the settings wrong?
Currently I've tried MinSoC on grid 25%, Max SoC 100%, FDSOC 25% but I've had MinSoC at 10% and FDSOC at 25% before with no difference.
The Work Mode settings seem to have changed again, with the drop down list now being:
Back Up
Feed-In Priority
Force Charge
--
Force Discharge
--
Self-Use
And, yes, the '--' options are each selectable!! Not that I dare try.
Am I right in that Feed-In Priority only applies to PV generation? Or would that be what I need to set?
Advice most appreciated.