FoxESS Community - Owners & Installers Forum

Posted: **Tue Aug 26, 2025 8:38 am**

The API appears to be down again, from 04:25 this morning. Others have reported the same issue as well - https://github.com/macxq/foxess-ha/issues/311

Code: Select all

This error originated from a custom integration.

Logger: custom_components.foxess.sensor
Source: custom_components/foxess/sensor.py:850
integration: foxess (documentation, issues)
First occurred: 08:19:34 (17 occurrences)
Last logged: 08:38:46

OA Battery Settings Bad Response: {'errno': 41203, 'msg': 'Operation timeout', 'result': None}

Posted: **Tue Aug 26, 2025 1:45 pm**

Yes there were several errors in the OpenAPI which started around 4.20am with a 41200 error from the report queries, and 41203 on the battery settings fetch.

Fox have been notified and very quickly rolled back whatever the change was, and so the openapi is working again - HOWEVER, if you restarted your home assistant because of the nature of the fault (a succesful api read that had a failure response) it will have very likely have burnt through your remaining api calls and you'll have to wait for midnight for that to be reset.

Posted: **Tue Aug 26, 2025 2:03 pm**

Yes, I've exhausted the API calls now due to this error. Is there anything that we can do, other than waiting until midnight for it to be reset?

Posted: **Tue Aug 26, 2025 2:37 pm**

My API call´s are as well burned down.
Would it be possible after you solved such errors to set the api count to the last count as well?

Posted: **Tue Aug 26, 2025 2:43 pm**

Sadly nothing that can be done, the api_count is internal to the Fox servers and once exhausted you have to wait for it to reset - my systems api_count is also now exhausted.

FoxESS Community - Owners & Installers Forum

API down again

API down again

Re: API down again

Re: API down again

Re: API down again

Re: API down again