"Operation Mode when soc target reached" if doing a forced discharge or forced charge once the soc target is reached in the window the user can select the remaining mode of operation in the schedule window ie "Self Use", "Backup/grid power", or "feed in priority".
Currently it looks like once soc target reached (for both forced charge and forced discharge) in the window it goes to backup mode i.e. feed from grid, users (not installers or agents) need the option to set the system to "Self Use", "Backup", or "feed in priority" for whatever time is left in the schedule window once the soc target is reached in the app and foxesscloud.
-------------------------------
So for example in a forced discharge window from 18:00-21:00 with discharge soc set to 40%, with self use set as the mode of operations where no time schedule exists (user has selected "operation mode when soc target reached = self use):
At 18:00 battery starts discharge at set level of 10kwh, soc target is reached at 20:00 then remainder of mode from 20:00-21:00 is set to self use, when 21:00 hits it goes to selfuse.
--------------------------------------
example a forced charge event from 11-2pm with soc target set to 100%, with self use set as the mode of operations when no time schedule exists, but if soc target reached during 11-2pm use wants to use grid power ie select backup mode/should rename to grid priority.
at 11:00 forced charge starts, battery reaches 100% soc at 12:00 then continues to draw from grid and not go to self use until 2pm.
-------------------------------------
Ive read its in firmware for months now since Jan 2026, if so what version from fox ess will this be available?
Yes, this is so important for users on Flow Power or Globird. When is this going to be implemented in the FW?
So this feature is now in foxess app v2.2.18, however to see this you need to be on version 1.69 master firmware for kh10. I do like the wording used "After Charging Cut-off:" and "After Discharging Cut-Off"
Problem is 1.69 master firmware version for kh10 introduces a 63amp grid import hard limit approx 14.5kw grid import, so 10kw to battery and 4.5kw to house loads max.
On Master Firmware version 1.67 KH10 the grid import limit wasn't restricted and it could be set to 80amps and do over 17.5kw grid import. So you can do 10kw battery charging and 7.5kw house loads at same time.
FOXESS Your are reading these please remove the restriction on the grid import limit on say version 1.71 so us single phase customers on 80amp+ grid circuit can make the most of the system!!!!!
Very interested as to why the 63amp grid limit was introduced in 1.69 on KH10 as the kh10 inverter installer settings state the kh10 can be setup with a max ac current of 78.3Amps and 18000 Kw. But the grid import limit isn't about the kh10 itself it is about thee grid load to the house (but every house will have a circuit breaker limiting power to hosue, even limited by the elctricity supplier), the kh10 is protected by its own inverter circuit breaker either 80amps or 63amps max depending on country.
Problem is 1.69 master firmware version for kh10 introduces a 63amp grid import hard limit approx 14.5kw grid import, so 10kw to battery and 4.5kw to house loads max.
On Master Firmware version 1.67 KH10 the grid import limit wasn't restricted and it could be set to 80amps and do over 17.5kw grid import. So you can do 10kw battery charging and 7.5kw house loads at same time.
FOXESS Your are reading these please remove the restriction on the grid import limit on say version 1.71 so us single phase customers on 80amp+ grid circuit can make the most of the system!!!!!
Very interested as to why the 63amp grid limit was introduced in 1.69 on KH10 as the kh10 inverter installer settings state the kh10 can be setup with a max ac current of 78.3Amps and 18000 Kw. But the grid import limit isn't about the kh10 itself it is about thee grid load to the house (but every house will have a circuit breaker limiting power to hosue, even limited by the elctricity supplier), the kh10 is protected by its own inverter circuit breaker either 80amps or 63amps max depending on country.
I have a kh10 anf upgraded the firmwareto 1.70. The After Charging Cut-off options I see are; Self-use, Feed-in Priority, Back Up, anf Standby. I've selected Standby but would like to know the difference between Standby and Back Up. Anyone know?
Hi, recent update these options are available on firmware 1.67 now (and i recommend staying on 1.67 if you have a main circuit breaker for your house above 63 Amps as 1.69/1.70 limit the grid import to 63 Amps).
For the functions:
-Standby - House load is covered by grid imports, and solar charges the battery when i tested and battery not full.
-Backup - This will priorities keeping the battery at the soc level set in the schedule window. If solar covers house load the rest goes to charging battery, unless battery is 100% then excess solar goes to grid. If solar doesn't cover house load the grid covers the remainder, keeping battery at the soc level set as a minimum.
-Self Use - This will priorities any solar generate to the house load and battery charging, before exporting to grid.
-Feed-In Priority-i didn't test but my understanding is it would prioritize sending solar to grid for feedin when above target soc.
For me when doing forced charge i use backup as the option and sometimes self use. I would never use Standby or feedin priority for my needs..
When doing a forced discharge i select self use as the option to avoid gid importing when target soc reached.
For the functions:
-Standby - House load is covered by grid imports, and solar charges the battery when i tested and battery not full.
-Backup - This will priorities keeping the battery at the soc level set in the schedule window. If solar covers house load the rest goes to charging battery, unless battery is 100% then excess solar goes to grid. If solar doesn't cover house load the grid covers the remainder, keeping battery at the soc level set as a minimum.
-Self Use - This will priorities any solar generate to the house load and battery charging, before exporting to grid.
-Feed-In Priority-i didn't test but my understanding is it would prioritize sending solar to grid for feedin when above target soc.
For me when doing forced charge i use backup as the option and sometimes self use. I would never use Standby or feedin priority for my needs..
When doing a forced discharge i select self use as the option to avoid gid importing when target soc reached.
Standby seems to behave exactly the same as Backup except the inverter is not active and does not consume and load (~150W). Why would you not use Standby?
I posted a detailed answer from Google Gemini but didn't seem to come through. Trying again.
1. Back Up Mode
How it behaves: Once the battery reaches the target SOC, the inverter stops charging/discharging the battery and holds it at that charge level.
Power source: Your home’s electrical loads are supplied directly by the grid (or PV generation if available), while keeping the inverter actively engaged and ready to instantly supply backup power if the grid drops out.
Best used for: When you want to preserve your battery's stored energy (e.g., during high dynamic tariff periods or peak rates) while ensuring maximum reliability and instant UPS/backup coverage.
2. Standby Mode
How it behaves: Once the target SOC is reached, the inverter disables its main power conversion stages and drops into an idle / low-power sleep state.
Power source: The grid continues to supply house loads via bypass, but because the inverter’s internal electronics go to sleep, the inverter's own internal self-consumption (tare loss) drops to near 0W.
Best used for: Minimizing self-consumption overhead when you know you just want the system sitting idle until the scheduled window finishes or solar production resumes.
1. Back Up Mode
How it behaves: Once the battery reaches the target SOC, the inverter stops charging/discharging the battery and holds it at that charge level.
Power source: Your home’s electrical loads are supplied directly by the grid (or PV generation if available), while keeping the inverter actively engaged and ready to instantly supply backup power if the grid drops out.
Best used for: When you want to preserve your battery's stored energy (e.g., during high dynamic tariff periods or peak rates) while ensuring maximum reliability and instant UPS/backup coverage.
2. Standby Mode
How it behaves: Once the target SOC is reached, the inverter disables its main power conversion stages and drops into an idle / low-power sleep state.
Power source: The grid continues to supply house loads via bypass, but because the inverter’s internal electronics go to sleep, the inverter's own internal self-consumption (tare loss) drops to near 0W.
Best used for: Minimizing self-consumption overhead when you know you just want the system sitting idle until the scheduled window finishes or solar production resumes.
Quick Comparison Summary
Option Household Loads Powered By Inverter Status Internal Energy Loss (Tare Loss)
Back Up Grid / PV Active & monitoring Normal (~100–150W baseline draw)
Standby Grid / PV Idle / Sleep Extremely Low (~0W draw)
Option Household Loads Powered By Inverter Status Internal Energy Loss (Tare Loss)
Back Up Grid / PV Active & monitoring Normal (~100–150W baseline draw)
Standby Grid / PV Idle / Sleep Extremely Low (~0W draw)
I didn't want to use grid import if not required and had sufficient solar.
If you are setting a force charge rule to go to 100% then Standby/Backup might be very similar.
For the current provider i have my rules set to smaller windows to do forced charge for 30min to a target soc level, but if my soc level is already achieved from solar then i wont be drawing in any grid power. Only draw grid power when my soc level is below target soc for that scheduled window.
If i were on a different provider I might use standby if i am trying to get to 100% soc level and keep it like that for the entire schedule window.
You should test them out and see what works for your specific situation.
If you are setting a force charge rule to go to 100% then Standby/Backup might be very similar.
For the current provider i have my rules set to smaller windows to do forced charge for 30min to a target soc level, but if my soc level is already achieved from solar then i wont be drawing in any grid power. Only draw grid power when my soc level is below target soc for that scheduled window.
If i were on a different provider I might use standby if i am trying to get to 100% soc level and keep it like that for the entire schedule window.
You should test them out and see what works for your specific situation.
Understood. I am with Ovo and have free electricity between 11am-2pm. If I reach 100% before 2pm I want to use the Grid and PV for my house load.FoxDownUnder wrote: ↑Tue Jul 28, 2026 6:44 am I didn't want to use grid import if not required and had sufficient solar.
If you are setting a force charge rule to go to 100% then Standby/Backup might be very similar.
For the current provider i have my rules set to smaller windows to do forced charge for 30min to a target soc level, but if my soc level is already achieved from solar then i wont be drawing in any grid power. Only draw grid power when my soc level is below target soc for that scheduled window.
If i were on a different provider I might use standby if i am trying to get to 100% soc level and keep it like that for the entire schedule window.
You should test them out and see what works for your specific situation.