Failed to deliver message: <sl_Status.ZIGBEE_DELIVERY_FAILED: 3074> #124516
Comments
|
Hey there @dmulcahey, @Adminiuga, @puddly, @TheJulianJES, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) zha documentation |
|
I'm having the same issue. I have a group of Ikea blinds that I control. Some of the blinds are triggered, but some are not. The logs show the same error |
|
This will likely be improved by zigpy/bellows#646 (in the next beta) if your devices are battery operated. Note that nothing changed between 2024.8.1 and 2024.8.2 (and in many many months beforehand) so any issues you're experiencing are with your environment. |
|
My environment has not changed in many months. This issue started after the upgrade to 2024.8.2. And, yes, my devices are battery operated |
If you haven't changed the stick firmware, something in your RF environment has changed. It doesn't mean that you changed something, just that it has changed. New neighbors (or old neighbors who added new equipment), wifi router moved its 2.4GHz network channel, temperatures changed and your device's battery voltage has dropped, new SSD nearby, etc.
They may have started at the same time but if you downgrade to 2024.8.1, things will remain exactly the same. |
|
I will say, that my environment did change in that in addition to my existing Silicon Labs Sonoff Zigbee dongle, I added a new Nortek Z-Wave/Zigbee to take advantage of the Z-wave frequency (the Zigbee is not active on the dual-device). It may have been coincidental that when I did so, I started to get the error, but yesterday I added a 10' USB extension cable to the Z-wave dongle (the Sonoff already had one) and I haven't had the error 3074 in over 24 hours. It could be a coincidence and I'll certainly keep this thread updated, but it's worth noting. |
|
I have also had this error pop up on IKEA battery operated blinds out of nowhere today. I haven't added or changed my zigbee devices in any way. They just refuse to communicate at all |
|
Just got it again after not seeing it for over 24 hours - Error while executing automation automation.new_automation_closet: Failed to send request: Failed to deliver message: <sl_Status.ZIGBEE_DELIVERY_FAILED: 3074> |
|
Yes, also getting these starting yesterday. No network changes. There are enough people having this that rules our typical device incompatibility. |
|
I started receiving these errors after upgrading as well. No other changes, this doesn't seem to be a coincidence that others are experiencing the same issues. I will mention that the devices I'm seeing as failing are Sengled light bulbs, not battery powered. |
|
Also started getting this in the last few days. No changes in months to zigbee devices. |
|
As mentioned above, there have been no changes to ZHA in the past few releases. More fundamentally, however, ZHA does not have control over routing to your devices. It asks the stick to send a message and the stick responds with the status code you're seeing. If this changed all of the sudden, this is 100% a result of your environment. You can verify by downgrading HA Core. That being said, if downgrading helps, please enable ZHA debug logging, leave it running for half an hour and toggle some devices to generate log data, and disable debug logging to generate a log. Please do this on a version that works and one that does not and we can see what the difference is between the logs. |
|
Just here to say I experienced very similar symptoms:
I have seen other similar reports eg https://community.home-assistant.io/t/connection-problems-with-zha/762314 Seems too widespread to just be a coincidence for all of us. I'll try to get some logs to post. |
|
Also chiming in here with the same issue. Was not seeing this until upgrading to I keep getting Zigbee requests sort of "pooled together" after a few minutes when trying to turn lights on and off. Then they all of a sudden execute and this error pops up. |
|
FWIW, I rolled back to I have an issue running my script with a Zigbee button to toggle some lights for some reason which hits this error:
I'll go to execute this script, then it won't work. So I'll go into Home Assistant to toggle the same lights, then that "pooling" action will happen and the lights will just turn on and off and on and off, etc.. Have also been getting a lot of zigbee devices notifying me they've gone "unavailable" suddenly |
|
I just downgraded to |
|
Can you generate a debug log by enabling debug logging for ZHA, reloading the integration, and letting it run for half an hour while doing what you can to trigger the issue? Without a log from each version, it's hard to see what's different. |
|
Sure thing I can try to get you something hopefully soon. On the |
|
Both of them, if you could. One alone won't show what changed. |
|
Here is my last log of it occurring from just today - Logger: zigpy.zcl |
|
A bit more information: I tried replacing the Nabu Casa SkyConnect with an old Sonoff Zigbee 3.0 USB stick, rebuilding my network from scratch. The flakiness and 3074 errors have disappeared. So, at least anecdotally this may be an issue specific to the SkyConnect stick. |
I have the issue with Sonoff Zigbee 3.0 USB stick. It's likely to pop up for you again. |
Sent you over the logs on Discord. Of course, after I did the logging on When going from
|
|
I have to say, I have not encountered this issue in a while. I have not changed anything about my environment and I am still on |
|
Same with me. Over the weekend I was getting this everywhere, for no reason. I rebooted, both soft and hard. I "reconfigured network". I removed and readded devices. Nothing worked. |
|
Just received it for the first time today. Funny thing is, I checked the time of the error and my log doesn't indicate any attempted contact with a Zigbee device at such time. Logger: zigpy.zcl [0x7B00:1:0x0020] Traceback (most recent call last): File "/usr/local/lib/python3.12/site-packages/zigpy/endpoint.py", line 265, in request return await self.device.request( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/zigpy/device.py", line 339, in request await send_request() File "/usr/local/lib/python3.12/site-packages/zigpy/application.py", line 833, in request await self.send_packet( File "/usr/local/lib/python3.12/site-packages/bellows/zigbee/application.py", line 825, in send_packet raise zigpy.exceptions.DeliveryError( zigpy.exceptions.DeliveryError: Failed to deliver message: <sl_Status.ZIGBEE_DELIVERY_FAILED: 3074> The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/local/lib/python3.12/site-packages/zha/zigbee/cluster_handlers/general.py", line 643, in check_in_response await self.checkin_response(True, self.CHECKIN_FAST_POLL_TIMEOUT, tsn=tsn) File "/usr/local/lib/python3.12/site-packages/zha/zigbee/cluster_handlers/init.py", line 83, in wrapper with wrap_zigpy_exceptions(): File "/usr/local/lib/python3.12/contextlib.py", line 158, in exit self.gen.throw(value) File "/usr/local/lib/python3.12/site-packages/zha/zigbee/cluster_handlers/init.py", line 75, in wrap_zigpy_exceptions raise ZHAException(message) from exc zha.exceptions.ZHAException: Failed to send request: Failed to deliver message: <sl_Status.ZIGBEE_DELIVERY_FAILED: 3074> |
|
this morning I have: and left it at that .. let's see how I go |
|
How does one update just the Core? I tried to restore from a partial backup with an old version and lost a lot of my changes I made. |
No I updated my HA core python virtual environment with that specific version using something like the following: FWIW still not seeing this error again over the weekend. Will update to the next version whenever that’s out and see if it comes back. |
|
Well, my downgrade, and upgrade didn't work. |
|
couldn't turn my lights off this morning. |
Perform these steps and attach debug logs. |
This is an automatic reply to a check in from the device. There are 0 functional issues from this particular log and it is safe to ignore. |
Ditto with this one. Safe to ignore |
These are also a non issue |
|
On a positive note, it's been about 48 hours without an error (did I just jinx it). |
|
@dmulcahey can you confirm that this is a new message (sl_Status.ZIGBEE_DELIVERY_FAILED: 3074) since bellows 0.40.0 which was bumped into zha 0.0.30 coming with HA Core in 2024.8.1 So that we are not insane 😅 and this message couldn't be seen prior? |
this has been happening all along. The only thing that changed is the actual error constant: <EmberStatus.DELIVERY_FAILED: 102> became <sl_Status.ZIGBEE_DELIVERY_FAILED: 3074> other than that this has been happening for years and it is innocuous. You can search closed issues if you don't believe me.
The cause is the stack failed to deliver the message. There is nothing we can do about that. |
|
I too have massive problems with zha (Skyconnect stick on an extension cable) since updating to 2024.8.3 / 13.1... Is it safe to downgrade to an older version? |
|
Okay so I’ve been running 
|
|
My zigbee is dead. Home assistant sometimes recognize state of entity but I cant control anything. Reboot sw or hw not helping. They are not battery device which I jlhave problem. My smart home is totaly useless. I dont know what to do... Logger: homeassistant.components.websocket_api.http.connection [140387397687120] Unexpected exception The above exception was the direct cause of the following exception: Traceback (most recent call last): The above exception was the direct cause of the following exception: Traceback (most recent call last): |
|
Not cool that I can't turn my lights off at night. |
|
Just wanted to also add the issues since the recent Home Assistant upgrade, My IKEA devices (mainly switches) either don't respond or very delayed. and get the sl_Status.ZIGBEE_DELIVERY_FAILED: 307 error Edit: Also worth adding that my thermostat is affected as well. It is very difficult to adjust the settings on it....and winter is coming. |
|
As per request. debug logging turned on |
|
+1 started getting this issue out of the blue 2024.9.1 hopefully it was a one time thing. |
I've experienced this kind of errors while using OTA with ZHA. Downgrading HA did not help that much. Since I've updated the Firmware of my SkyConnect the connection seems to be stable. |
|
For anyone commenting on this issue with logs, please generate them as shown below. The tracebacks you see in 
|
|
couldn't turn my lights off this morning from a slave switch (a zigbee switch that isn't wired directly to the lights circuit - _TZ3000_ugaem1nb): |
|
I seem to have the same problem. First I thought it was down to the quirk I used for one particular Aqara light, but after disabling quirks the problem (slow/failing zigbee network after a couple of hours) still persists. Only restarting the ZHA integration or HA all together helps. Context information: Home Assistant: ZHA with Sonoff Zigbee 3.0 USB Dongle E (EFR32MG21) see also: https://github.com/home-assistant/core/issues/125789#issuecomment-2347326713 |
|
Coming back to this, still on |
|
I've not received this error now in over a week. I did change the channel of my ZHA Hub to 24. The error just eventually stopped showing up. Perhaps it was interference that has now somehow subsided. Not completely sure. |
|
Did a restart of ZHA and ran a debug log for a couple of hours and stopped it when ZHA became unresponsive again. Requests are getting queued and are running delayed? Have the full log file available if needed, but it is 62 MB... |
|
Zip the log and attach it here |
I would stay away from channel 24. It overlaps directly with WiFi channel 6 and if you have any APs in the vicinity that can automatically pick channels, it's only a matter of time before it does.
From your log, there is a constant stream of network address requests coming from a couple of devices on your network (mostly Please open a separate issue and attach the same log file, your issue isn't related to this one. |
and others
The problem
Never had an issue and now I'm getting the following error on various Zigbee devices - Failed to deliver message: <sl_Status.ZIGBEE_DELIVERY_FAILED: 3074>
What version of Home Assistant Core has the issue?
core-2024.8.2
What was the last working version of Home Assistant Core?
core-2024.8.1
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Zigbee
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
This has occurred sporadically over the past few days. I did add a Nortek dongle along with my existing Zigbee dongle, but even after unplugging it I'm still getting this error.
The text was updated successfully, but these errors were encountered: