using OpenAPI v3/device/schedule/enable
Posted: Wed Apr 01, 2026 4:09 am
Hi All,
I'm new to the forum. Anyway, I've been building a Python based Home Dashboard that includes many things (Weather forecast, upcoming calendar events, Smart Devices control etc.) as well as a dashboard of the Fox-ESS System. This shows most of the working status of the system (PV generation, grid in/out, house load, battery SoC and power in/out). This is all working very well. The next step is to add control of the current mode (Mode Scheduler). Can anyone share examples of working v3/device/schedule/enable json messages. My concern is around Fox-ESS's new (ish) "defualt mode" it uses in its Web and Phones Apps. Their json's include a "isRemainMode" flag is there v3/device/schedule/enable commands. This seems to allow for overlaping schedules (you see it on the apps). So you can have a "Force Discharge" for 16:00 to 19:00 and there will be the "default" (fall back) schedule set to say "selfuse" for 00:00 to 23:59. Which appears to be a no no, for using the public API. How is this managed when using the Open API that does not have the "isRemainMode" flag?
Many thanks in advance.
Rob
PS Yes, I am reinventing the wheel as I could use Home Assistant etc. I'm retired, I've got the time, and I'm learning stuff.
I'm new to the forum. Anyway, I've been building a Python based Home Dashboard that includes many things (Weather forecast, upcoming calendar events, Smart Devices control etc.) as well as a dashboard of the Fox-ESS System. This shows most of the working status of the system (PV generation, grid in/out, house load, battery SoC and power in/out). This is all working very well. The next step is to add control of the current mode (Mode Scheduler). Can anyone share examples of working v3/device/schedule/enable json messages. My concern is around Fox-ESS's new (ish) "defualt mode" it uses in its Web and Phones Apps. Their json's include a "isRemainMode" flag is there v3/device/schedule/enable commands. This seems to allow for overlaping schedules (you see it on the apps). So you can have a "Force Discharge" for 16:00 to 19:00 and there will be the "default" (fall back) schedule set to say "selfuse" for 00:00 to 23:59. Which appears to be a no no, for using the public API. How is this managed when using the Open API that does not have the "isRemainMode" flag?
Many thanks in advance.
Rob
PS Yes, I am reinventing the wheel as I could use Home Assistant etc. I'm retired, I've got the time, and I'm learning stuff.