FoxESS H1(G2) not charging or discharging on schedule?
The G2 generation is a better-defined FoxCloud 2.0 target than legacy H1/AC1. Start with homeowner-visible mode and SOC checks before treating the behaviour as a hardware fault.
1. Confirm the label says H1(G2) or AC1(G2)
FoxESS Australia lists H1/AC1 and H1(G2)/AC1(G2) as distinct generations. Do not apply this page to an older H1/AC1 solely because the brand and kW rating look similar.
2. Check Mode Scheduler
FoxCloud 2.0 documents custom time periods with Forced Charge and Forced Discharge. Forced Charge uses PV and grid power; Forced Discharge uses PV and battery power to supply loads and may export subject to site constraints.
3. Check the remaining-time mode
Outside scheduled blocks, FoxCloud falls back to the selected Remaining Time Work Mode. A correct overnight charge window can therefore be followed by behaviour that looks very different during unscheduled hours.
4. Check minimum/threshold SOC
Minimum SOC and peak-shaving threshold logic can stop discharge while the app still shows stored energy.
5. Check firmware/app generation
FoxESS's 2026 FoxCloud manual specifically documents in-app firmware upgrading for H1-G2. If the expected controls are missing, establish the installed firmware/app state before assuming the feature is unavailable.