restriction-card: Card Bug? Client exceeded max pending messages

Hi, 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

About this issue

Original URL
State: closed
Created 5 years ago
Comments: 20 (10 by maintainers)

Most upvoted comments

Got a test environment setup and found the bug right away 🎉 was a simple typo in my update check 🙈 thanks, everyone!

iantrich on Nov 8, 2019

I’ll try to do some further digging tonight

iantrich on Nov 6, 2019

You mean this way, right? (replacing restriction card with vertical stack):

type: 'custom:vertical-stack-in-card'
cards:
  - type: map
    entities: []

type: vertical-stack
cards:
  - type: map
    entities: []

With this, the flashing is gone.

@ludeeus I already tried that, but tried again and it didn’t help

kathy705 on Nov 6, 2019

Another thing, try using /local/community/restriction-card/restriction-card.js to make sure HACS is not doing anything funny here.

Clear the cache to make the change.

ludeeus on Nov 6, 2019

The simplest view config with which the problem occurs is this:

  - title: TEST
    path: test
    badges: []
    cards:
      - type: 'custom:restriction-card'
        card:
          type: map
          entities: []

And max pending messages is still happening

kathy705 on Nov 6, 2019

Hi, today the error didn’t appear anymore. Maybe it was just network problem or something like this and this card was just the proverbial straw that broke the camel’s back. I’ll close this for now and keep an eye on that error message. If it comes back, I check out if removing other cards also help (I only removed just this one, because it was the last one added and had no problems before). Sorry for bothering you!

kathy705 on Oct 21, 2019