#Clean up Thread networks

1 messages · Page 1 of 1 (latest)

storm furnace
#

I currently run HA in a container in my Talos Linux cluster. I'm also running the Matter Server in container as well. I'm trying to get an Aqara presence sensor P2 to commission, but it keeps failing. I noticed there seems to be some issues with my Thread networks. I'm attaching a picture. I have an Aqara M3 Hub, a Nest Hub Max and Google Streamer and a Nest Hub that are all exposing a thread network. HA is also recording one, but says No Open Thread Border Routers found. It seems I can only make the Nest one the preferred one. I think I'd like to make the M3 Hub the preferred one, or even HA.

So is it possible to clean this up and make them all be able to selected as the preferred network?

My network is a Unifi network and it's connected to Xfinity here in the US. It pulls an IPv6 address. My IoT network has both IPv4 and IPv6 enabled. IPv6 is enabled with Prefix Delegation and client addresses are assigned with SLAAC. DHCP is configured to go through Cloudflare.

Screenshot_2025-04-02_at_1.58.31_PM.png
green spindle
#

It appears that the Thread credentials for AqaraHome-2e38 are not stored on the mobile.

Are you using iOS or Android? If on Android, the Thread credentials should sync to Android's key store automatically in the background. However, on iOS, you'll need to open the Google Home app to retrieve the credentials from Google TV Streamer and store them in iOS key store.

storm furnace
#

I'm on android. I'll see if I can sync them