I've been using this for a few months, but recently have started to experience frequent dropouts and lost data, particularly in the UK/Europe afternoons.
I'm sure it was much better back about March 2024.
In the .../home-assistant.log, I see many errors like:
2024-06-22 12:18:04.008 ERROR (MainThread) [custom_components.foxess.sensor] OA Device Detail Bad Response: {'errno': 40256, 'msg': 'Parameter could not be parsed correctly illegal timestamp'}
2024-06-22 12:18:04.008 WARNING (MainThread) [custom_components.foxess.sensor] FoxESS has Cloud timeout or the Inverter is off-line, connection will be retried in 1 minute.
2024-06-22 12:22:01.642 WARNING (MainThread) [custom_components.foxess.sensor] FoxESS has Cloud timeout or the Inverter is off-line, connection will be retried in 1 minute
2024-06-22 12:25:44.496 WARNING (MainThread) [custom_components.foxess.sensor] FoxESS has Cloud timeout or the Inverter is off-line, connection will be retried in 1 minute
Is this a general problem?
I'm running HA on a Raspberry PI5 using Raspbian OS and have tried using wifi or ethernet, with identical results.
My broadband is VirginMedia ~400mbps, with plenty of spare capacity and I am not seeing any ethernet errors
I'm a bit stumped, my next move may be to move HA from the RPI5 to a VM or WSL on Windows 11.
Home Assistant Foxess Cloud Integration
Foxess Cloud is OK for me at the moment.
I'm still getting dropouts with the HA integration, I lost API data so far today from 09:46-09:56, then 11:17- 11:34. then 11:40-11:46, then 15:30-15:07.
This is actually a relatively good day compared to the recent past.
I'm still getting dropouts with the HA integration, I lost API data so far today from 09:46-09:56, then 11:17- 11:34. then 11:40-11:46, then 15:30-15:07.
This is actually a relatively good day compared to the recent past.
-
- Posts: 1111
- Joined: Thu Oct 13, 2022 7:21 pm
This is a known problem with the Fox ESS OpenAPI, it is suffering performance problems from approx 12 noon, until 10pm and results in a number of sporadic time outs as it overloads.
Fox are aware of the problem and we are waiting on them to implement a fix - I have been recommending that users report the problem by raising a ticket or by email so that they know how many people are affected by this... and hopefully they will resolve it a bit faster.
Fox are aware of the problem and we are waiting on them to implement a fix - I have been recommending that users report the problem by raising a ticket or by email so that they know how many people are affected by this... and hopefully they will resolve it a bit faster.