Exactly! For the very first setup, you always use the code printed directly on the device. For any subsequent ecosystem, you can simply generate a new pairing code from any app where the device is already successfully connected. It definitely doesn’t have to be the original or first app.
Also, try the following: In the HA companion app, go to Settings → Devices & services, and select the Thread integration.
On Android, select “Configure” and then “Import credentials”. You should see a notification confirming that the credentials were imported.
On iOS, select “Send credentials to Home Assistant”.
That should actually do the trick, and then you’ll also be able to add devices to HA first. I did it exactly like this recently, but as I said: HA simply needs the credentials for the Thread network.
Also, @JohnD regarding credentials. I bumped into the “Send credentials to HA” and clicked on it. I figured it would do no harm. Perhaps that’s why everything fell into place for me today.
I’m on my second time through your excellent write-up. Very helpful! I have one note for you.
You write:
Connecting to Additional Systems (Multi-Admin)
Generate Code: Go to the app with which you connected the device first (e.g., Aqara Home). Important: Do not use the sticker on the device for this second step.
It’s the “device first” that led me to believe that all secondary/tertiary pairings must be done with the first ecosystem. Now, most people probably aren’t as “anal” as me and don’t read it like this. Perhaps it should read, “Go to an app that has already been paired successfully with the device.”
Note: if you don’t change a thing, it’s still a very helpful guide!
I already had a draft ready with an explanatory note:
For any subsequent ecosystem, can simply generate a new pairing code from any app where the device is already successfully connected. It does not have to be the original or first app to which the device was connected.
Since I’m already editing it, though, I’d like to fix a few other things while I’m at it. Just give me a little more time before I publish it!
Yeah, I meant the Primary BBR — the one with the star. You’re totally right that’s just normal Thread doing its thing. I was more flagging it as something worth checking if people are seeing weird connectivity issues, not that there’s anything wrong with it. Just good to know what you’re looking at in the Matter Server.
For any subsequent ecosystem, can simply generate a new pairing code from any app where the device is already successfully connected. It does not have to be the original or first app to which the device was connected.