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.
Inverter: H3-10.0-Smart
Batteries: EQ4800-L9
PV's: 13.6kw Who Flung Dung (unknown Chinese Panels?)
PV Inverter: 10kw Solaris
Batteries: EQ4800-L9
PV's: 13.6kw Who Flung Dung (unknown Chinese Panels?)
PV Inverter: 10kw Solaris
Please post an example of some JSON including the flag as this isn't in the public docs.
My guess is that this is flagging the Remainng Time Slots periods 00:00-23:59 and sets the default work mode. It probably only works when attached to that time period.
My guess is that this is flagging the Remainng Time Slots periods 00:00-23:59 and sets the default work mode. It probably only works when attached to that time period.
H1-6.0-E hybrid inverter
6 x HV2600 v2 batteries
16 x JA Solar 405w panels
7 x Tigo TS4-A-O optimisers
6 x HV2600 v2 batteries
16 x JA Solar 405w panels
7 x Tigo TS4-A-O optimisers
From a quick test, the isRemainMode flag isn't processed by Open API. You can send overlapping time periods via Open API though and these are accepted. However, it isn't clear how these will be processed by the inverter.
The best advice when setting schedules via the API is always send explicit non-overlapping times and modes to cover the whole day. In this case, there is no need to try to send a remaining time period.
If you get a remaining time period fetching schedule data, the best approach seems to be to delete it for reliable operation of your schedules.
The best advice when setting schedules via the API is always send explicit non-overlapping times and modes to cover the whole day. In this case, there is no need to try to send a remaining time period.
If you get a remaining time period fetching schedule data, the best approach seems to be to delete it for reliable operation of your schedules.
H1-6.0-E hybrid inverter
6 x HV2600 v2 batteries
16 x JA Solar 405w panels
7 x Tigo TS4-A-O optimisers
6 x HV2600 v2 batteries
16 x JA Solar 405w panels
7 x Tigo TS4-A-O optimisers