I have 3 m3 hubs on different locations (not in same network). i thought that home m3 is my primary matter controller. i would like to add p2 sensor to 2. and 3. under each m3 as sub but as soon as i removed the primary m3 and put into my house the p2 are offline. why ? i have them all in my aqara app. 3 different cards. each card with all sensors an. only p2 wont work ?
Hi @guenther if added all correctly it should work if you add P2 to M3 (2 or 3) and you unplug the first M3 which is connected in a different network . Do you add the M3 in a different home? Just for understanding, may you can add some screenshots for better understanding
i installed all m3 at home together in my homelan and setup them on separate desktops. then i moved 2 m3 to another location. i buyed p2 door sensors and would like to add them on 2 and 3 but it wont work when p1 is not on same nw. then i removed them and tried to add them als subordinated to 2 and 3 . as long as the m1 on same nw it works but when removing from nw the p2 are offline again. thermal sensor works, plug woks but p2 door not. why. whats wrong in my config. p1 is the only prim matter controller home.
This is my understanding and correct someone from Aqara if I am wrong.
The thread network works differently to the ZigBee network in that your thread network operates on single tread network and only one controller can be the mater thread controller. If the master controller is lost or disconnects then effectively the thread communications cannot continue.
When you added all3 Hubs did they all join to the same Thread network or did you create separate Thread networks?
I was wrong I’ve got this from the internet.
Here’s how the network handles a controller failure:
- Automatic Reconfiguration: The Thread network constantly monitors its health. If a device acting as a router or the Leader fails or is removed, the other devices automatically re-route data through a different path.
- Leader Election: The network dynamically elects a new Leader from the remaining eligible devices (mains-powered Thread routers) to take over management tasks.
- Redundancy: Any mains-powered Thread device can become a router and help relay signals, creating a robust and redundant network. The more routers you have, the stronger and more resilient the network becomes.
- Local Operation: The network continues to function locally, even without an internet connection, allowing local automations and device-to-device communication to persist.
He has another post here in the forum in German: M3 auf verschiedenen Standorten
Here is the translation of my last post:
What exactly do you mean by that? Where is which hub and when?
If you have three networks, you need a Thread border router in each network to use “Matter over Thread” at the respective location. Since Matter over Thread works with IPv6, IPv6 should be configured on each router at the respective location.
As far as I know, the concept of a ‘main/primary matter hub’ only exists within the Aqara app, rather than at the Matter or network level. This is why only Aqara hubs are displayed in the app, and not other Thread border routers, such as the Apple HomePod. I don’t know exactly what Aqara has implemented. Others can surely provide more details on this.
Addendum: The leader of the thread routers is elected automatically. Users cannot select one themselves.
Have you set up multiple “houses” in the Aqara Home app under Profile > Home Settings > Home Management?