Until the app updates to this new look my system was working great. But now I'm getting power bills and its not wiring how it used to. I have 2x5kw hybrid inverters each with 22kw of batteries. We have cheap power from 11am till 4pm. I have force charge set for this period and grid charging enabled. It starts charging at 11 am as expected and finishes filling the batteries mid afternoon at some point. Horace as soon as the battery is full the related inverter turns off. Eventually both inverters turn off and no solar comes in and the system sits idle until 4pm then goes back to normal. Previously it would run the house from solar and export to grid. Now it just powers from the grid until 4pm hits. I've rebooted the inverters. Updated to newest firmware on everything and still no good. This is frustrating the he'll out of me as my bill went from 30$ a month to over 200!
I had my battery system installed in March 2026, and it has been operating exactly as you described from day one - PV is disabled after the battery is fully charged during "Force Charge". To maximise the benefits, I have to manually switch to “Self Use” or “Back-up” after the battery is fully charged each day, clearly not ideal.
I am unsure whether this is a firmware bug or intended behaviour by Fox. However, I cannot see any reason why PV should be disabled while I am purchasing power from the grid. It is good to know that the previous system strategy was more “clever.”
There are some similar discussions, but there does not appear to be an easy solution so far.
viewtopic.php?t=2660
I am unsure whether this is a firmware bug or intended behaviour by Fox. However, I cannot see any reason why PV should be disabled while I am purchasing power from the grid. It is good to know that the previous system strategy was more “clever.”
There are some similar discussions, but there does not appear to be an easy solution so far.
viewtopic.php?t=2660
Same here. Bloody annoying.
After the battery reaches the threshold I just want it to return to Self Use mode. Can't be that hard
After the battery reaches the threshold I just want it to return to Self Use mode. Can't be that hard
The other thing I just realized is that if I force discharge to a certain amount (say 6000kW), then the battery will not discharge more than that. So if usage happens to go higher than that amount, it will draw from grid for rest, even if more battery is available.
I'm not sure how it works with exporting limits.
I'm not sure how it works with exporting limits.
When you set a discharge rate, you are telling the Inverter to create xxxx W of AC power. (you must be running a BIG system to discharge 6000kWcjau wrote: ↑Wed May 20, 2026 2:55 pm The other thing I just realized is that if I force discharge to a certain amount (say 6000kW), then the battery will not discharge more than that. So if usage happens to go higher than that amount, it will draw from grid for rest, even if more battery is available.
I'm not sure how it works with exporting limits.
)If you have a 10kW Inverter with a 5kW export limit from your energy supplier, and you program a 6kW discharge...
Then if you are using 0.5kW of house load, then it can do this, and your export will remain at 5kW.
If your house load is 2kW, then your export will drop from 5kW down to 4kW.
If your house load is 5.5kW, then your export drops to 0kW.
If your house load is 8kW, then sadly only 6kW would be created from PV/Battery and you would draw 2kW from the grid.
Oops! Yes, 6kW. Imagine if I had 6000kW...!MaterialBarracuda48 wrote: ↑Wed May 20, 2026 4:56 pm (you must be running a BIG system to discharge 6000kW
Thanks for list about export limits. Helpful!
Luckily for me im a software developer and had enough of this issue so thought I would look into it further. Using the FoxESS Open APIS ive found a solution which just shows how absoluately stupid this issue is.
The work mode set by the new app is called "ForceCharge" which causes the issues I mentioned in my previous post. However, the previous work mode "ForceCharge(BAT)" is still listed on the work modes available.
Using the API I changed the API mode back to ForceCharge(BAT) which isnt available in the app of course and SHAZAAAM the old behaviour is back and all is working perfectly like it did before the app was messed with and all these problems started.
I wrote the code in PHP but happy to share with anyone who thinks is useful.
The work mode set by the new app is called "ForceCharge" which causes the issues I mentioned in my previous post. However, the previous work mode "ForceCharge(BAT)" is still listed on the work modes available.
Using the API I changed the API mode back to ForceCharge(BAT) which isnt available in the app of course and SHAZAAAM the old behaviour is back and all is working perfectly like it did before the app was messed with and all these problems started.
I wrote the code in PHP but happy to share with anyone who thinks is useful.
Attachments:
- Foxess .png (10.84 KiB) Viewed 120 times
So - this proves that it would be super easy for developers to add a toggle, or choice list, in the app, to allow users to select which mode to use once the battery reaches 100%
Great investigative work!!!! (From another app developer)
Great investigative work!!!! (From another app developer)
So what exactly is the different behaviour between "ForceCharge(BAT)" and "ForceCharge"?Roadkil wrote: ↑Sat May 23, 2026 8:25 am The work mode set by the new app is called "ForceCharge" which causes the issues I mentioned in my previous post. However, the previous work mode "ForceCharge(BAT)" is still listed on the work modes available.
...
I wrote the code in PHP but happy to share with anyone who thinks is useful.
Yes, please share the code. Thanks!