#Struggling w/ Thread

1 messages · Page 1 of 1 (latest)

visual sluice
#

A while back, I experimented with Matter and Thread but barely got it working and eventually set it aside. Now I’d like to revisit it and see how much progress has been made.

At the moment, my setup is mainly anchored in Apple’s ecosystem. I have two Apple TVs running as HomeKit hubs, and I use the HomeKit integration assistant to expose a number of devices to HomeKit. I also have a new SLZB radio flashed as a Matter OpenThread Border Router (OTBR).

From what I can tell, things are working in the sense that I can see three separate networks: one coming from Apple, and one from the OTBR and one from my singular Google Home device,. But none of them is showing up as “primary,” and I don’t seem to have an option to designate one as preferred. I’ve tried managing this from mobile too, but I’m still unsure how to proceed.

I think the first step is figuring out how to make one network preferred, but I’m not sure how to do that.

image.png
#

when I go into the companion app -> debugging -> thread, I see no credentials. I've tried uninstalling the app, but it doesn't seem to make a difference. II think the lack of credentials is just another symptom of my borked configuration but figured I would share since best I can tell something should be here

Screenshot_2025-09-25_at_9.01.15_AM.png
visual sluice
visual sluice
#

Somehow after a few restarts I was abe to at the OTBR as my preferred network

image.png
#

but now when I try to send credentials to ios I get this error

Screenshot_2025-09-26_at_2.29.24_PM.png
primal edge
# visual sluice Somehow after a few restarts I was abe to at the OTBR as my preferred network

That is a good thing. Can you commission Matter over thread devices to your "ha-thread" network now?
Via the Google Home app you should be able to join the Nest BR to the "MyHome" network, and via the dots menu you should be able to join the OTBR to the "MyHome" network as well (if you installed and configured the OTBR Integration).
This way your get a unified stronger thread network instead of three competing for the same spectrum.

visual sluice
#

I dont see any options related to thread on the ios google home app

#

honestly, I dont even really use the good display at this point.... any reason not to join the OTBR to the applie BR ??

wary dawn
#

do you have ble dongle or interface on your HA? Use Matter Server webUI to add it directly, no need using smart phone if it confuses you

hushed pewter
visual sluice
visual sluice
#

IOS26....

#

any suggestions on how to proceed... or at this point am I just accepting that matter on Hass is broken ?

trim bluff
#

If you have a working Apple home setup and apple Thread Border routers, Easiest way forward for me was ditch the HA OTBR (that implementation is old and buggy at the moment). HA can use the currently better implementation of the apple thread network as its own.

Onboard new matter devices in apple home and then multiadmin them into HA. Done and dusted, at least for me. Full control from the HA and the matter server (both matter over thread and wifi), including OTA firmware updates for the thread devices.

visual sluice
#

The problem is, I don’t think I have a working Apple set up…. I have no option to make it my preferred network or anything.

trim bluff
#

My suggestion is get rid of the HA SLZB thread network (unplug the device), disable the OTBR add on in HA and the Google thread network (for now at least) and see if you can then onboard into Apple home.

after that 'Turn on Pairing mode" in the device settings of each Matter over Thread device in apple home, you will be presented with a new Matter pairing code for that device, which you can use to onboard into HA.

Iterate and see how things work. you may find, as I did, you have no need to force fit a HA OTBR at all. At least until the HA OTBR software/firmware is updated to more recent code and can play nice with other ecosystems. even then it might not offer any real usable benefits for those with a widely distributed apple thread network.

visual sluice
#

ok, so I have removed the OTBR add-on, removed the integration and kinda back to square one I think

#

cant make any of them my preferred network

visual sluice
#

In the app my thread network is empty

image0.jpg
trim bluff
visual sluice
#

Years ago, I tried thread in matter with a single device, but that device died so I never really went anywhere

#

It did work for a few days while I was toying with it so I suppose at one point this all worked

#

When I go to part five of the blog, there is no option to import credentials

trim bluff
#

Have you added any thread devices to Apple home?

ionic valley
#

read somewhere that you have to use a non apple device to login to your matter router and set credentials.

trim bluff
#

I suspect you do not have any apple thread credentials in iOS because you don't have any apple home thread devices. So zero apple thread network credentials to share until you do.

visual sluice
#

I have a level lock which supports matter integrated into apple home

#

This lock is currently not manageable via home assistant

trim bluff
#

Since you have no 'Turn On Pairing Mode' above remove accessory in that screen shot, likely connected via bluetooth only. See example screenshot.
all your Matter devices (Matter over wifi and Matter over thread) should have that option.

image.png
#

So ... how close is the lock to your Thread enabled Appletv? from the initial screenshot assuming only one of the 2 appleTv you own is thread enabled (only one showed up). Do you know which of the 2 has thread?

visual sluice
#

the 4k apple tv one, which is the one closer, its 20' from the front door

visual sluice
#

Yea, I added the device to iOS home from the level app itself using the QR code on the lock

#

So I matter contact sensor as well that I have not paired with anything…. You think I should remove the level lock from Apple home and then what?

#

By the way, I don’t think I said thank you. I appreciate your help & patience in trying to get me sorted out!

trim bluff
#

I think you will eventually need to remove the lock and repair with apple home so it uses Matter over thread.

First i would turn off/disable the nest thread boarder router to decrease extraneous variables and then add the Matter contact sensor (are you sure this is Matter over thread) to apple home . keep the contact sensor close to the apple TV for now and use the iphone for onboarding/adding to applehome. After adding wait for about 20-30 min to make sure the contact still works as expected in apple home. After that Apple home should create shareable apple thread network credentials in your apple keychain.

visual sluice
#

Should I delete the thread network in the keychain at one point in time I did do that and tried to re-create. It probably did more damage than good.

#

Zero problem unplugging the Google device, I don’t even use it

trim bluff
#

just try and on board the Matter over thread contact sensor to apple home

visual sluice
#

OK, a little bit of a breakthrough, I was able to add the contact sensor to Apple home. I then was able to create a sharing code and add that as a matter accessory within Home Assistant …. so I seem to have connected the ecosystems I have since removed the level lock from Apple home. I have removed it from the level lock app, and I was able to add it as an accessory within Apple home but does not show the pairing code sharing option yet I had to step out for dinner so I’m hoping maybe like you said giving it 30 minutes might do something there. I’ll report back later this Evening

visual sluice
#

yea, time didnt seem to change anything the level lock is still showing up the same within the apple home app

#

no option to toggle pairing mode or anything

#

tried adding it directly into apple home using the Homekit code, skipping their app.... then tried again via their app and adding to home kit via their app... both seemed to yeild the same results

#

I'll try again fresh tomorrow , maybe I rush it or something since it was dark

trim bluff
trim bluff
visual sluice
#

I have done the upgrade , it forces it from the first time setup... still no option to get this setup via matter though

trim bluff
#

After the Matter firmware upgrade, you should be using an 11 digit Matter pairing code to onboard into apple home, not the old 8 digit homekit pairing code that may have come printed on the lock. other that that, I am out of ideas for the level lock.

visual sluice
#

So as it turns out the problem, here was in fact the firmware !?!? I had to call and specifically ask them to target the lock with the matter enabled firmware, even though the box said matter supported!! totally crazy, and very annoyed how much time I wasted getting to the bottom of that . once they updated the lock everything works as expected.

#

Is there a step I need to do to close this thread as solved ?