Card Bug? Client exceeded max pending messages
See original GitHub issueHi,
when I let Home Assistant open for a while, I get hundreds of these entries in my log:
ERROR (MainThread) [homeassistant.components.websocket_api.http.connection.139694929600976] Client exceeded max pending messages [2]: 512
Additionally the “reconnecting” toast message flashes up and dissapears alternating.
When I remove the restriction card everything is fine again.
Is there any way to read the pending messages and check their origin or something like that?
Best regards,
Kathy
Issue Analytics
- State:
- Created 4 years ago
- Comments:20 (10 by maintainers)
Top Results From Across the Web
Client exceeded max pending messages - Configuration
Client exceeded max pending messages · Open and edit a Lovelace card in Firefox (have not tested Chrome yet). · Close the card...
Read more >Permanent error: Client exceeded max pending messages [2 ...
I have more than 15.000 such errors a day. Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):.
Read more >Client unable to keep up with pending messages. Stayed over ...
Client unable to keep up with pending messages. Stayed over 512 for 5 seconds. These messages have been filling my logs.
Read more >Error codes for the Amazon EC2 API - AWS Documentation
The number of client connections you're attempting to terminate exceeds the limit. CidrConflict, You cannot enable a VPC for ClassicLink or extend a...
Read more >Error Codes Guide - Developer Central - Verifone
Display Message Additional Display Message Possible Reasons for the Message
Success The transaction is successful.
Transaction Cancelled Operator Abort
Transaction Cancelled Operator Timeout
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Got a test environment setup and found the bug right away 🎉 was a simple typo in my update check 🙈 thanks, everyone!
I’ll try to do some further digging tonight