#Matter isn't getting wifi/thread config w/ SkyConnect
1 messages · Page 1 of 1 (latest)
Debug information from the Thread service does correctly show my "home-assistant" network with "homeassistant.local." in the hash of routers...
Matter is still in beta. I haven't been able to add any matter-thread devices using skyconnect. It always needs Google or Apple TBR (thread border router). Seems like you were able to commission the device via Apple. You can't choose which TBR will be the leader (it's done automatically). Did you share the device with HA and able to see the device in HA?
Matter is getting wifi/thread config w/ SkyConnect
Matter isn't getting wifi/thread config w/ SkyConnect
I think you actually can choose at this point, right? Under the Thread service, it certainly knows what my network and preferred BR is... does the Matter integration not pass over the keys and TLVs?
Lots of gunk in the matter server... timeouts subscribing to things. Gonna reboot the Pi
With debug logging on for some things...
Repeat warning as from multiproto addon [W] Platform------: Failed to update ipsets: Failed ipset v7.10: The set with the given name does not exist
From what I can tell, the Matter Integration does not get Thread credentials from any of the integrations, and the only time it would use any Thread credentials is when you use the Matter Server's bluetooth (instead of an App) to fully commission a device onto both Thread and Matter Fabric
looking at the matter integration there certainly does seem to be code to send configurations over to the Matter server https://github.com/home-assistant/core/blob/dev/homeassistant/components/matter/api.py#L118
Yes those APIs (websockets) exists and some have used them including myself to commission devices when the Apps fail, but AFAIK, the integrations don't use them
It gets invoked during matter startup... https://github.com/home-assistant/core/blob/dev/homeassistant/components/matter/__init__.py#L80
or is that just registering the calls?
I haven't looked at the integration code in a while, but I had not seen where the set_thread_datatset was actually invoked.
in other words was Thread or OTBR integration passing it to Matter Server
or Matter Client to Matter Server
well that feels terrible. seems like there should be a feature ticket somewhere for that.
A beta that lacks the ability to pass on wifi or thread credentials would certainly explain the YouTubers' disappointment I've seen.
Yes in the case the Apps can not do the Thread commissioning properly, I too would like to see a way to populate the Matter Server with the credentials and let the Matter Server do the network related commissioning
Gotcha... sounds like I should be also looking at client code. My bulbs certainly seem to only work if they've been deleted from from a Homekit network and have some ghost config left behind...
is there an easy way to attach a REPL to HA's python process? 🤓
My swift and react are rusty... but it sure looks like the current iOS code calls matter/commission on HA via RPC.
So last I heard you can’t use iOS to add a device via OTBR full stop
You need a special api permission from apple
HA got it very recently
Then immediately hit a bug, which I think was reported to apple
Apple commissions devices on to thread, but only the networks it has the keys for. So basically it’s own.
Android should work. There are some edges where it only works if you eg only have non-google border routers. That seems to be a thing with googles sdk. But it should sync creds between the thread integration and android when you try to add a device through the HA app on android,
Direct matter commissioning was supported originally but I believe there was a bluez conflict. And actually it’s really annoying as every lightbulb you want to commission has to be moved within Bluetooth range of HA to be added to the mesh. Much easier to move your phone to your light bulb.
All this said, right now your apple BRs will proably give you the most stable matter experience
I'd rather play socket-shuffle next to my HA-branded SkyConnect and the web UI.
Last I heard, apple > google > SkyConnect 🥲
(My inner PM and developer are having a shouting match about priorities.)
More importantly, I can't seem to find the "bring your phone close to the device" shims... it REALLY looks like the apps are making an API call...
They are leveraging matter sdks from apple and google if that’s what you mean
I'm actually just looking for where that API call gets made in the iOS code right now.