Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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 #82562

Closed
kranendijk opened this issue Nov 23, 2022 · 43 comments · Fixed by #86854

Comments

@kranendijk
Copy link

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

@tanker11
Copy link

I have the same issue and in addition to it the following error:

Logger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/http.py:52
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 01:35:47 (149156 occurrences)

At the same time Node-Red is having issues of repeated disconnection/reconnection, seemingly this has something to do with it. When it first appeared I was trying the new Bluetooth related capabilities, and iBeacon tracker created a lot of related entries.
When removing them the situation got better for a while , but then the errors and Node-Red reconnections are back. (iBeacon integration disabled and related entities removed.)

HA version is 2022.11.2

@henkzet
Copy link

henkzet commented Nov 25, 2022

same issue here , also Node-Red is disconneting and connecting all the time...
Home Assistant 2022.11.4
Integration: Home Assistant WebSocket API
logger: homeassistant.components.websocket_api.http.connection

HA/Node-Red very very unreliable for the last weeks...

@kroon040
Copy link

Same issue here
Homeassistant 2022.11.4

Logger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/http.py:157
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 06:27:14 (4802 occurrences)
Last logged: 13:57:34

[281472552731696] 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
[281472593219152] 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
[281472122599792] 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

@ghost
Copy link

ghost commented Nov 27, 2022

I also have this issue on 2022.1.4 but I do not have Node-Red like some of the others

Logger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/http.py:157 
Integration: Home Assistant WebSocket API (documentation, issues) 
First occurred: 26 November 2022 at 23:33:10 (1 occurrences) 
Last logged: 26 November 2022 at 23:33:10

[547619470880] 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

@tanker11
Copy link

tanker11 commented Dec 2, 2022

As others are saying in other forums, deleting entities not used any more, cleaning up in Node-red, etc seems to help for a while, then it comes back, and I am really interested how to catch the guilty process or integration...

@ss89
Copy link

ss89 commented Dec 7, 2022

One of my home assistant installations is having the same issue.
I'm not sure if it relates, but we checked the logs because we have a very laggy shelly plus i4 (ac version). There's an automation to trigger the state change of shelly plug s power outlets.
There's also a dc version in the system, but that is never misbehaving.
Only 1 AP in the network and no fancy setup.
Used integrations:

  • shelly
  • Dlna (just discovered, not activated)
  • Avm fritz smart home
  • Supervisor
  • Home (meterologisk institutt)
  • Mobile app (android)
  • Raspberry pi power supply checker
  • Sun

@pratahsinnetamby
Copy link

pratahsinnetamby commented Dec 27, 2022

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.

@donburch888
Copy link

+1 for about 3 months now.

It was making my RasPi4 unresponsive at 26% processorUsage and requiring 3 reboots to clear the problem.

I have now upgraded to a OptiPlex 7050 with i5 processor and now, after less than 12 hours since reboot, 12 million error messages logged. "Not happy Jan". Thankfully the processorUsage shows 12% and doesn't bog the system down excessively like on the RasPi.

image

Logger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/http.py:132
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 11:22:38 AM (12937776 occurrences)
Last logged: 9:07:55 PM

[140561482277136] Client exceeded max pending messages [2]: 2048
[140561482648928] Client exceeded max pending messages [2]: 2048

sensor.connected_clients is showing 5
I have disabled node-RED because I am using it for all my automations - connected clients dropped by 1 but still high (12%) CPU
I know debug proceedure is to remove the unofficial LocalTuya HACS add-on - but then I might as well quit Home Assistant without automations or half my devices. ;-(

@dbrb2
Copy link

dbrb2 commented Dec 29, 2022

Is there any way of diagnosing what are making the problematic calls?

@akula3
Copy link

akula3 commented Dec 30, 2022

Same issue since yesterday. HA restart doesn't help.

Home Assistant 2022.12.8
Supervisor 2022.12.1
Operating System 9.4
Frontend 20221213.1 - latest

The error from subject is always coming together with:

Logger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/http.py:132
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 29. Dezember 2022 um 11:38:02 (5808 occurrences)
Last logged: 10:06:22
[547830186336] Client exceeded max pending messages [2]: 2048

I'm not sure, if it has something to do with the subject, but at the same day I got info message for one Hue bulb:

grafik

An update via Z2M integration doesn't work:

grafik

@chench00
Copy link

chench00 commented Jan 1, 2023

+1. A restart fixes it for me.

@ghost
Copy link

ghost commented Jan 1, 2023

+1. A restart fixes it for me.

Genuine question: Does the restart fix it or simply clear the log (and it reoccurs later)?

@chench00
Copy link

chench00 commented Jan 1, 2023

+1. A restart fixes it for me.

Genuine question: Does the restart fix it or simply clear the log (and it reoccurs later)?

It fixes it temporarily (hence the +1 reply above). Sometimes it will be days before it reappears. I only notice it since my syslog server sends me an alert of the repeating messages. Still looking for a fix.

@ghost
Copy link

ghost commented Jan 1, 2023

It fixes it temporarily

cheers.

@dbrb2
Copy link

dbrb2 commented Jan 1, 2023

This may not be the case for all users. In my case I now think the problem only occurs directly after a reboot, subsequently stopping - suggesting it was some artefact of the system catching up at startup.

@Qpernicus
Copy link

It would be very helpful to get some sort of pointer to WHICH part is causing the problem. I get this alert to intermittently. And yes a reboot mostly sorts it out for a while. But still would like to keep my log 'clean' of errors as much as possible. This one is partly unfixable atm

@MihleTX
Copy link

MihleTX commented Jan 5, 2023

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.

@ss89
Copy link

ss89 commented Jan 5, 2023

Thanks for your Hint @MihleTX !
I will definitely try this out.
The thing i want to try first is a small wifi router upgrade, as mine currently reports >= 90 usage and it might just become unstable.
After that i'll disable the sun (just the integration 😉) and see what happens.

@kuradi
Copy link

kuradi commented Jan 6, 2023

i tried disable sun component...
image
in first place i had this number in the end ca 60000, now i got 30000... so - progress :)

@ghost
Copy link

ghost commented Jan 7, 2023

The only thing I have in common with @ss89 is also sun.

I am on 20223.1.1 (HA container) and got 2 more logs entries this morning.

I have disabled sun and we'll see what happens - thanks for the suggestion, @MihleTX

@ghost
Copy link

ghost commented Jan 14, 2023

I have disabled sun and we'll see what happens - thanks for the suggestion, @MihleTX

I haven't seen the issue since.

@JohnBull-1975
Copy link

New with HA and on my way to migrate my stuff over.
Running most current on a 6th gen i3 NUC with 8GB of RAM.
I saw the same issue in my log today.
Have node red installed but have not experienced any problems with it.
Might try to disable sun as I don't use it.
Following...

@murkumurdok
Copy link

Can you still use sunrise/sunset conditions in automations if the sun integration is disabled?

@JohnBull-1975
Copy link

Can you still use sunrise/sunset conditions in automations if the sun integration is disabled?

Guess not, but I'm only using my light sensor for deciding when to turn lights on/off.
For my old controller I used some sunrise/sunset conditions. Might implement that in HA as well.
Is sunrise/sunset in BigTimer in node red dependent on sun integration?

@MihleTX
Copy link

MihleTX commented Jan 16, 2023

I use Node Red and BigTimer - and it is not leveraging the SUN integration for it.

@MihleTX
Copy link

MihleTX commented Jan 16, 2023

I used to have all my window shades integrated using the SUN integration and the sun position to determine when to open and close, but I switched over to light sensors in the rooms and that worked better anyway.

@JohnBull-1975
Copy link

Tried to disable sun integration but had the same error again this morning at 7:57

@KitHubek
Copy link

the same here. Newest HA version

L```
ogger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/http.py:157
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 18 stycznia 2023 16:37:04 (2 occurrences)
Last logged: 15:16:07

[548012469472] 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
[545111189120] 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

@ghost
Copy link

ghost commented Jan 21, 2023

I have disabled sun and we'll see what happens - thanks for the suggestion, @MihleTX

I haven't seen the issue since.

scratch that - I still get them.

@bdraco
Copy link
Member

bdraco commented Jan 29, 2023

Some cases can be caused by a large number of entities. The linked pr should improve the situation when you have 2000+ entities.

If you still get the message after 2023.3.0 (2023.2.0 will not have the change) be sure to include a callgrind.out file from the profiler integration profiler.start service in any new issues

@JohnBull-1975
Copy link

OK...sounds good it will be solved!
I'm at 2023.1.7 now...guess it takes a while, but if it's a known issue I assume I don't have to worry.
I have <<2000 entities. Probably <200.
What is callgrind.out file? I'm new to this...

@bdraco
Copy link
Member

bdraco commented Jan 29, 2023

You can generate a callgrind with https://www.home-assistant.io/integrations/profiler/#service-profilerstart

@JohnBull-1975
Copy link

OK - so the file is not a solution for the problem, it's some kind of log/debug file.
Good to know, but I hope I don't have dig into that...have had too much else to struggle with last few days - but I have at least learned something and my system looks to work better than my old simple controller now

@rossco555
Copy link

Disabling the Sun integration does not prevent this error occurring on my setup, under the latest version (no issues on 2022.11).

I'm using HA Container on Synology NAS (DS920+ with 20GB RAM).

Hugely frustrating, two and half months into trying to work through this, but glad I'm not alone!

@donburch888
Copy link

The linked pr should improve the situation when you have 2000+ entities.

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.

@swissjon
Copy link

I had this a couple of weeks ago. I can't pinpoint exactly what fixed it, but I suspect it was zigbee2mqtt. Make sure you have the latest version installed.

@rossco555
Copy link

I'm on 1.30.1 which I think is the latest. Unfortunately, I've still got the issue.

@ghost
Copy link

ghost commented Feb 12, 2023

I'm also on 1.30.1 (latest) and also still have the issue.

@donburch888
Copy link

It seems the problem still exists in 2023.3, but now the system slows to a crawl (even on my i5 PC) for much longer before reporting the error.

Client unable to keep up with pending messages. Reached 4096 pending messages.

The good news is that the error message now gives information about where the issue lies, ... I think ...
... though in my case it seems to be pointing the finger at Firefox browser on my PC unable to display a HTML

.

@ghost
Copy link

ghost commented Mar 2, 2023

The good news is that the error message now gives information about where the issue lies, ... I think ... ... though in my case it seems to be pointing the finger at Firefox browser on my PC unable to display a HTML

What's the full log entry (pointing to the where the issue lies)?

@donburch888
Copy link

I am intending to look more into this, starting with disabling the HACS frontend "HTML Jinja2 Template card" which (from memory) is used for lovelace "- type: custom:html-template-card" used to generate the HTML

... but at the moment I am focused on getting my pc191ha_xxx power switches migrated from LocalTuya to ESPHome. In fact, these are the switches referred to in these error messages !

Logger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/http.py:154
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 5:42:29 PM (9 occurrences)
Last logged: 7:42:52 PM

[140112695769744] don from 192.168.1.99 (Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:99.0) Gecko/20100101 Firefox/99.0): Client unable to keep up with pending messages. Reached 4096 pending messages. The system's load is too high or an integration is misbehaving. Last message was: {"id":4190,"type":"event","event":{"result":"<table width='100%'><tr>\n <th>name</th>\n <th>Upright</th>\n <th align='right'>Fridge</th>\n <th align='right'>Chest Freezer</th>\n</tr><tr>\n <td>Current (Amps)</td>\n <td align='right'>0.34 A</td>\n <td align='right'>0.21 A</td>\n <td align='right'>0.46 A</td>\n</tr><tr>\n <td>Current (Volts)</td>\n <td align='right'>248.9 V</td>\n <td align='right'>249.2 V</td>\n <td align='right'>246.5 V</td>\n</tr><tr>\n <td>Current (Watts)</td>\n <td align='right'>55.1 W</td>\n <td align='right'>49.4 W</td>\n <td align='right'>90.5 W</td>\n</tr><tr>\n <td>Today kwh</td>\n <td align='right'>0.003 kwh</td>\n <td align='right'>0.003 kwh</td>\n <td align='right'>1.08 kwh</td>\n</tr><tr>\n <td>Total kwh</td>\n <td align='right'>247.957 kwh</td>\n <td align='right'>23.121 kwh</td>\n <td align='right'>18.279 kwh</td>\n</tr><tr>\n <td>SWITCH</td>\n <td align='right'>on</td>\n <td align='right'>on</td>\n <td align='right'>on</td>\n</tr></table>","listeners":{"all":false,"entities":["sensor.hs110_102_current_consumption","sensor.kp115_103_current_consumption","sensor.hs110_101_total_consumption","sensor.hs110_102_voltage","sensor.hs110_102_today_s_consumption","sensor.kp115_103_current","sensor.hs110_101_current","sensor.kp115_103_voltage","sensor.hs110_101_current_consumption","sensor.hs110_101_today_s_consumption","sensor.kp115_103_total_consumption","sensor.hs110_101_voltage","sensor.hs110_102_total_consumption","sensor.kp115_103_today_s_consumption","switch.hs110_102","sensor.hs110_102_current","switch.kp115_103"],"domains":[],"time":false}}}
[140112693971456] don from 192.168.1.99 (Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:99.0) Gecko/20100101 Firefox/99.0): Client unable to keep up with pending messages. Reached 4096 pending messages. The system's load is too high or an integration is misbehaving. Last message was: {"id":4194,"type":"event","event":{"result":"<table width='100%'><tr>\n <th>name</th>\n <th>Upright</th>\n <th align='right'>Fridge</th>\n <th align='right'>Chest Freezer</th>\n</tr><tr>\n <td>Current (Amps)</td>\n <td align='right'>0.49 A</td>\n <td align='right'>0.21 A</td>\n <td align='right'>0.44 A</td>\n</tr><tr>\n <td>Current (Volts)</td>\n <td align='right'>248.9 V</td>\n <td align='right'>249.6 V</td>\n <td align='right'>247.9 V</td>\n</tr><tr>\n <td>Current (Watts)</td>\n <td align='right'>83.1 W</td>\n <td align='right'>49.1 W</td>\n <td align='right'>86.2 W</td>\n</tr><tr>\n <td>Today kwh</td>\n <td align='right'>0.007 kwh</td>\n <td align='right'>0.006 kwh</td>\n <td align='right'>1.085 kwh</td>\n</tr><tr>\n <td>Total kwh</td>\n <td align='right'>247.961 kwh</td>\n <td align='right'>23.124 kwh</td>\n <td align='right'>18.284 kwh</td>\n</tr><tr>\n <td>SWITCH</td>\n <td align='right'>on</td>\n <td align='right'>on</td>\n <td align='right'>on</td>\n</tr></table>","listeners":{"all":false,"entities":["sensor.hs110_102_current_consumption","sensor.kp115_103_current_consumption","sensor.hs110_101_total_consumption","sensor.hs110_102_voltage","sensor.hs110_102_today_s_consumption","sensor.kp115_103_current","sensor.hs110_101_current","sensor.kp115_103_voltage","sensor.hs110_101_current_consumption","sensor.hs110_101_today_s_consumption","sensor.kp115_103_total_consumption","sensor.hs110_101_voltage","sensor.hs110_102_total_consumption","sensor.kp115_103_today_s_consumption","switch.hs110_102","sensor.hs110_102_current","switch.kp115_103"],"domains":[],"time":false}}}
[140112377496288] don from 192.168.1.99 (Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:99.0) Gecko/20100101 Firefox/99.0): Client unable to keep up with pending messages. Reached 4096 pending messages. The system's load is too high or an integration is misbehaving. Last message was: {"id":4194,"type":"event","event":{"result":"<table width='100%'><tr>\n <th>name</th>\n <th>Upright</th>\n <th align='right'>Fridge</th>\n <th align='right'>Chest Freezer</th>\n</tr><tr>\n <td>Current (Amps)</td>\n <td align='right'>0.51 A</td>\n <td align='right'>0.21 A</td>\n <td align='right'>0.43 A</td>\n</tr><tr>\n <td>Current (Volts)</td>\n <td align='right'>243.7 V</td>\n <td align='right'>248.2 V</td>\n <td align='right'>243.3 V</td>\n</tr><tr>\n <td>Current (Watts)</td>\n <td align='right'>84.4 W</td>\n <td align='right'>48.2 W</td>\n <td align='right'>82.4 W</td>\n</tr><tr>\n <td>Today kwh</td>\n <td align='right'>0.021 kwh</td>\n <td align='right'>0.013 kwh</td>\n <td align='right'>1.098 kwh</td>\n</tr><tr>\n <td>Total kwh</td>\n <td align='right'>247.975 kwh</td>\n <td align='right'>23.131 kwh</td>\n <td align='right'>18.297 kwh</td>\n</tr><tr>\n <td>SWITCH</td>\n <td align='right'>on</td>\n <td align='right'>on</td>\n <td align='right'>on</td>\n</tr></table>","listeners":{"all":false,"entities":["sensor.hs110_102_current_consumption","sensor.kp115_103_current_consumption","sensor.hs110_101_total_consumption","sensor.hs110_102_voltage","sensor.hs110_102_today_s_consumption","sensor.kp115_103_current","sensor.hs110_101_current","sensor.kp115_103_voltage","sensor.hs110_101_current_consumption","sensor.hs110_101_today_s_consumption","sensor.kp115_103_total_consumption","sensor.hs110_101_voltage","sensor.hs110_102_total_consumption","sensor.kp115_103_today_s_consumption","switch.hs110_102","sensor.hs110_102_current","switch.kp115_103"],"domains":[],"time":false}}}
[140112720916448] don from 192.168.1.99 (Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:99.0) Gecko/20100101 Firefox/99.0): Client unable to keep up with pending messages. Reached 4096 pending messages. The system's load is too high or an integration is misbehaving. Last message was: {"id":4194,"type":"event","event":{"result":"<table width='100%'><tr>\n <th>name</th>\n <th>Upright</th>\n <th align='right'>Fridge</th>\n <th align='right'>Chest Freezer</th>\n</tr><tr>\n <td>Current (Amps)</td>\n <td align='right'>0.55 A</td>\n <td align='right'>0.02 A</td>\n <td align='right'>0.42 A</td>\n</tr><tr>\n <td>Current (Volts)</td>\n <td align='right'>242.7 V</td>\n <td align='right'>244.1 V</td>\n <td align='right'>242.5 V</td>\n</tr><tr>\n <td>Current (Watts)</td>\n <td align='right'>91.3 W</td>\n <td align='right'>0.0 W</td>\n <td align='right'>78.4 W</td>\n</tr><tr>\n <td>Today kwh</td>\n <td align='right'>0.046 kwh</td>\n <td align='right'>0.03 kwh</td>\n <td align='right'>1.13 kwh</td>\n</tr><tr>\n <td>Total kwh</td>\n <td align='right'>248.0 kwh</td>\n <td align='right'>23.148 kwh</td>\n <td align='right'>18.329 kwh</td>\n</tr><tr>\n <td>SWITCH</td>\n <td align='right'>on</td>\n <td align='right'>on</td>\n <td align='right'>on</td>\n</tr></table>","listeners":{"all":false,"entities":["sensor.hs110_102_current_consumption","sensor.kp115_103_current_consumption","sensor.hs110_101_total_consumption","sensor.hs110_102_voltage","sensor.hs110_102_today_s_consumption","sensor.kp115_103_current","sensor.hs110_101_current","sensor.kp115_103_voltage","sensor.hs110_101_current_consumption","sensor.hs110_101_today_s_consumption","sensor.kp115_103_total_consumption","sensor.hs110_101_voltage","sensor.hs110_102_total_consumption","sensor.kp115_103_today_s_consumption","switch.hs110_102","sensor.hs110_102_current","switch.kp115_103"],"domains":[],"time":false}}}
[140112697236720] don from 192.168.1.99 (Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:99.0) Gecko/20100101 Firefox/99.0): Client unable to keep up with pending messages. Reached 4096 pending messages. The system's load is too high or an integration is misbehaving. Last message was: {"id":4162,"type":"event","event":{"result":"<table width='100%'><tr>\n <th>name</th>\n <th align='right'>Washer</th>\n <th align='right'>Dryer</th>\n</tr><tr>\n <td>Current (Amps)</td>\n <td align='right'>0.04 A</td>\n <td align='right'>0.0 A</td>\n</tr><tr>\n <td>Current (Volts)</td>\n <td align='right'>242.9 V</td>\n <td align='right'>245.8 V</td>\n</tr><tr>\n <td>Current (Watts)</td>\n <td align='right'>0.5 W</td>\n <td align='right'>0.0 W</td>\n</tr><tr>\n <td>Today kwh</td>\n <td align='right'>0.009 kwh</td>\n <td align='right'>unknown</td>\n</tr><tr>\n <td>Total kwh</td>\n <td align='right'>8.47 kwh</td>\n <td align='right'>unknown</td>\n</tr></table>","listeners":{"all":false,"entities":["sensor.kp115_104_total_consumption","sensor.kp115_104_voltage","number.pc191ha_105_total_consumption","sensor.kp115_104_current_consumption","sensor.kp115_104_current","number.pc191ha_105_today_s_consumption","switch.pc191ha_105","sensor.kp115_104_today_s_consumption"],"domains":[],"time":false}}}

I note that the correct values are being displayed in the HTML code, and indeed the tables display correctly in Lovelace, so the issue is not the HTML code itself. Possibly HA is trying to update them too frequently ?
image

@ghost
Copy link

ghost commented Mar 2, 2023

There is the following comment in the "hints" section for this card, but not sure if it applies to you:

If you want to enable refreshing for every change in HA use flag always_update: true. WARNING: this may cause heavy load of browser/HA. Best to use with flag do_not_parse: true.

There is also a long-running bug report for "Client exceeded max pending messages". Again, not sure if it applies to you, but maybe worth look? It refers to problems when the card is permanently displayed (maybe on a wall-mounted device) or similar.

@donburch888
Copy link

There is also a long-running bug report for "Client exceeded max pending messages".

There are many many bug reports for these error messages, which I have been looking at periodically since September ... and lots of guesses as to which is the "misbehaving" integration.

There is the following comment in the "hints" section for this card,

That was one of the things I looked into, and yes it does now appear to be my problem. I don't want the table constantly updating unless the user is actually looking at that Lovelace tab, so always_update is set false. And do_not_parse prevents the templates to insert the values of the sensors and attributes, no that defeats the purpose.

At least the new error message does show that for me, the HTML tables are the issue, and I need to think or find another approach.

@github-actions github-actions bot locked and limited conversation to collaborators Apr 1, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.