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.