Hi everyone, I was about to create a bug report, but when I was gathering all information, I was able to solve the issue myself ![]()
Thought I just drop the necessary information here if someone encounters the same issue.
My setup
- HAOS 16.3 on ODroid M1
- Core 2025.12.2 (issue was there at least already on 2025.12.1)
- Supervisor 2025.12.3
- Frontend 20251203.2 / Companion App 2025.12.1 (2025.1546)
- Thread Border Router: Open Thread Border Router (OTBR) AddOn with ZBT-1
The issue
Existing Matter-over-Thread devices were working just fine. My motion sensors were triggering automations for Matter-over-Thread, Shelly WiFi and WLED lights. My Matter-over-Thread smoke sensors were online. My Eve Energy Outdoor was providing real-time data.
But I was not able to add new Thread devices. The Thread integration showed a known network with the correct name (the same as the Matter-devices showed under their device pages), but stated that there would be no Border router found. When trying to add a new Matter device, I got an error somehow (roughly translated from German) like this:
Error for saving credentials for Thread-Network, Error: Thread network credentials does not match with any of the active Thread networks around. The login information for the Thread network could not be saved.
I was able to click “continue”, but I could not add new devices because “Pairing Failed”. When trying to add a Matter-over-Thread device to Apple Home (which worked fine before), it tried to connect but failed with:
Thread Border Router Required. To connect this device, you need a Thread Border Router in your private network.
The solution
Under Settings, Hardware I have an image of the ODroid-M1 at the top and a CPU / RAM usage graphs at the bottom. In between is a button “Home Assistant SkyConnect (Configure)”. By clicking on it, you get ask whether you want to migrate your ZigBee or Thread network to a new radio adapter. Originally I just wanted to see where this leads, but by clicking “Migrate Thread to a new adaptor (By this, your Thread Border Router is migrated to a new device)”, it started off some update process (re-installing firmware?), which eventually solved my problem.