core: Client unable to keep up with pending messages. Stayed over 512 for 5 seconds. The system's load is too high or an integration is misbehaving
The problem
In the logfile for the websocket_api I see the error below, I am unable to check what the cause of this error is:
Logger: homeassistant.components.websocket_api.http.connection Source: components/websocket_api/http.py:157 Integration: Home Assistant WebSocket API (documentation, issues) First occurred: 07:21:40 (1 occurrences) Last logged: 07:21:40
[281472675383568] Client unable to keep up with pending messages. Stayed over 512 for 5 seconds. The system’s load is too high or an integration is misbehaving
What version of Home Assistant Core has the issue?
2022.11.04
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
websocket api
Link to integration documentation on our website
https://www.home-assistant.io/integrations/websocket_api/
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
ogger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/http.py:157
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 07:21:40 (1 occurrences)
Last logged: 07:21:40
[281472675383568] Client unable to keep up with pending messages. Stayed over 512 for 5 seconds. The system's load is too high or an integration is misbehaving
Additional information
No response
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 43 (2 by maintainers)
I got to this thread when I encountered the same error and what was interesting was that I have been encountering similar symptoms with my HA for a long time, where it disconnects and reconnects constantly, and most annoyingly refreshing my Node-Red and destroying all the work that I did since I last deployed it.
Along the way - I wont go into all the integrations that I tried to take out or disable to find my own culprit. To be honest, I thought it was associated with the TUYA integration, but nothing changed with disabling or removing that integration.
When I read through @ss89 comment to see what integrations were common, of all things, I tried to disable the SUN integration under pure desperation. I could not believe my eyes. All my disconnects stopped!
While I am not sure this will be the fix for other, I wanted to contribute to this and see if it helped anyone else. I really wish there was a better way to diagnose what integration was causing my issues, but I was just floored that this could have caused my issue.
Yes - I did move to the latest HA version 2023.1.0, but once I did, I got other errors and I solved those, but still had the disconnect issue. I kept hoping that each new release would solve the issue, but again no. So I decided to spend some time to diagnose it (AGAIN!) and then I looked over @ss89 list of integrations and decided to just disable my SUN integration.
Now my new issue is that I use the SUN integration for monitoring the sun angles and elevation to adjust the shades in my house, so I will be heading down the path of, removing it all together and then seeing what happens when I install it again.
Again - I am offering this as something to try. I will post as I continue to find anything new - good or bad.
I upgraded to an i5 PC to make sure I had enough CPU for my 20 devices, and the number of errors only increased - so I believe there is something more serious going on. So I think it’s a little premature to close the PR a month before we can test it.
If only there was some clue as to what the offending messages are, where they are coming from, or where they are going to.
scratch that - I still get them.
Any progress on this one? I am facing the same issue. It appears to be impacting the MQTT messages as well (i.e. devices not being able to connect) .
I do have close to a hundred devices on localTuya and it is core to the automations.
The system is running on a VM with 8 cores and 10 GBs memory - so grunt is not an issue.