Zigbee now slow or stopped
The problem
Latest updates on HA OS and Core yesterday. ZigBee noW intermittent to stopped. Apologies if all needed info not provided, I am new at this. Please let me know right way to submit. Thank you.
What version of Home Assistant Core has the issue?
2025.4.2
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
Zigbee Home Automation
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
Anything in the logs that might be useful for us?
Logger: homeassistant.components.automation.garage_rocket
Source: components/automation/__init__.py:738
integration: Automation (documentation, issues)
First occurred: 8:56:54 AM (2 occurrences)
Last logged: 9:08:48 AM
Error while executing automation automation.garage_rocket: Failed to send request: Failed to enqueue message: <sl_Status.ZIGBEE_MAX_MESSAGE_LIMIT_REACHED: 3075>
Logger: homeassistant.components.automation.garage_rocket_radio_eyeball_outlets
Source: helpers/script.py:2057
integration: Automation (documentation, issues)
First occurred: 8:40:52 AM (5 occurrences)
Last logged: 8:53:36 AM
Garage -Rocket, Radio, Eyeball outlets on: Error executing script. Error for device at pos 1: Failed to send request: Failed to deliver message: <sl_Status.ZIGBEE_DELIVERY_FAILED: 3074>
Garage -Rocket, Radio, Eyeball outlets on: Error executing script. Error for device at pos 1: Failed to send request: Failed to enqueue message: <sl_Status.ZIGBEE_MAX_MESSAGE_LIMIT_REACHED: 3075>
Additional information
No response
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 closeCloses the issue. -
@home-assistant rename Awesome new titleRenames the issue. -
@home-assistant reopenReopen the issue. -
@home-assistant unassign zhaRemoves the current integration label and assignees on the issue, add the integration domain after the command. -
@home-assistant add-label needs-more-informationAdd a label (needs-more-information, problem in dependency, problem in custom component) to the issue. -
@home-assistant remove-label needs-more-informationRemove 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)
Can you download diagnostics for the ZHA integration and attach the JSON here?
ZIGBEE_MAX_MESSAGE_LIMIT_REACHED sounds like you have an automation running group commands, which will clog up the network. What adapter are you using and what firmware are you running?
Thanks very much!
Adapter, if I understood correctly is SONOFF Zigbee 3.0 USB Dongle Plus V2. I do not see how to check the firmware…will research if you direct.
Good day, didn't want to flood useless information… Could I ask you for more direction on what the adapter is, so I can get you the firmware version?
Thank you again.
That info is in the diagnostics you uploaded: SONOFF Zigbee 3.0 USB Dongle Plus V2, running firmware 6.10.3.0 build 297.
Are you using Zigbee groups to control your devices? Or are you turning individual ones on/off?
Thanks very much!Individual on and off. On Apr 20, 2025, at 12:31 PM, puddly @.> wrote: That info is in the diagnostics you uploaded: SONOFF Zigbee 3.0 USB Dongle Plus V2, running firmware 6.10.3.0 build 297. Are you using Zigbee groups to control your devices? Or are you turning individual ones on/off?—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.>
puddly left a comment (home-assistant/core#143092) That info is in the diagnostics you uploaded: SONOFF Zigbee 3.0 USB Dongle Plus V2, running firmware 6.10.3.0 build 297. Are you using Zigbee groups to control your devices? Or are you turning individual ones on/off?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>
I can see my comment was not well formatted, I'm using individual on/offs in an automation that's triggered by a motion
Having the same issue. I can also add that I can only add new devices in range of the main coordinator now. It will not connect to other routers or on-power devices, not even when trying to "add devices via this device". I also had the issue that the NWK is cycling, but I was able to fix that by updating the main coordinator to Z-Stack 20240710. Devices outside of the main coordinator range also keep dropping off the network.
EDIT: furthermore, various plugs and switches no longer respond when i try to turn them on or off via home assistant, but instantly update when i press the physical button, so reading info works, but setting info doesnt. the issues are all outside of the coordinator range in my garden, but the zigbee network is dense enough with 4 dedicated sonoff routers.
I had exactly the same error message, when trying to toggle my brand new Ikea inspelning smart plug. And I solved the problem with a power cycle of my home assistant controller (with the SONOFF Zigbee 3.0 USB Dongle Plus V2).
A few years ago I had a flaky zigbee stick, which I had to power-cycle quite often to get it running again. Note just a reboot of the controller wasn't enough, it really needed to discharge completely.
I hoped this erroneous behavior would be solved with the SONOFF stick, but unfortunately, it seems to have the same issue :(
Thanks Ronald. I tried and tried. Took the plunge to Matter 🤦🏻♂️On Jun 18, 2025, at 8:06 AM, Ronald Hiemstra @.***> wrote:RonaldHiemstra left a comment (home-assistant/core#143092) I had exactly the same error message, when trying to toggle my brand new Ikea inspelning smart plug. And I solved the problem with a power cycle of my home assistant controller (with the SONOFF Zigbee 3.0 USB Dongle Plus V2). A few years ago I had a flaky zigbee stick, which I had to power-cycle quite often to get it running again. Note just a reboot of the controller wasn't enough, it really needed to discharge completely. I hoped this erroneous behavior would be solved with the SONOFF stick, but unfortunately, it seems to have the same issue :(
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>