Solved - How to change the preferred network on my android phone

In Home Assistant I have two Thread networks that show up:

The first one is the ZBT-1 that I want to use. The other is a device that I don’t actually have. I’ve checked my Unifi network and I have no Eero devices on it. I also checked Google Home, Apple Homekit, and Amazon and there are no Eero devices in any of those. If I delete it and refresh it comes back.

On my phone when I try and use the companion app to sync the creds I get an error saying
Sync Thread Credentials
Home Assistant and this device prefer different networks (device prefers: eero-thread-ce19)

I can’t seem to find a way to change that on my phone. Anyone have any ideas?

In case anyone else runs into this it was caused by the Google Play Services app. I had to force quit it and then clear the cache and data and then restart it. That corrected the Eero thing. But then the Matter server was showing as unavailable when I tried to add a device so I had to uninstall the Google Home app and reinstall it which fixed that issue. Everything is now working perfectly.

NOTE: If you clear the it will disconnect your watch if you have one and also remove all your credit cards from your google wallet. You just need the security code for each one to add them back in.

4 Likes

I have exactly the same problem and can’t get my phone to choose the right one. I’ve deleted google home, smartthings, HA on my phone, I’ve deleted the wrong network on HA on my PC, I’ve reinstalled HA on my phone and it doesn’t help much, so now I’m a very very desperate old man sitting there saying some nasty words, help is needed in advance, thanks

1 Like

Is there a generally valid solution for this?
The whole issue with Thread networks is really unnecessarily complicated.

Everything has worked well so far, but for some time now I have been unable to add devices via Matter because the HA Companion App indicates that Home Assistant and my Android device prefer different networks. In this case, my AqaraHome from the Aqara G5 Hub is getting in the way. For whatever reason, because I have never selected this Thread network and OTBR is also selected as preferred in Home Assistant and also set for the Android logins.

I have same issue. I installed Aqara M100 Hub as Thread board router but it had issues with Nuki device. Now I ordered ZB-GW04 and installed openthread firmware. Everything went good but my device preffered network is still Aqara and I cannot change it. In HA the preffered network is the new openthread router network but the android phone preffered Aqara. I deleted HA from phone also Google home but still have the problem.

I still see this issue.

I am convinced it’s related to the HA companion app and it’s inability to prompt the user as to which thread network to use when connecting a new device.

Is this even possible? Do we need to open a problem report?

This is my screenshot of my issue:

Same problem here, after I press OK it does start to sync but it’s never ending.

Same issue here, spent days trying to get otbr to communicate with HA and now this :frowning:

I have the exact same problem. I have tado BGRs and I just added the new HA zgbt2. Did all the settings but when I sync I get the error. Did remove cache, reinstalled home app etc, nothing changes :cry:

Make sure you remove the storage too.

1 Like

I managed to fix my issue by doing the following on my android tablet:

  • Remove the google home app
  • Clear cache and data for Google Play Services
  • Switched off the Google Nest Hub device & waited 5 mins
  • In HA/settings/Thread then deleted the NEST thread network
  • In the compansion app then did a sync credentials

all working now and my devices now get added to my “ha-thread-4dc3” network.

It shouldnt be this difficult though :frowning:

3 Likes

I did all of this and still get the error:

“can’t connect to thread network ha-thread-f9b3” check that your device can work with this network type and try again.

Totally agree, and it still doesn’t quite work for me.
What works fine (and is actually somewhat easier) is to commission device directly through the matter server webui.

You’ll need:

  • The matter server enabled with bluetooth
  • The TRV as displayed in HA Thread integration “info” page
  • The pairing code that goes with the device

Et voila, device integrated…
In this process, the matter server basically replaces the phone.

2 Likes

I have same issue. Samsung Galaxy phone and Smart Things Hub alongside with Home Assistant with USB Dongle for Thread.

Seems that no matter what I try , Smart Things hub is preferred Thread Border Router.

Whole Matter system is still far from user friendly promise. I am engineer and I cannot get it to work.

I know I will make it will work - eventually , but this is just crap that will not have chance of becoming main stream until it works flawlessly without so much hassle.

This worked for me. My device running HAOS doesn’t have bluetooth, so I’m dependent on my Android smartphone to onboard Thread/Matter.

The absolute hell that is Google Play Services is a reminder of why many of us seek to use cloud-free, local-only solutions - Home Assistant, Thread, Matter. Like others on this thread, I am an engineer and spent almost two days banging my head off the wall in the vain hope that I wouldn’t have to clear both cache and data for Google Play Services (as well as uninstalling Aqara home) from my phone simply to get HA Companion App sync with HAOS w.r.t. preferred Thread network. As others have commented, if this is not made simpler, Matter over Thread on Home Assistant will lose people.

Thank you Mark, for laying it out so clearly.

Ronan

1 Like

Thank you, this is actually the best solution! I manage 2 different homes with 2 different Thread Networks and I couldn’t connect anything at the 2nd home because my Android phone is stuck on the first home Thread network as Preferred Network.
Using the Matter Server UI allowed me to add a new device to the 2nd home.

1 Like

For future reference, going into terminal in de .storage folder and performing (Ubuntu server):

sudo rm -rf thread.datasets

and restart HA also works!

Just be carefull, as a typo or buggering around can break your system in the .storage folder!

Hi

I have same problem that matter tries to connect over old inexistent thread network.

I have deleted my old thread network, deinstalled old OTBR and switched off old OTBR.

restarted HA
I then added new HA ZBT-2 OTBR and generated new Thred network.
restarted HA
added matter integration new
restarted HA
In matter integration I see new thread network under thread

I also did reset of matter/thread sensor.

Android smartphone:
deleted aqara app
Google play services for AR cache and data deleted
Google play service is not installed
App cache and data delete
newstart
When I synchronize threadaccessdata in companion app it popups that
Android preferes different data “Aqara…network” than HA.

According my understanding that is the proplem. I still do not manage to get rid of the old “Aqara…network” data that no more exists.

When I try to pair my matter/thred sensors with Companion App it generates Matter data and then want to connect to sensor via old thread network. That fails logically as this does no more exist.

How can I get rid of this old thread network entry? I suppose it is somewhere cached or old factory …

Any idea?
All imputs are highly appreciated.
Thanks very much

2 Likes

Almost the same issue. Smart Things as border router. No Thrads dongle for HA though. All devices (IKEA) connected to Smart Things. Impossible to make HomeAssistant use the ST-xxxx-fabric as preferred network.