No extension cord but before the update it worked like a charm!
What kind of device do you use for HA? Does it have a wifi adapter build in?
Let us summarize
Your hue devices work. A cube works. Xiaomi sensors do not.
Xiaomi sensors have a reputation for having an issue with connecting to any other router than it originally connected to. A proper device will attempt to connect to a different router (like a lightbulb) or directly to the coordinator. It is most likely that all you need is to repair then. You do not need to remove then and add then again. Just ask Phoscon to add new device and go to the sensor and click the pairing button. Not factory reset. Just click the button. They will normally reconnect and become available again. You can also remove the battery and put it in again. That may also force then to reconnect.
I personally have the sensors branded Aqara and they do not seem to have an issue. It probably depends on firmware. Problem is in the sensors and it is also a problem on other systems than Deconz
One problem can be that you carry the sensors to your computer with the Conbee, pair then, and then carry then to a remote location. Because they refuse to reconnect to a light bulb in near then they may insist on being connected to the Conbee with a poor link. So always pair Xiaomi sensors where they are placed so they connect to a nearby router
And get 1 m USB extender cable for your Conbee. There is too much RF noise near any computer.
Does anyone know when this fix will be implemented ?? I have quite a lot of devices that’s not working right now, and it looks like it fixed here:
I’m using the odroid as a system. The Xiaomisensors are Aqaradevices, so these are the same as yours.
I do not think RF noise is a problem at all, because everything worked before updating to 21.12.
In Phoscon all sensors are available.
Best regards,
Stefan
Please start with adding an extension cord.
I will give it a try but why should that happen just after upgrading and working for almost a year before?
Additionally i do have some hue bulb that act as repeater.
Quick update:
Everything back to normal. Problem was that all these devices have been deactivated.
I still have no idea why this happened during the update.
Thank you for all the support!
Deconz losing connection to Aqara devices has nothing to do with upgrade of Home Assistant. It is a coincidense. There are 10000s of users on HA and Deconz. There are 12 major releases of HA per year and more than 60 releases of HA when you include patch releases. And we all experience glitches with devices. I had an Ikea switch that lost connection yesterday for no good reason. It worked after repairing. Be careful with declaring cause and effect. Some of us will experience that Deconz or Zigbeejs2mqtt, ESPHome devices drops off the same day as a HA update even if the issue is not caused by the HA update.
Deconz is a software that runs as an addon and it did not get upgraded with the 2021.12 release.
1 Like
Sadly not, i’m using the deconz addon
Hi Kenneth, just by the way. Yes, sometimes, some Aquara devices will loose their connect, which normally can be easily reestablished. And yes, it is not related to HA upgrades.
But now, since the last update to 2021.11.x, I can not manage to reintegrate a lost Aquara motion sensor. So I bought a new hue motion device which cannot be paired as well. What could cause these issues? I’m using PhosCon on Conbee2 and deConz
So yes, as also mentioned by another user everything under “lights” in Deconz lost connection after updating HA again. I tried reloading Deconz as suggested but nothing happened. As always I used “add new device” and they popped right up again, but I just had to give them the same names again. So yeah, it sadly didn’t solve it 
And yes, I have my Conbee on an extension cord. And as mentioned all other sensors do not lose connection. Only everything under “lights”. And nothing was visible in my logs either. Any other ideas? Or where I should look for info in my system when it happens again?
Updated via deconz 6.10.0 => 6.11.0 via supervisor UI. This update bumps from v2.12.6 => 2.13.4
Result: None of the zigbee devices detected anymore . Deconz VNC shows the network, but Phoscon app does not find the gateway anymore.
Restored back to deconz 6.10.0 0 => everything works as expected.
What gives?
Running Raspbery Pi 4 4GB + HA OS, with latest updates
EDIT: gateway is Conbee II
2 Likes
Yeah I have the same issue 
same here: Pi 3B, HA OS and Conbee I
same here
HA Blue with conbee II
edit: restore to 6.10 .0 and it works again -
I got a little bit nervous 
1 Like
Same here
[s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] firmware.sh: executing... [15:35:34] INFO: GCFFlasher V3_17 (c) dresden elektronik ingenieurtechnik gmbh Path | Vendor | Product | Serial | Type -----------------+--------+---------+------------+------- /dev/ttyACM0 | 0x1CF1 | 0x0030 | DE2194613 | ConBee II /dev/ttyACM1 | 0x1CF1 | 0x0030 | | ConBee II /dev/ttyUSB0 | 0x0403 | 0x6001 | AO3RXEHS | Generic FTDI [cont-init.d] firmware.sh: exited 0. [cont-init.d] nginx.sh: executing... [cont-init.d] nginx.sh: exited 0. [cont-init.d] novnc.sh: executing... [cont-init.d] novnc.sh: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. [15:35:34] INFO: Websockify waiting for VNC to start [15:35:34] INFO: Running the OSRAM LEdvance OTA updater... [15:35:34] INFO: Running the IKEA OTA updater... [15:35:34] INFO: Running the deCONZ OTA updater... [15:35:34] WARNING: Your direct VNC access is not protected! [15:35:34] INFO: Starting VNC server (local/no)... [15:35:34] INFO: Starting websockify... WebSocket server settings: - Listen on 127.0.0.1:5901 - Flash security policy server - Web server. Web root: /usr/share/novnc - No SSL/TLS support (no cert file) - proxying from 127.0.0.1:5901 to 127.0.0.1:5900 [15:35:37] INFO: deCONZ waiting for VNC to start [15:35:37] INFO: Starting the deCONZ gateway... libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile [15:35:38] INFO: Starting Nginx... 2021/12/20 15:35:38 [notice] 314#314: using the "epoll" event method 2021/12/20 15:35:38 [notice] 314#314: nginx/1.14.2 2021/12/20 15:35:38 [notice] 314#314: OS: Linux 5.10.83 2021/12/20 15:35:38 [notice] 314#314: getrlimit(RLIMIT_NOFILE): 1048576:1048576 2021/12/20 15:35:38 [notice] 314#314: start worker processes 2021/12/20 15:35:38 [notice] 314#314: start worker process 1457 15:35:37:841 HTTP Server listen on address 0.0.0.0, port: 40850, root: /usr/share/deCONZ/webapp/ 15:35:37:854 COM: use stable device path /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2194613-if00 15:35:37:864 COM: /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2194613-if00 / serialno: DE2194613, ConBee II 15:35:37:864 ZCLDB init file /data/.local/share/dresden-elektronik/deCONZ/zcldb.txt 15:35:37:890 found node plugin: libde_signal_plugin.so - Signal Monitor Plugin 15:35:39:804 found node plugin: libstd_otau_plugin.so - STD OTAU Plugin 15:35:40:826 COM: /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2194613-if00 / serialno: DE2194613, ConBee II 15:35:42:292 Device firmware version 0x26720700 ConBee II 15:35:42:301 unlocked max nodes: 512 15:35:42:414 Device protocol version: 0x010E 15:35:42:496 Current channel 15 15:35:42:524 CTRL ANT_CTRL 0x03 15:35:42:528 CTRL ZDP_RESPONSE handler 0x0001 15:35:42:567 Device protocol version: 0x010E 15:35:42:671 CTRL ANT_CTRL 0x03 15:35:42:674 CTRL ZDP_RESPONSE handler 0x0001 parse error: Invalid numeric literal at line 1, column 34 15:36:37:812 Device TTL 4789 s flags: 0x7 15:37:37:810 Device TTL 4729 s flags: 0x7 15:38:37:812 Device TTL 4669 s flags: 0x7 15:39:37:814 Device TTL 4608 s flags: 0x7
Same issue