Sync Thread credentials failed

[xyu6]

Hi, I buy the home assistantconnect zbt-1.

step1: burn the thread firmware,

step2: follow instructions to install the thread.

step3: follow instruction 2&3.

Before you can add Matter-based Thread devices, your phone needs to know the credentials of your newly created Thread network.

• To share the credentials with your Android phone, open the Home Assistant Companion app.
  • In the Companion app, go to Settings > Companion app > Troubleshooting, then select Sync Thread credentials.
  • Follow the instructions on screen.

but i have the error message.

ha os thread preferred network is ha-thread-fd34

anyone faces the issue or any idea, please let me know. thanks.

[wmaker (Tommy Long)]

Unfortunately this is a known problem. HA Companion App uses the Android framework for commissioning a device and the Android framework stores and uses the very first Thread network dataset it finds out about, and will only use that dataset. In your case, it looks like it has stored an eero-thread dataset.

The only way to remove it is to clear out the Google Play (See here) . Just be aware that if you have anything else stored in the Google play, then it too will be cleared out.

If you are still using your eero-thread network, note that it isn’t necessary to have a ZBT-1. If you want to use both, it may be possible to sync the eero-thread credentials in Android to HA, but I’m not entirely sure how. I would have thought the “Syncing” you did earlier would have sent the eero-thread dataset to HA.

[WallyR (Wally)]

Sometimes the Google Play services refuse to remove the old credentials.
Try this guide to copy the credentials.

Cannot add Matter devices

Make sure you have the correct thread credentials on the Android. On the Android Companion App open Settings → Companion App → Troubleshooting (I think that is what it is called in english, but it list logfiles and other tools to diagnostics as description of the item). In this next window click the Sync Thread Login Credentials (Again it might not be named exactly that, but close to and there should not be that many options and it should be in the bottom) It should say either something with …

[mehoranto]

I came here because of the same problem. I use an android custom OS without google play services. So i’m basically screwed at this point I guess? Is there any solution to set up a thread/matter network without a smartphone? I also have nothing else or old I could use. Relying on google and apple appears ridiculous to me and seems to make a mokery of the whole Idea of open standards

[peterxian]

@mehoranto

Is there any solution to set up a thread/matter network without a smartphone?

Yes, but the matter add-on needs dedicated access to a Bluetooth dongle and the device being paired needs to be within Bluetooth range of the server. Scroll about halfway through this post for details:

Matter Pairing/Commissioning hints

If you are new to Matter, check the official Matter integration docs! Specifically read the Adding a Matter device to Home Assistant which walks you through all the steps necessary to add a device. This post adds some more information and other commissioning options if you have problems or you are seeking for other ways to commission devices. The recommended commissioning mode for Matter devices is currently through the official Home Assistant companion apps. Both, the Android…

[Server (Jeremiah)]

Your post helped me get my first thread device to connect!
I had purchased a ZBT-1 to make Home Assistant my main thread border router.
When trying to connect a new Matter over Thread device to Home Assistant, I’d get a annoying screen on my phone saying I needed to add a thread border router. I tried plenty of things over the course of a few days, with no luck.

A google search with the right keywords found this message thread. I would never have known about this VERY OBSCURE - yet - VERY CRITICAL button. One could say it is upsetting that the developers did not put this button somewhere else… you know, like maybe under the thread device configuration or something… maybe a link to the troubleshooting? This should be fixed on some future app update.

I thank you for taking the time to make your post and lead me to the solution.
Thank you very much!