V1.0.18: Logging flooded with websocket errors
See original GitHub issueIf I cast to a single CC I only have these errors sporadically. While casting to a Group of 3 CC’s the log is flooded with these errors. This immediately stops when pausing the music
547493887328] Client exceeded max pending messages [2]: 2048
17:53:27 – (ERROR) Home Assistant WebSocket API - message first occurred at 17:46:51 and shows up 1065 times
[547493887328] Client unable to keep up with pending messages. Stayed over 512 for 5 seconds
17:53:26 – (ERROR) Home Assistant WebSocket API - message first occurred at 17:46:53 and shows up 67 times
Note: this logging is for a few minutes. Release notes for v1.0.18 don’t explain this. Related to chromecast updates in core-2022.5.4?!
Issue Analytics
- State:
- Created a year ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
WebSocket connection failed. Error in browser console, since ...
I'm using nginx as reverse proxy with letsencrypt. grafana log file: t=2021-10-28T13:43:05+0000 lvl=info msg="Request Completed" logger ...
Read more >Websocket errors flooding the console of browser
Today I switched my on-site environment to file system mode and these errors are still not going away even after disabling call center...
Read more >Changelogs – API Reference - BIT: BTC & Crypto Exchange
Update paging information of following REST endpoints: GET v1/market/trades. GET v1/orders. GET v1/transactions. GET v1/user/settlements
Read more >Logging - websockets 10.4 documentation - Read the Docs
If an error occurs, websockets tells you by raising an exception. For example, it raises a ConnectionClosed exception if the other side closes...
Read more >Changelog - Cypress Documentation
Compile errors are now surfaced in the command log during tests for Angular ... Fixed an issue where Cypress could crash if a...
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
I did not yet upgrade my production/family instance to 2022.5.4. That one is now without errors. I’ll take a look if these issues appear when I upgraded. Sounds to me like a bug or some endless loop.
This issue is solved in v1.1.x