I asked Fox Support and they advised that it "should be included in a future API update", but they have no timescale. The Open API documentation hasn't been updated since late May. Just wondering if anyone has any clues e.g. whether it'll be an update to SchedulerV3 / a new API? Calling /op/v3/device/scheduler/get doesn't return the current setting. The web interface and the app are able to set it so there must be a way to call it now...
Hi, Fox have introduced a new setting where you can choose what state the battery goes into after the cut-off SoC is reached (Self-Use / Feed-In / Back up / Standby). Unfortunately they've changed the default from "Standby" to "Self-use" which makes more sense, but breaks one of my daily scripts.
I asked Fox Support and they advised that it "should be included in a future API update", but they have no timescale. The Open API documentation hasn't been updated since late May. Just wondering if anyone has any clues e.g. whether it'll be an update to SchedulerV3 / a new API? Calling /op/v3/device/scheduler/get doesn't return the current setting. The web interface and the app are able to set it so there must be a way to call it now...
I asked Fox Support and they advised that it "should be included in a future API update", but they have no timescale. The Open API documentation hasn't been updated since late May. Just wondering if anyone has any clues e.g. whether it'll be an update to SchedulerV3 / a new API? Calling /op/v3/device/scheduler/get doesn't return the current setting. The web interface and the app are able to set it so there must be a way to call it now...
Fox may update Open API when it suits them, usually after pressure from 3rd party VPP providers.
They have a bizarre view that not maintaining parity by adding features to the app and not to Open API gives them a competitive advantage and have refused to add some features in the past because of this, such as reading cell temperatures...
The Fox app uses a separate private cloud API that is not published or documented.
You just have to wait and watch to see if or when they decide to update Open API.
They have a bizarre view that not maintaining parity by adding features to the app and not to Open API gives them a competitive advantage and have refused to add some features in the past because of this, such as reading cell temperatures...
The Fox app uses a separate private cloud API that is not published or documented.
You just have to wait and watch to see if or when they decide to update Open API.
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
That's friendly!
I guess I'll give it a while and send in another question and in the mean time manually edit the schedule via app/web every day 
I did ask if I could sign up to be alerted when the API is updated, but I didn't get a reply...
I did ask if I could sign up to be alerted when the API is updated, but I didn't get a reply...
For the API, most people won't use this feature anyway. It's simpler to use the data available to you to calculate the correct charge time and set the period needed instead of setting what happens after cut off?
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
Currently my script looks at the SoC in the evening, works out the charge rate needed to get to 95% SoC at 05:30 (Octopus IoG tariff) based on estimated house load overnight. The battery's usually charged a little before 05:30 - it used to "Standby" until the script ends; now it goes back into Self-use mode. It's not a biggie, just annoying.
There are various way round it - setting the schedule to Standby just seemed easiest. 