When incorporating matter devices, the phone always remembers "-ha-thread-xxxx previous. I have already cleared the phone’s cache.
all, same here.
connected my u200 lock to the google thread network “NEST-xxx” and wanted to share it to home assistant without any luck.
I ordered the ZBT-2 and installed OT.
I deleted the NEST-xxx network, resetted the lock itself, re-installed home assistant on my phone… but when I try to connect the lock to the thread network, it wants to connect to the NEST-xxx network, which does not exist anymore. I even uninstalled google home.
Is there a possibility to chose the network to connect to?
thanks
lukas
The mobile device that one uses for commissioning stores the Thread network dataset/credentials that it uses for commissioning. Both Android based and iOS based mobile devices tend to keep and use the first Thread credentials it sees. iOS has a way to delete individual Thread network credentials, but AFAIK, Android requires Google Play Services’ data store/cache to be deleted (which deletes other things too) to remove an existing Thread dataset/credentials.
Not that I’m aware of — this is a limitation of the platforms (Apple and Google) which have (sadly) chosen to abstract all this away from the end user.
The iOS companion app provides an interface to see and optionally swipe left to delete credentials (under debugging Thread) but I’ve heard reports it may not work, and that you need a Mac running the keychain access app to permanently delete old network credentials. I haven’t found anything similar in the Android companion app, and have only heard you have to blow away everything by clearing your Play Services settings.
surely android has a technique to replace the thread credentials in Google play services. Could this problem be escalated to Nabu Casa for analysis. Or surely the storing of the string border router credentials in android files could be avoided.
The HA Companion App relies on the underlying Android Thread Framework. There are APIs of course available to apps using the framework, but there appear to be limits. For example, the app can only delete Thread credentials that it created. There also doesn’t appear to be a way to set Preferred credentials.
I’m not sure why the CA doesn’t provide the ability to delete the creds it created, but most cases I’ve seen is where the user has Google Home Thread creds stored and is the one the framework has set as preferred, so in this case the Companion App wouldn’t be able to help out the user.
1 Like
so I did and this worked for me.
nevertheless I can’t connect my aqara u200 to home assistant with zbt-2 antenna (as my border router). the lock will be found. the thread network will be found. but after generating the matter login credentials the process stops with ‘not possible to connect’.
any ideas?
setup: unifi udm, 2 vlans (wlan - home assistant companion app, lan - home assistant itself), which have ipv4 inter-vlan routing allowed. furthermore ipv6 inter-vlan routing allowed (any types). (see 1)
home assistant ipv6 is active and set to automatic/dhcp. (see 2)
ping from vlan ‘wlan’ to ‘lan’ (thread border router) is possible. (see 3)
ping from ‘lan’ (home assistant, thread border router) to ‘wlan’ ist also possible. (see 4)
I’m desperate… please help!
Lukas
Having two VLANs is often the problem as the mDNS advertisements (which are heavily used in Matter/Thread) don’t get seen across VLANs.
Otherwise, see if this Unifi tip helps …
SOLUTION:
Mobile phone and Home Assistant need to be in the same VLAN. Even if the IPv6 communication is completely allowed between VLANs it won’t work…
best regards
lukas