I have 9 Aqara door/window sensors, 4 Aqara vibration sensors, and 1 Aqara multi-sensor. For many months they have been rock-solid and among my most reliable devices. In the past few weeks, they fail to remain connected to the Conbee II network. I have repeatedly deleted, and re-added the sensors in Phoscon and read all clusters, node descriptor, and simple descriptors in the deconz GUI. I have followed the directions at Xiaomi: Lost devices or functional issues multiple times. The sensors will sometimes reconnect for a short time and then disconnect. When they disconnect, the cluster info in the Deconz GUI for the basic cluster is typically blank. I have also tried changing the zigbee channel from 11 to 25, but that did not resolve the issue.
Steps to reproduce the behavior
Add Aqara sensors to network using Phoscon and Deconz GUI and wait for them to lose connection to deconz.
Expected behavior
The sensors should stay connected to deconz.
Screenshots
Environment
Host system: Synology DS718+
Running method: Marthoc Docker container
Firmware version: 26720700
deCONZ version: 2.12.06 / 8/19/2021
Device: ConBee II
Do you use an USB extension cable: yes
Is there any other USB or serial devices connected to the host system? If so: Which? APC UPS
I may have solved it by modifying the docker container to run with high privileges. All of my Xiaomi devices have neighbour links now. I’ll monitor and update this thread after a few days.
Here is a link to some log excerpts. I don’t really know what I am looking for and the entire log is too large for Pastebin (even if I had a paid account), so if there are some specific log entries you would like to see, let me know what keywords I should be looking for. Thanks!
EDIT: I lost the vibration sensor in my office chair within the last half hour. Here’s a link to some more logs
When I went to re-pair all of the sensors this morning, I saw that only some had dropped out and others did not need re-pairing. The ones that had dropped out had lost their neighbour link in deconz gui (see attached screenshot). Some have since reconnected to a router and some have not. I think if they do not get a neighbour link to a router within an hour they will drop out and I’ll have to re-pair them again.
Yes. Some of the Xiaomi sensors directly connect to the Conbee II, whereas some of them connect to a different router (either a Tradfri bulb or a Sinope Thermostat). It doesn’t seem to affect which sensors drop out - even those directly connected to the Conbee drop out even though the Conbee doesn’t become unavailable.
Do you have any ideas as to why this is happening? Or is there anything in the logs that you think will shed light on it? I have had the Aqara sensors for around a year and they have been very reliable up until within the last month. Since then I have updated both the Conbee firmware and deconz to the latest versions. I haven’t made any other changes to my setup.
IN my experience the older Xiaomi sensors have a problem when their parent device, e.g. a light or the coordinator isn’t powered for a few hours, when it sometimes, but not always, happens they go into some hibernate mode and stop sending.
What I usually do is to press the small button on the sensor 5 times, when they try to reconnect to the parent. This often works, the biggest problem with the old sensors is that they stick to a parent and most of the time won’t automatically search for a new parent, for example in case a light is switched off physically.
The new Xiaomi/Aqara devices appear to not have this issue anymore.
