I’m running HA Green Core: v.2025.12.4 / OS:16.3
… connecting Aqara bulbs via Matter,
… with a SONOFF Zigbee 3.0 USB Dongle Plus that is not near other devices.
In my house, I have four relatively new eero mesh routers. Speed, latency, and jitter are all good.
I’m setting up bulbs in the Matter interface in the HA app on my phone. I pair with only 2.4Ghz wifi turned on.
Once they are set up in HA and working correctly, I use Google Echo to control them. When I first power the bulbs, they pop-up to populate directly into Alexa – I do not do that. I only populate the bulbs that are exposed to Alexa from HA.
Six bulbs are in the same room as the Green/Sonoff and an eero router. The other four bulbs are in the basement directly below the eero/Green/dongle.
The bulbs work fine for several days, then one or two will start dropping off – the node goes offline. This has happened multiple times. There have been no power drops as far as I know. The light switches to those bulbs are locked under covers. (In some cases, pairing fails once or twice before the bulb connects.)
Why do some bulbs arbitrarily unpair? Bulbs go offline a couple at a time (in different rooms), and then I need to go through the whole re-pairing process.
Any assistance to keep these connected would be helpful.
Same! Driving me crazy. I have an automation to turn the light on or off based on motion sensor activity. When the inactivity timer ends and the light turns off, more than half the time HA unpairs it. With the bulb direct Zigbee paired to HA, it just drops completely and I have to re-pair it. When I have the bulb paired to the Aqara M2 hub, the anti-delete feature prevents the bulb from being reset, but I get “Anti-delete” alerts from Aqara. So it’s definitely something in HA that the bulb interprets as “unpair”. Nothing in the logs other than normal on/off activity. No new firmware for the bulbs available. I have 2 other Aqara bulbs that are working fine. Probably going to replace this flaky one with a Hue bulb.
My automation for turning the light on and off uses an Aqara motion sensor or an Aqara door sensor as the triggers to turn the Aqara bulb on or off. So everything is Aqara. As an experiment, I disabled the automation in Home Assistant and created an identical one in the Aqara app, using the M2 hub. I get the same “Anti-Delete” warning using only Aqara. So this has nothing to do with Home Assistant. Since I have 2 other Aqara bulbs working fine in Zigbee mode with HA, this has to be a bad bulb (which I’ll be replacing) and nothing to do with Home Assistant
I figured out my issue. I was using the Sonoff ZBDongle-P (which does not support Thread) instead of the ZBDongle-E, which I thought I’d ordered.
I’m surprised that Thread worked at all – but apparently there is enough built-in Thread support in the HA Green or in the dongle that some devices worked marginally.
I got the HA ZBT-2 and things are working much better.
Noo, Not Same, Nowhere OP mention AqaraM2, and in facts He clearly State “Matter-bulps” (not zigbee ) And he is using Another Controller(Which seems to be a Zigbee( which only support Matter, if it’s flashed with other firmware ! ), which He don’t mention,and He use Another Integration …
NOTE: Running Zigbee And Matter, through the same controller, still seems for some Devices to cause Problems
You, on the other Hand don’t mention Matter Anywhere in your 2 Posts
Note: OP has "TAG"ed his Topic, with “Matter/Thread”
You could open A new Topic, presenting your Issue( And delte your 2 posts, copy paste to your new Topic) (thou there are tons of similar Topic in here, But for sure you would be better of searching these ( Make sure it’s Zigbee related ) And delete your post here, please