core: Permanent error: Client exceeded max pending messages [2]: 512

Home Assistant release with the issue:

HA 0.93

Last working Home Assistant release (if known): HA 0.91 (0.92.0?)

Operating environment (Hass.io/Docker/Windows/etc.):

Home Assistant, Raspberry Lovelace interface on desktop Opera browser.

Component/platform:

homeassistant.components.websocket_api.http.connection

Description of problem: Tons of errors in error log with no any clear reason. I have more than 15.000 such errors a day.

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

Traceback (if applicable):

ERROR (MainThread) [homeassistant.components.websocket_api.http.connection.xxxx] Client exceeded max pending messages [2]: 512

Additional information: Didn’t have this issue in 0.91 and most probable (I don’t remember exactly) in 0.92.0 and did have it in 0.92.2.

About this issue

Original URL
State: closed
Created 5 years ago
Reactions: 1
Comments: 46 (12 by maintainers)

Most upvoted comments

HA authors should definitely add any mechanism that could process such kind of interface errors. They force the system to fall down, while there is no any tool to debug the reason of them.

Spirituss on Oct 1, 2019

Something blocked your browser to consume the websocket message. Turn on the debug log of webscoket_api component you will be able to see what was happening

logger:
  default: info
  logs:
    homeassistant.components.websocket_api: debug

awarecan on May 17, 2019