Six days ago, four T2 bulbs lost connectivity around the same time. They are connected to a Thread network which includes both a ATV4K and M3 as Thread Border Routers. They are 4m away from the TBRs. They are now flashing which seems to mean they in pairing mode.
This is not the first time. @AqaraBot what is happening?
@European It sounds frustrating to have your T2 bulbs lose connectivity. Given that they are connected via a Thread network with both ATV4K and M3 as Thread Border Routers, there are a few things we can consider:
Thread Network Partitions: Thread networks can sometimes become partitioned, which means groups of devices may temporarily lose communication with each other but retain their security credentials. When the partitions resolve, the network should automatically merge. This could be a reason why your bulbs are flashing, indicating they are trying to reconnect.
Proximity to Border Routers: Although 4 meters (about 13 feet) is relatively close, ensure there are no significant physical obstructions or sources of interference between the bulbs and the Thread Border Routers.
Reboot and Reconnect: As a first step, try rebooting the Thread Border Routers and see if the bulbs reconnect automatically. You can also try resetting the bulbs by turning them off and then back on to re-enter pairing mode.
Network Stability: Check if your network, including both Wi-Fi and Thread networks, is stable. Network instability could be causing the bulbs to drop out.
If these steps don’t resolve the issue, it might be helpful to discuss further in the community or consider other environmental factors that might be affecting the network’s reliability. Your experience could also aid others facing similar issues.
Thanks @AqaraBot
If the network partioned, they have been unsuccessfully trying to reconnect for the last six days. Both the ATV4K as the M3 report the bulbs as disconnected. The bulbs at in line of sight with no obstructions.
Can you share any technical references which explain the potential partitioning issue?
@European It seems like you’re experiencing a persistent issue with your T2 bulbs not reconnecting after a network partition on your Thread network. Let’s delve into the concept of network partitioning to see if we can provide some clarity.
A Thread network can indeed experience partitioning. This happens when a group of Thread devices can no longer communicate with another group within the same network. Each partition operates as an independent Thread network with its own Leader, Router ID assignments, and network data while maintaining the same security credentials. Normally, when the partitions can communicate again, they automatically merge back into a single network.
Given that your bulbs have been trying to reconnect for several days, it’s possible that there might be a persistent issue preventing the partitions from merging. Since both your ATV4K and M3 are reporting the bulbs as disconnected, and considering there are no physical obstructions, here are a few steps you could try:
Reboot Devices: Restart both the ATV4K and the M3 Thread Border Routers. Sometimes a simple reboot can resolve connectivity issues.
Reset Bulbs: You might also want to reset your T2 bulbs to ensure they re-enter pairing mode and attempt to reconnect to the network afresh.
Check for Interference: Even in the line of sight, other wireless devices or electronic equipment could be causing interference. Ensure that your Thread network’s channel does not overlap with other wireless networks.
Firmware Updates: Make sure all devices, including the bulbs and Thread Border Routers, are running the latest firmware to ensure compatibility and stability.
Consult Technical Support: If the issue persists, it might be beneficial to contact Aqara support for more in-depth troubleshooting.
I hope this helps clarify the situation. Please feel free to share any further observations or results from these steps with the community; it could help others facing similar issues. If you need further technical documentation or support, consider reaching out to Aqara’s technical support team.
Did you find any solutions ? I have the same problem but connect via zigbee
@dRoble I’m sorry to hear you’re facing similar connectivity issues with your Zigbee-connected bulbs. Let’s troubleshoot based on common Zigbee device connectivity solutions:
Update Firmware & App: First, ensure your Aqara Hub (like M3) and Aqara Home App are updated to the latest versions. Outdated firmware can cause stability issues with Zigbee connections .
Check Signal & Interference: Even if the distance seems short, confirm there are no heavy obstructions (like metal barriers) or nearby devices emitting 2.4GHz interference (e.g., microwaves, Bluetooth devices). Zigbee signals can be disrupted by such factors [“content_id”:0, “content_id”:3].
Verify Hub Status: Ensure your Zigbee Hub (M3) is online and connected to a stable Wi-Fi network. A offline or unstable hub can’t maintain device connections .
Reset & Re-pair: If the bulbs are stuck in pairing mode (flashing), try resetting them (refer to the T2 bulb manual for reset steps) and re-adding them via the Aqara Home App. Also, check if they were accidentally bound to another hub before .
Battery Check (if applicable): If the bulbs are battery-powered, low battery can cause disconnections—replace or recharge them .
Have you tried any of these steps yet? Let us know how it goes, and we can dig deeper if needed
I would like to mention that with loosing connectivity, I actually mean that the bulb seem to be in a network reset mode and the bulbs are flashing. This happens so often that I printed out the matter codes and stuck them near the bulbs so that I don’t need to remove the bulbs to be able to scan the code.
Hello, If you are using Aqara home, enable the “prevent device removal” feature on the gateway.
Thanks for the suggestion. What does this option do? It does not seem to be related to do hub. At some point the bulbs start flashing and the hub shows the device as having lost connectivity.
Thanks @gafich10
My bulb was connected via Thread, so I wasn’t using the Aqara app. I switched it to Zigbee and activated this. Hopefully this fixes the issue; otherwise, I may need to switch to different bulbs.
Having the exact same issue, whether on zigbee or matter. Trying the above solution. I hope they fix this with a firmware update
Tried it, and now I’m constantly getting notifications that someone is trying to reset it
Hello, happy 2026! Maybe you have a problem with the switch contact, it does not have good contact and it imitates a 5-time On/Off lamp?
Is the lamp connected directly to 220 or is it connected through a smart switch?
I’m having the exact same problem. Using an automation to turn on and off a bulb based on motion sensor activity. Every time it turns off I get an “Anti-delete” notification saying someone is trying to reset the bulb.
Hi, welcome to the forum. Is the smart bulb connected to a smart switch?
My bulbs are connected to non smart switches. Aqara does not sell them in Japan. I am still loosing the bulbs and I resorted to sticking QR codes next to the bulbs.
When re-adding the bulbs, the Aqara app asks me whether I want to add them as Thread or Zigbee. I don’t know whether that means it was a network reset or factory reset.
It happens to all my Aqara T2 bulbs and it seems unlikely that all my switches have bad contacts. If it would be a problem of the switches, I would be a bad implementation of the bulb firmware because the switches should be able to distinguish between a human initiated reset or bad contacts.
I also have Hue bulbs connected to the same type of switches and in never happened that I would connectivity or the bulbs would do a reset.
Nope it has nothing to do with switch contact. When I use a T1 bulb on it, it works perfectly fine. It’s not connected to a smart switch. There’s obviously a bug with the T2 bulb. Now I can’t sleep a single night without the bulb trying to reset itself and flash brightly in my bedroom. Please fix this in a firmware update
Hi, I have forwarded your issue for review. Sorry for the inconvenience.
I am seeing the exact same behavior. This is not an isolated incident. Have to keep the power switch off until I can get someone to change the bulb for me (ceiling light, and I am disabled).
