#ZIGBEE_MAX_MESSAGE_LIMIT_REACHED needs to daily reset my Yellow/ZHA

1 messages · Page 1 of 1 (latest)

full beacon
#

I keep hitting this error in Home Assistant:

Error while executing automation automation.hue_dimmer_chambre: Failed to send request: Failed to enqueue message: <sl_Status.ZIGBEE_MAX_MESSAGE_LIMIT_REACHED: 3075>

The only temporary fix is restarting Home Assistant or the ZHA integration. Based on forum threads, this seems to be a common issue, but no real solution has surfaced yet.

My setup is minimal: 5 Philips Hue bulbs, 2 remotes, and 2 wall switches. I’ve already opened an issue, but no response so far.

Is this a known bug with ZHA or the Zigbee stack? Are there any fixes or workarounds planned? I’m stuck on how to debug it further and this drives me crazy! Running on a Home Assistant Yellow with the built-in radio (no external dongle).

distant leaf
#

What firmware is your Yellow's radio running?

#

And are you using Zigbee groups at all?

full beacon
#

I am not using any Zigbee groups, my yellow is running latest version I think

#

It says EmberZNet Zigbee up to date 7.4.4.5

distant leaf
#

Can you post the automation.hue_dimmer_chambre automation?

full beacon
#

Sure

# 
blueprint:
  name: Philips Hue Dimmer (ZHA)
  description: Control lights with a Philips Hue Dimmer
  domain: automation
  input:
    dimmer:
      name: Philips Hue Dimmer
      description: Philips Hue Dimmer
      selector:
        device:
    entities:
      name: Light entities
      description: Light entities to control.
      selector:
        target:
          entity:
            domain: light

trigger:
  - device_id: !input dimmer
    domain: zha
    platform: device
    type: remote_button_short_press
    subtype: turn_on
    id: turn_on
  - device_id: !input dimmer
    domain: zha
    platform: device
    type: remote_button_long_press
    subtype: dim_up
    id: dim_up_long
  - device_id: !input dimmer
    domain: zha
    platform: device
    type: remote_button_long_press
    subtype: dim_down
    id: dim_down_long
  - device_id: !input dimmer
    domain: zha
    platform: device
    type: remote_button_short_press
    subtype: dim_down
    id: dim_down
  - device_id: !input dimmer
    domain: zha
    platform: device
    type: remote_button_short_press
    subtype: dim_up
    id: dim_up

action:
  - choose:
      - conditions:
          - condition: trigger
            id:
              - turn_on
        sequence:
          - service: light.toggle
            target: !input entities
            data:
              transition: 1
              brightness: 255
      - conditions:
          - condition: trigger
            id:
              - dim_up_long
        sequence:
          - service: light.turn_on
            target: !input entities
            data:
              transition: 1
              brightness_step_pct: 50
      - conditions:
          - condition: trigger
            id:
              - dim_down_long
        sequence:
          - service: light.turn_on
            target: !input entities
            data:
              transition: 1
              brightness_step_pct: -50
      - conditions:
          - condition: trigger
            id:
              - dim_up
        sequence:
          - service: light.turn_on
            target: !input entities
            data:
              transition: 1
              brightness_step_pct: 10
      - conditions:
          - condition: trigger
            id:
              - dim_down
        sequence:
          - service: light.turn_on
            target: !input entities
            data:
              transition: 1
              brightness_step_pct: -10
#

I restarted ZHA, and it became instantly unresponsive, some of my light are on, then they shortly turn off and turn on

#

Like there was a command stuck being broadcasted

#

I moved all my non philipps hue devices in a secondary network, the issue persists

#

I don't know if it's a configuration issue or a faulty device

full beacon
#

I think the issue is caused by Philipps hue wall switch

#

For an unknown reason they keep emitting even every now and then

#

"hold event"