Hello
I have problem with my thread network:
I have installed Open Thread Network on separate Home Assistant instance, and formed Thread network.
On my production Home Assistant instance I added that Thread network and added Apple TV 4k 128Gb WiFI + ethernet as BorderRouter and successfully added some devices. that worked. So happy…
Accedently, as everything works fine (With AppleTV as BorderRouter) I reused rPi with HomeAssistance with Thread Network, so that Thread network doesn’t exists any more.
Here comes the party.
All Matter devices added to Home assistant become unavailable.
Tried to add them again, unsuccessfully.
I realized that Threadset data that is still in my Apple keychain that should be transferred to device in order to join Thread network is from the formed network that is no longer available.
So, i need to reset, or remove complete Thread network data from my HomeAssistant, and from my Apple keychain, and let Apple TV to form a new Thread network that should be added into Home Assistant, or create new Thread network on production instance, and add Apple TV as Border Router.
Right now I can’t use, nor add any device even in Home app, where is my Apple TV Home Hub because Thread set that should be transferred to Matter device from Keychain are wrong…
Has anyone have solution, how to properly reinitialize new Thread Network with apple TV as Border router, and update Thread credentials in Apple Keychain?
I don’t know of any way to remove the stale Thread credentials from iOS keychain. The developer of iOS HA Companion App mentioned that it was on his to-do list to provide the user with a way to remove it, but as far as I know, it has not been implemented
On your new HA machine, using your iOS HA Companion, goto UI->Settings->Integrations->Thread->Configure
do you have any Thread networks showing up? If not, then at the bottom should be a button “Send Credentials To Home Assistant”. Hit the button and see if it adds a new Thread network. I’ve not tried it but it may possible work for you.
Hey Everyone, I had a similar issue as the OP did… My setup consists of a virtualized HA instance with USB pass-through of the official SkyConnect adapter.
Here are the steps I followed to get my Thread / Matter / Thread Border Router working again after I migrated VM hosts and lost my functioning thread network…
Removed Matter Server Add-on
– Settings > Add-ons > Matter Server > Uninstall
Removed Open Thread Border Router, Thread, Matter Integrations
– Settings > Devices & services > Open Thread Border Router > three menu dots > Delete
– Settings > Devices & services > Thread > three menu dots > Delete
– Settings > Devices & services > Matter > three menu dots > Delete
Shut down HA
Reinstalled SkyConnect USB Dongle
Forced Thread firmware (multi-protocol firmware seems to be a bust)
– Settings > System > Hardware > “Configure” Home Assistant SkyConnect > Thread
– Follow On-screen prompts until done
Add Thread , Matter Integrations
– Settings > Devices & services > “Add Integration” > Search for Thread and follow on-screen prompts and accept default settings
– Settings > Devices & services > “Add Integration” > Search for Matter and follow on-screen prompts and accept default settings
At this point the "Open Thread Border Router should have automatically added during the flashing of the SkyConnect dongle… Almost there…
Configure HA Thread Border Router credentials
– Settings > Devices & services > Thread > click “Configure” > click three dots next to “Home Assistant OpenThread Border Router” > Click "Use for Android + iOS credentials
– You should see a picture of a phone with a key pop up next to the HA border router entry
Configure credentials via iOS companion app
– Open HA on iOS > Settings > Devices & services > Thread > Click “Configure” > Click “Send Credentials To Home Assistant”
At this point I was able to add Matter devices (which use thread networks) back into HA. I factory my matter device and put it in paring mode, then added it via iOS app
I am pretty sure there were some unnecessary steps throughout this journey - but after a few hours of messing around, this is what seemed to work for me.
