Page 1 of 1

Depletion of API calls results in Scheduler defaulting to on

Posted: Sun Jul 13, 2025 5:02 pm
by Kosymodo
I’ve had my system running for a few days now, and initially set it up with a schedule to force charge my battery during my IOG cheap hours. However, I soon realised that at this time of year, this isn’t required, with enough solar available during the day to charge the battery and cover load (and also not yet having an export set up). So I switched it off.

Yesterday evening, I noticed that the battery was being charged from the grid. Knowing that the Scheduler was off, I wondered what was happening. I then noticed that my Energy Stats app wasn’t updating, with the error message being that I’d no FoxESS API calls remaining. (This, I think, was due to me having set up multiple widgets etc, all requiring API calls)

Putting 2 + 2 together, I believe that the Energy Stats app having no remaining FoxESS calls resulted in the Scheduler defaulting to on. Is this expected behaviour? It shouldn’t be an issue from now on, as I’ve deleted some of my widgets, which will result in fewer API calls. However, if it’s expected behaviour, it’ll be something to keep an eye on, just in case.

Easy fix was to go into the FoxCloud app to turn off the Force Charge, so only 2kWh (14p) wasted :)

Re: Depletion of API calls results in Scheduler defaulting to on

Posted: Sun Jul 13, 2025 5:24 pm
by alpriest
If there are no API calls left then Energy Stats can't call the API to switch on the scheduler (widgets etc. do not switch on the scheduler but yes they would also use API calls). Also multiple phones can use more API requests.

You could check that you have the correct number of API - it should be 1440 as documented in https://www.foxesscloud.com/public/i18n ... ument.html and see how they go during the day from within ES, under settings > debug data > view request count.

I don't know how the scheduler could get switched on without user interaction though, this does seem a bit scary!

Re: Depletion of API calls results in Scheduler defaulting to on

Posted: Sun Jul 13, 2025 5:37 pm
by Kosymodo
Thanks Al

Is it perhaps a case of Energy Stats not being able to call the API to switch off the scheduler? Thinking about it in reverse, perhaps the inverter has the scheduler set to on, and Energy Stats is switching it off? Without the API call, there’s no off command?

I do have 1440 API calls available…any idea what the 24hr period is? I didn’t see it reset at midnight (BST), it must have been sometime later.

Re: Depletion of API calls results in Scheduler defaulting to on

Posted: Sun Jul 13, 2025 5:57 pm
by alpriest
I've never seen it reset, but I would assume it's either UTC midnight or midnight at whatever timezone the Fox servers are located in which I would imagine China which I think means a 5pm reset.

That's correct it wouldn't be able to switch off the scheduler but this is a manual task too so I'm pretty sure you'd get a rate limiting error message if you tried it when that happened. Additionally you'd see either old data or error messages on the power flow screen when that failed too.