zigbee2mqtt
zigbee2mqtt copied to clipboard
Zigbee2Mqtt sometimes does not send any commands but recieves them
What happened?
I have a quite big zigbee2mqtt network with lot of main power devices and a Sonoff C2652 usb stick as the coordinator. Most of the time everything is working perfectly. In the last weeks two times I had a complete outage, where the zigbee2mqtt docker was running fine, but no devices where sending their state anymore nor could i turn on any lights. The last time it seems to happen about 5am today. In the log I can not see any error at this time happening, but what you can see is, that at around 5am no more messages of my plugs where send...
After restarting zigbee2mqtt docker container everything is again up and running.
What did you expect to happen?
No response
How to reproduce it (minimal and precise)
No response
Zigbee2MQTT version
1.36.1
Adapter firmware version
20230507
Adapter
Sonoff C2652P
Setup
Intel Nuc with Unraid, zigbee2mqtt in docker
Debug log
I probably have the same issue. Also quite large zigbee installation (~40 devices). Runs fine for days, suddenly I cannot send anything to a device nor do I get anything back. Restarting zigbee2mqtt did not help. Disconnecting the Sonoff ZBDongle-E and restarting zigbee2mqtt did help. Anything I can do to help troubleshooting ? Don't know exactly which update did bring this problem .. ~3 weeks now ...
Does any of you using the coordinator with the multiprotocol (Zigbee and Thread(Matter)) firmware? If yes, then you should change it to a Zigbee only firmware.
I am using the P version with the CC2652 chip... so I do not use a multiprotocol firmware ...
How can I get that information ? I did nothing special to the Sonoff stick ...
Similar (?) Issue - Using Front End trace any activity imposed by MQTT Client and managed any command like changing configuration or setting up different log Noone of the command sent to any device is performed.
same here..about 2/3 times per day
Is there a maximum number of devices the system can handle ?
Same issue on 1.36.1 with a Skyconnect dongle and 65 zigbee devices. I restored to zigbee2mqtt 1.35.3-1 and all is running fine again. so i think there is something in version 1.36 which cause the problem.
Also reverted to 1.35.3-1 and no issues so far ..
I have exactly the same problem since yesterday. Out of the blue, I cannot send anything. Sensors are working fine. Unfortunately I don‘t have a backup before 1.36.1-1 Is any suggestions?
It happened to a neighbour of mine today as well. So I can rule out a hardware problem. No lights can be switched any more. It seems more an more devices are going offline over time. For me it's Aqara LED Strip and all Ikea bulbs at the moment. I am using Zigbee2mqtt with HA OS on a Proxmox server.
I just tested the edge version in HA and it doesn't work as well.
It's definitive a problem that was not existent in 1.35.3-1. Running that version it works without any flaw, after updating to newer one it's a matter of hours until the problem occurs.
Strange that there is no (koenk) activity on this thread. It's clear there is a problem with version 1.36
maybe the title of the thread is misleading?
Does anyone have an idea how I could get 1.35 installed not having a backup?
Does anyone have an idea how I could get 1.35 installed not having a backup?
https://github.com/Koenkk/zigbee2mqtt/releases/tag/1.35.3
Thanks, but how would I get that into my homeassistant installation?
There is an update out (1.37) but i don't see any about this issue. So i don't know if it will fix the issue with not sending commands.
I'm still staying on 1.35 and will not update to 1.37 (i also read new problems with the newer version)
Well it doesn‘t fix my problem. Its the same. Only receive states, not send commands. But I see many different issues posted, that could be the same symptom.
Please send this information on this topic: https://github.com/Koenkk/zigbee2mqtt/discussions/22379
maybay they will pick it up quickly
It is trange this problem still exists in version 1.37 :/
I don‘t want to hijack topic #22379 since this is a complete different problem.
Ok, my issue is solved (sort of). It must be interference from one of my neighbours. I changed everything from channel 11 to channel 20 and all is working again (for now)