sl_Status.ZIGBEE_MAX_MESSAGE_LIMIT_REACHED: 3075

[dmarkscouk]

The problem

Hello,

I'm repeatedly getting the following issue:
sl_Status.ZIGBEE_MAX_MESSAGE_LIMIT_REACHED: 3075

Looking on Google I see others are having the same issue also.
It tends to happen in my office more than other areas of the house... Each room has a presence sensor. Most rooms work at 99% reliability. My office works at 70% reliability either not turning on the lights, or leaving them on. When I go to automation traces to find out what went wrong I get the following issue sl_Status.ZIGBEE_MAX_MESSAGE_LIMIT_REACHED: 3075

I have 81 devices in my zigbee network with a fair few routers (highlighted in white below)

I have the zigbee sky connect dongle on the end of a usb extension cord.

My automation traces error:

Previously I was using helper groups to group lights together, and have since moved to zigbee groups. Both have the same issue.

What version of Home Assistant Core has the issue?

core-2024.12.5

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

ZHA

Link to integration documentation on our website

https://www.home-assistant.io/integrations/zha

Diagnostics information

config_entry-zha-01J42G1PXV70WRJR904N77FV5X.json

Example YAML snippet

alias: Auto Office Lights New
description: ""
triggers:
  - alias: LUX Low
    entity_id:
      - sensor.office_epl_illuminance
    below: input_number.lux_on_limit_office
    id: LUX Low
    above: 0
    trigger: numeric_state
  - alias: LUX High
    entity_id:
      - sensor.office_epl_illuminance
    id: LUX High
    above: input_number.lux_off_limit_office
    trigger: numeric_state
    for:
      hours: 0
      minutes: 0
      seconds: 10
  - entity_id:
      - binary_sensor.office_epl_occupancy
    to: "on"
    id: "On"
    trigger: state
  - entity_id:
      - binary_sensor.office_epl_occupancy
    to: "off"
    id: "Off"
    for:
      hours: 0
      minutes: 0
      seconds: 0
    trigger: state
conditions: []
actions:
  - choose:
      - conditions:
          - condition: trigger
            id:
              - "On"
        sequence:
          - action: light.turn_on
            metadata: {}
            data: {}
            target:
              entity_id:
                - light.nabu_casa_skyconnect_v1_0_office_spotlights_zha
          - if:
              - condition: numeric_state
                entity_id: sensor.office_epl_illuminance
                below: input_number.lux_on_limit_office
            then:
              - action: light.turn_on
                metadata: {}
                data: {}
                target:
                  entity_id: light.office_desk_lamp
      - conditions:
          - condition: trigger
            id:
              - "Off"
        sequence:
          - action: light.turn_off
            metadata: {}
            data: {}
            target:
              entity_id:
                - light.office_desk_lamp
                - light.nabu_casa_skyconnect_v1_0_office_spotlights_zha
      - conditions:
          - condition: trigger
            id:
              - LUX Low
          - condition: state
            entity_id: binary_sensor.office_epl_occupancy
            state: "on"
        sequence:
          - action: light.turn_on
            metadata: {}
            data: {}
            target:
              entity_id: light.office_desk_lamp
        alias: Turn on Lamp
      - conditions:
          - condition: trigger
            id:
              - LUX High
        sequence:
          - action: light.turn_off
            metadata: {}
            data:
              transition: 5
            target:
              entity_id: light.office_desk_lamp
        alias: Turn Off Lamp
mode: single

Anything in the logs that might be useful for us?

No response

Additional information

I want to cry, this is driving me crazy

[home-assistant]

Hey there @dmulcahey, @Adminiuga, @puddly, @TheJulianJES, mind taking a look at this issue as it has been labeled with an integration (zha) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of zha can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign zha Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

zha documentation
zha source
_{^{(message by IssueLinks)}}

[puddly]

Zigbee group commands are very chatty and shouldn't be sent very frequently. If you send more than one light command every couple of seconds, you'll start seeing things like this.

That being said, try to upgrade your coordinator firmware first: https://connectzbt1.home-assistant.io/firmware-update/

[dmarkscouk]

@puddly , thankyou for such a quick reply.

I've updated the firmware and will test it out and see if this helps. I'll let you know back here either way.

With regard to calling lights or lights groups more than once every few seconds; I don't think I am, but will also look into this to make sure.

Kind regareds.

[dmarkscouk]

So problems seem to have gone (thought only a day of testing). What I did...

• firmware updated on sky connect
• updated my automations to try and avoid sending more zigbee commands that are needed: where I was using presence detection, I suspect I was sometimes turning the lights on before they turned off (when presence detection briefly thought there was no one in the room, then detected presence again, turn on commands would be resent). I now have a condition to check the light is not on before asking if to turn on).
• adjusted settings on HACS Adaptive lighting (trying to reduce their commands and thus overloading the zigbee network)

Hopefully I won't be back on, but if issues continue, I'll repost here.

Thanks again @puddly