#New Apple Homepod Mini's thread network shows up as part of existing OTBR network, not its own

1 messages · Page 1 of 1 (latest)

wraith crest
#

I'm swimming against the current here, but I wanted to migrate my thread network off the ZBT-2 to a new homepod mini. I've had lots of issues with thread credentials and the matter server adding devices using the HA add ons integrations. I figured migrating to the homepod would also free up the ZBT-2 for zigbee.

My plan was to add devices via apple home and share them via matter. However, the homepod is showing up as a border router in my existing thread network as opposed to its own network. Does anyone know how to segregate these?

vocal charm
#

If you have a Mac, open the Keychain and delete everything that has Thread in the name then reboot the mini. Then add a device in Apple Home that uses thread and it will create its own network.

wind tusk
#

If it's in the same network, no need to migrate anything. Just turn off the OTBR/ZBT-2 and you're done. The Homepod mini will take over.

vocal charm
#

Doh! Yeah, Boris with the much better answer.

wraith crest
#

let me see check that...the OTBR is on a different vlan

low wraith
#

sounds like a bad time. all your thread border routers need to be on the same vlan if you expect things to actually work

#

thread network traffic can use any thread border router as an exit from the thread network, so they all have to be "equal" in terms of routing.

wraith crest
#

Thanks, I added a wifi address to home assistant and was able to get some better coordination between the homepod and HA. I'm still not sure why the Homepod showed up as an additional border router for the existing thread network vs creating its own.

low wraith
#

The goal is for multiple thread border routers from different vendors to join the same thread network rather than start their own