Devices unavailable after Conbee to SkyConnect migration #86231
Comments
|
Hey there @dmulcahey, @Adminiuga, @puddly, 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 |
|
Please download diagnostics for the ZHA integration after letting it run for a few hours:
|
|
Aqara sensors becoming unavailable is not unusual: when joining a network, they pick the very first parent they detect, which rarely is a physically close one. If they picked good parent (at random) when joining your Conbee network but picked a bad one with the new network, that would be an issue. You can force them to pick a new parent by re-joining them to your network via a specific, physically-close routing device:
Is your SkyConnect in exactly the same position as the Conbee, plugged into the exact same USB extension cable? Is it away from USB 3.0 devices, SSDs, 2.4GHz routers, etc.? |
|
I can confirm this bug report. I have 8 Aqara water sensors and 2 temperature sensors. I've been using ZHA with a Conbee II USB stick (latest firmware) for a couple years without issues. Using 2023.1.3 all my sensors were working. After upgrading to 2023.1.5 none of the Aqara sensors will not stay connected for longer than a few hours. I have 76 total zigbee devices (Jasco, SmartThings, Centralite, Aqara) with a large number of them being routing devices. Looking at the ZHA device map, none of the Aqara devices are showing connections to any routing device or the coordinator. They're just kind of floating. I went through and removed and re-paired all the Aqara devices using the "Add via this device" on the closest routing device (typically 5-15 ft total distance with no walls). Unfortunately, that didn't help. All the devices went to unavailable after the ZigBee battery timeout found in the ZHA configuration settings. For more debugging I swapped in a Sonoff ZBDongle Plus E for the Conbee II, but I get the same result. Tonight I'll try reverting to an older version of HA Core. System Details:
|
|
Joining aqara through any router won't work. You have to join it only through an aqara compatible router. There was a list somewhere on the forums |
I already tried this method, it doesn't help
Yes, everything the same and away of routers, SSD and so on |
It is not only affecting aqara. Ikea Bulbs, Motion Sensors and so on are also affected |
|
today I had again some unavailable devices, re-joined them with bulbs nearby (as you suggested) . |
I can confirm. I have been having nothing but issues with my hue motion sensors since switching to the skyconnect. |
|
HUE motion sensors (i have 2 in production system) is real jumpers and is in the end using the worse parent they can but then they is being stable. I think you need having some router around them so they can doing there jumping thing or they is leaving the network. You have one very long issue in Z2M with the problem Koenkk/zigbee2mqtt#2693. |
as I have already written, there have been no problems at all with Deconz |
|
I cannot confirm when my zigbee devices stopped working, but it was since Jan 1 2023. Every day I have a different set of Aqara motion sensors, zigbee switches and other zigbee devices that become unavailable. I tried some ikea plugs to use as routers but that didn't make any difference. Wish I seen this thread earlier as I assumed the problem was my house just couldn't handle zigbee and I have been busy returning my zigbee stuff and migrating to yolink. The only devices that haven't gone off line at some point in the last month were those within 2m of the stick (with no walls). An Aqara motion sensor about 4m away (1 simple wall) goes off line intermittently. Beyond that, my devicers come "online" intermittently. I am using a sonoff zigbee 3 stick. I did try moving it from usb3 to usb2, I tried a 1 m and a 2 m extension cable with multiple different locations for the stick. None of this had changed prior to the disconnect issue arising, but I was going through various trouble shooting scenarios so decided to try this. The timing of my issues does seem to correlate with the revision history discussed above in this thread. These devices were relatively solid last year (Aug - Dec 2022) I'm running HA 2022.1.7 on a Raspberry Pi |
|
I'm also having multiple sensor dropping off as late. Usually the Samsung Centralite ones, I've been lucky with my Aqara ones by the sound of it. I'm unable to get one of the Samsung sensors working again as well despite re-pairing it, it also won't go through a re-configure. I couldn't tell you what version exactly it started but I've had Philips hue bulbs dropping off which has never happened in the last 2 years of using Home Assistant, so to me something is definitely wrong. Hope it gets fixed soon as before long I'm likely to fall down the stairs in the dark. |
|
Alright, I've been doing some testing and researching all weekend... Here's my findings. TL;DR; Full History & Troubleshooting: Upgraded to HA Core 2023.1.5. All of a sudden multiple Aqara sensors went unavailable, but others stayed connected. I was in this state about a week, so I purchased the Sonoff ZBDongle Plus E after reading a few forums (should have read more). Used the ZHA migration to switch to the Sonoff dongle and everything seemed good, but by the next morning ALL the Aqara devices were unavailable. I've been trying to force specific routing devices to the Aqara sensors (like mentioned in an earlier post) while using the Sonoff dongle. Turns out that neither the Jasco/GE nor the Centralite routing devices I have are Aqara friendly. Connecting the sensors to those devices or the Sonoff dongle directly will not result in a stable connection. I tried reverting back to HA Core 2022.12.9, but got the same results. Decided I wanted to use the new Zigbee 3.0 stick instead of the old Conbee II, so I investigated using both sticks at the same time. First, I completely rebuilt the Zigbee network from scratch using the Sonoff dongle and ZHA (this took a long time) to make sure my ZHA setup was up-to-date/clean. I left the Aqara sensors disconnected. Using deCONZ/Phoscon I was able to add all the Aqara sensors. It correctly identified them and even had a pretty image of the device. In HA I then refreshed the integration and all the sensors showed up. My HA has been sitting this way for over a day now. I've had no unavailable devices on ZHA or deCONZ/Phoscon. Reviewing the history for the Aqara devices I can see that they're periodically updating (temperature graph shows changes). So.... there's my solution to the problem... Not pretty or optimal, but functional. I now have 2 Zigbee networks. One on the Sonoff ZBDongle Plus E running ZHA and one on the Conbee II running Phoscon/deCONZ that I'm only putting Aqara devices. After reviewing LOTS of forums, I believe that there are some Aqara devices that will work with non-Aqara Zigbee 3.0 routers/coordinators, but it appears that the temperature/weather and leak sensors are not in that list. It sounds like this is due to an older method of keep alive used by Aqara vs the Zigbee 3.0 protocol. Essentially, if you have a deconz coordinator and are using ZHA then Aqara devices should work (and has for me for years), but something in the new 2023.1.x versions is causing it to no longer work (guessing route optimization and updated reporting configuration). Going to keep watching for updates on the issue, but given I've spent many hours troubleshooting/debugging this issue on my setup I'm out for now. |
|
Rasp/CprnBee is one very dominant and normally is all end device having it as parent = good and bad. EZSP is working little different and is normally no problems if the devices is working as Zigbee devices shall doing but Aqara is not doing it. And the problem is that EZSP is restarting its not knowing if some sleepers is being its children and they must pulling its parent OK after restart for being OK. I was 3 week on holiday with the laptop and coming back and connecting it and in one hour is all device online also all 10 Aqara sensors then they have routers online and was working well without the coordinator being online for out of house time. Is up to you building one star network or one mesh network but Zigbe shall being one mesh network for healing and working OK. |
|
I wanted to comment that my HA set up has been unstable since recent updates. Everything seems to work fine after a reboot, with the exception of my Zigbee aqara sensors. Sometimes none of them connect after the reboot, sometimes some of them do. But eventually all of HA locks up, all devices (aqara plus everything else) go offline, and I have to manually turn off the Pi and back. I am investigating on how to get logs, in case that can be of help. Is there any private info in these logs that I need to remove first? |
|
I'm also in everyone situation I buyed a ZBDongle Plus E, but my aquara devices doesn't stay connected: temperatures are a bit stable, but botton and magnetic door switch not even a tiny bit..
Could you link even in private some resource where you find information? I have 25days before I can return the device ( thanks Amazon ) and I refuse to keep two network and use my old cc2531.. |
|
I switched from Conbee 2 to SkyConnect (Both ZHA). I am having the same issues. Chiefly with IKEA shortcut buttons and 2-button controllers. I also have some issues with aqara contact sensors (but they were quite unreliable before). On at least one of the shortcut buttons even after I re-join it to the network clicks don't produce events - almost as if it has become immediately unavailable (pending the time out). Last Seen doesn't update. I have my SkyConnect connected to the same USB2 extension cord that I had used for the conbee stick. RPI3B+ on HAOS. Edit: I have transitioned back to the ConBee II and the devices are working well now |
|
Copying this comment from another issue ticket, seems to be a duplicate of this one but this seems like the most active so I'm going to try and following here: "Same problem here, just migrated from Deconz / Conbee II to ZHA / SkyConnect. Hue motion sensors get "stuck" in some state, occupancy may be either true or false but they never change. Require a re-pair to get them working again. Aqara magnet sensors seem to either stop sending updates or just become unavailable. This can happen twice a day on some of these devices. Latest HA version, latest SkyConnect firmware." Everything was stable on Deconz / Conbee II and had been for about 3 years. |
|
I switched back to Deconz / Conbee and everything works fine. |
|
Before even starting to troubleshoot any problems with those kinds of symptoms I always highly recommend following this in-depth best practice guide regarding reception optimization and interference avoidance -> https://community.home-assistant.io/t/guide-for-zigbee-interference-avoidance-and-network-range-coverage-optimization/515752/ As well as in addition a switch/change to using a less noisy Zigbee channel (which is part of that guide) -> https://www.home-assistant.io/integrations/zha#defining-zigbee-channel-to-use Then also follow these other related best practices to at least re-pair your devices again in their final location after trying to take on all the suggested actions -> https://www.home-assistant.io/integrations/zha#best-practices-to-avoid-pairingconnection-difficulties Note that those are actions that you need to take regardless of which Zigbee Coordinator radio adapter and Zigbee gateway solution you use. If still have issues then you will need to enable debug logging and replicate the issue so that you can provide debug logs that show the exact time when the issues occur. Again, please understand and remember that all and any problems will be much easier to narrow down and troubleshoot if you have already taken actions to reduce any sources of interference and changed to a Zigbee channel with less noise. |
If you have read this thread carefully you will see it is not because of radio issues. |
|
I went from Deconz to ZHA and had similar issues at first. What I did was make sure all Aqara devices are paired close to the Co-ordinator so they don't try to pair through a router. I then put the Aqara devices in their place after they were paired and never had a problem again. I know that wasn't necessary with Deconz, so it may be a limitation with ZHA, but none of my Aqara devices have ever fallen iff the network after doing that. |
|
I'm also having issues with unavailable devices all over since the day I've switched from ConBeeII to SkyConnect -through ZHA both of them. It seems that something is very wrong with SkyConnect, because using ConBeeII did not give me this issue. The reason to change to SkyConnect was future Matter support and better support in general or of specific devices (like Aqara Plug). First the migration process went sideways having devices out of the zigbee network and then having to re-pair them again and again. I'll move back to ConBeeII. I hope the backup will work without having to re-pair 40 devices around the house. |
|
I want to report that I've had zero disconnects by using 2023.3.0b5. Except two TRADFRI repeaters which change from unavailable/available all day long, but without hurting any End Devices of the network which are connected to coordinator via them. It might be the connected End Devices that are put themselves to "power saving sleep" due to inactivity and thus the TRADFRI repeater itself. |
Can also confirm that this wasn't the issue for me. Both sticks were on the same USB 2 ext lead. WiFi access points on channels that don't overlap with Zigbee 15, commands still reached distant parts of the network with a similar reliability to the Conbee II. Issue was exclusively with battery-powered devices dropping off the network and/or having rapid battery drain. |
|
Likewise for me - I'm now ~5 days in with no dropouts from 5 SML003 Hue motion sensors whereas 13/14 Hue SML001 are unavailable. So seems that it's a subset of battery devices that are affected. |
|
Also, I do not know how to check if any firmware on the TRADFRI repeaters was silently applied OTA during the last 10 days or so. It might be a parameter that we've missed. I've IKEA OTA enabled on configuration.yaml. I will search for an official online release list of IKEA firmwares. |
FYI, @MattWestb tries to maintain an unofficial release list of IKEA Zigbee OTA files under zigpy discussions -> zigpy/zigpy#660 |
|
Well, I can say after reverting back to a backup from 2 days prior to the Skyconnect migration didn't help. The problem persists between ZHA and zigbee2mqtt, even with an updated firmware on the Sonoff stick. The problem: All 3 motion sensors are simply not connecting to the rest of the zigbee network, despite correctly reporting occupancy under devices. They can't be used to trigger automations. |
|
Hello, another update from my side. After the problem did not reoccur after update to 2023.2.5 since days. I decided to restore my full backup/snapshot of the VM in Proxmox to the point where problem existed in the first place. Result: Still no problems since two days... As I wrote before the measured humidity values are changing all the time, so the sensor may not go to sleep, which can be the problem. I keep the debug logging active and will wait for the problem to reoccur. |
|
@TheFelix93 Is your sensor connected to one router or the coordinator for the moment ? |
Directly to the coordinator "ZNP = Texas Instruments Z-Stack ZNP protocol: CC253x, CC26x2, CC13x2" |
|
Just installed |
|
Well, I got a chance to run a couple of tests again and for some stupid reason my issue is now resolved. |
FYI, Zigbee Coordinator radio adapter and antenna orientation is covered here -> https://community.home-assistant.io/t/guide-for-zigbee-interference-avoidance-and-network-range-coverage-optimization/515752/ |
|
@puddly i don't mean to pester, but since you mentioned being a maintainer related to ZHA I thought it ok to ping you. Is this issue being looked into or is there any news to share? I keep coming over the same story - issues with ZHA and Sonoff/SkyConnect and Philips SML001 sensors (SML003 not affected) where the sensor drops out after some short (mins to 1 day) amount of time yet the rest of the network is stable. Also the same story that the user moved from some other platform to ZHA with one of these coordinators, previously the network was fine (same device positions) but now the network is seemingly broken. It seems something is fundamentally going wrong in many setups. In my case, I have 14 SML001 that keep dropping out. I've moved the coordinator (Sonoff E), it's already on an extension cable, I have 40 router devices (hue bulbs/lightstrips/plugs). I've tried changing channels twice (first to 20, which my Hue hub was using previously, then to 25 after inspecting Wi-Fi interference and researching good channels to use to co-exist with an Eero mesh Wi-Fi network). Nothing has made any meaningful difference, the behaviour of the devices on the network is fine except for the SML001 sensors. I'm concerned with what appears to be silence given the number of issues here and threads on HA forums - and aside from the usual (useful and well intentioned) advice to fix up the network fundamentals it seems no one knows what is going on. Are you able to provide any more info on this? I've spent a lot of time trying to figure this out (prob 10+ hours researching, tinkering, changing channels, pairing etc. This has taught me some useful stuff WRT zigbee network health, but I haven't solved the issue and now I'm considering moving back to my rock solid Hue hub (I literally had it under a sofa, on top of a pi, next to a stack of network switches, PSUs, modem, firewall and ring alarm system for the last year of it's life with no noticeable issues aside from speed of comms for automations from Hue > HA > NR > HA > Hue) or to try zigbee2mqtt. I have logs for the past few days, including channel switching if it's useful for debugging. Thanks in advance, and thanks for your work on the project! |
I have one of each on order and will see if I can replicate the problem on my network. Can you please open a new issue specifically for connectivity issues with the Philips SML001 with SiLabs coordinators (i.e. SkyConnect/Yellow/Sonoff E)? I'm afraid that these general "devices unavailable" GitHub issues become unmanageable after a while due to them aggregating so many unrelated problems (general network issues, problems with specific devices, other coordinator hardware, etc.).
How specifically did you switch channels? In the ZHA configuration page, does |
|
@lougreenwood Can you check the (To read them: Settings -> Integrations -> ZHA: Configure -> Devices -> select your SML001 -> three dots on the left -> Manage Zigbee device -> cluster -> select |
|
@puddly / @TheJulianJES - I created a new issue here and included the info you requested in that issue - thanks for your help! |
|
Just as a note, this issue seems to have mutliple tickets open under various titles, maybe need to combine them all as the issue is not just related to Hue SML001 or SML003 detectors. Hue RWL021 and RWL022 dimmer switches are affected and also Aqara Motion/light sensors, some Aqara Temp/humidty sensors and Tuya zigbee motion sensors. |
|
Same issue. Two of my four philips motion sensors constantly become unavailable and I have to remove and re-add them and one of them is 1m away from the skyconnect. |
|
@Ultra9k |
This is really my experience as well. I can't tell if it's down to a ZHA update or in my case the switch from a Conbee II Stick to a Skyconnect. In my case I have Hue RWL021, SML001 and some Aqara AQ2 motion sensors acting up recently. My routers are mainly Tuya TS011F wall plugs. Funny thing is, that I have some of these devices that are rock solid while others just refuse to work reliably no matter how many times I repair them. I also noticed that they don't seem to always get paired the same way. I have one AQ2 where it just has the entity "motion" while others have "Iaszone" as a motion entity. To be fair I thought it was all my mistake, as the Conbee II to Skyconnect migration was quite the disaster. (It failed to repair the devices as the ZHA migration process didn't respect the previous Zigbee channel and just decided to change it. And when I used a manual Zigbee backup it switched up all my identical devices on the network. So switch RWL021 A was suddenly switch RWL021 B and so on. This was especially messy with all my TS011F wall plugs which I used for my Energy Monitoring. Basically wiped all my cost history for the past months. But I guess as we always do, bit the bullet and rebuilt it. =] ) I'm glad to find out though that there is some larger problem here. Since I didn't get some of the Hue devices working reliably on the Skyconnect I switched them to the Hue Bridge. They're a bit slower now... but they work. One of the AQ2 is killing me though. It's like tossing a coin if it works or not. I'm at the point where I start betting with myself if it's going to work so I know it's time to ditch them. Don't know if I can wait for the fix of this. LOL I have the following threads atm.:
I wouldn't say it was 100% reliable with the Conbee II, especially some HUE RWL021 acted up similarly. But it's worse now. That's for sure. |
|
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
|
I still have some Sensors that turn unavailable regularly and need to be repaired, to work for some hours or days. It's happening with all latest software updates |
|
Author of the original issue is no longer using ZHA so there's no way to further debug. @pschneider87 The issue with your Hue sensors is unrelated. Take a look at #89311 (comment) for more info and for a potential fix. |
and others
The problem
I switched from Deconz/Conbee to ZHA/Skyconnect and since then the problems started.
Everyday some random devices (Aqara sensors, Ikea Bulbs) getting unavailable. I have to pair them again and the next day some diffent device is unavailable.
With Deconz/Conbee I never had this problems.
What version of Home Assistant Core has the issue?
core-2023.1.5
What was the last working version of Home Assistant Core?
core-2022.11
What type of installation are you running?
Home Assistant OS
Integration causing the issue
zha
Link to integration documentation on our website
https://www.home-assistant.io/integrations/zha
Diagnostics information
zha-f63193a751e4f18abbdbeaba6257af97-LUMI lumi.sensor_magnet.aq2-38e364b71addd13e8f72c896cb83e544.json.txt
zha-f63193a751e4f18abbdbeaba6257af97-Zigbee Coordinator-aabc7e236d33f421590e46eb61ea0400.json.txt
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: