aloha,
Installed my new nuki pro 4 smartlock today and wanted to try out its matter integration:
running a skyconnect with latest openthread firmware
on HA I installed open thread border router add-on and the HA matter integration
on starting the matter integration it asks to install the HA matter add-on
once everything is (to my understanding) setup in HA …
in nuki app starting the matter integration - which is already a bit weird to me as it just states to scan the QR code and reference only google home but not home assistant
so I tried (as I am used to from z-wave) to just manually add a new device within matter integration
and there it is just asking me to select the select the connection method (see screenshot)
and then just tells me that it has successfully reconfigured the matter integration…
You need to go to the Home assistant settings page, devices list and add a device there. You can pick matter and follow instructions. Curious how you fare. I added it through a nest hub 2 as border router, but it periodically becomes unavailable.
I’m wondering if this is a Thread issue… in your HA Thread Integration (not AddOn), does it have a “Preferred Network”… Take a look at UI->Integrations->Thread->CONFIGURE Does it have “home-assistant” under “Preferred network”?
I used the Companion app app to join the network of the Nest Hub 2 border routers as I do not own a SkyConnect and my Sonoff Dongle E is configured for Zigbee only. So the nest border routers are my preferred network.
Edit: I used the three dot menu to import the credentials from it if I remember correctly. Maybe you need to do something similar with your SkyConnect?
If you’re only using SkyConnect w OTBR AddOn (No other TBR), then the OTBR will already generate its own credentials, I just can’t remember if you have tell HA to set it to Preferred or not.
The Commissioning Apps get the Thread creds from HA Thread Integration set to Preferred.
The other thing to check is that since the Nuki App didn’t see Home Assistant after scanning QR code, I’m wondering if IPv6 is setup on HA. HA should be advertising its “meshcop” using mDNS via IPv6 over the layer 2 network for the App to see. Also, the mobile device running the Nuki App has to be on the same layer 2 network as HA.
I know I tried several things and if I remember correctly the Nuki app did not show HA either, at least not initially. I had to reset my Nest hubs (for different reasons) in order to get it to work. But I added though HA afterwards, so I’m not sure if HA was there in the Nuki later on, so I didn’t check. The Nuki website it only supports the ones you see. But that is clearly wrong, I got it working. The initial problems could have been for two reasons:
I had factory reset the router for some other problems and restored a backup on it. The hubs may not have reregistered with dns properly afterward, requiring them to reboot.
I also have problems with mdns only working a certain time after a device reboot. I have several esp32 devices suffering from the same thing, ESPHome no longer seeing them after a while. Others work just fine. I see more reports from people suffering the same fate. Maybe my Fritz!Box is not so good with mdns, it could also be my switches with IGMP snooping on (required for iptv) messing things up.
Mdns trouble may be why my connection is not very stable.
Ipv6 settings for HA can be checked on the network tab in settings. It must be set to automatic or static.
If I remember correctly, I opened the Nuki app to add matter (I assumed it was needed to activate matter an/or enter pairing mode). But HA wasn’t there, so I left the page open, manually opened HA, went to devices and continued the process there. After that the Nuki app showed Matter was configured.
(After looking back at some notes), a non-HA mobile App for Matter/Thread will not find HA Matter Server, but it is possible (but may be App dependent) for it to find HA’s Thread Network, get the Thread Creds from HA’s Thread Integration, and commission the Device onto the HA Thread network, and if successful, it may ask you to choose another App to do the Matter Commissioning, and from the list should be HA Companion App, and from there do the HA Matter Add Device as you mentioned.
did the same and it nearly worked … but instead of your successfull integration I ended up with an error in the nuki app … will try again and post some more details once i am back home
thanx
I wanted to share my success story in getting some TP-Link Tapo plugs discovered through Matter. No matter what I tried, I couldn’t get the plugs adopted in Home Assistant nor Google Home. I then found the solution on YouTube!
YouTube creator Eric Welander gave me the solution in his “BEFORE getting Matter devices” video that IPV6 needs to be enabled on your network to allow Matter devices to get a required IPV6 address!!! I had disabled IPV6 on my OPNsense firewall across all networks and the WAN. Nobody mentions enabling IPV6 for Matter and I never saw it mentioned in the HA docs! Once enabled and configured, the plugs were instantly found and adopted!
I just wanted to share the solution in case anybody else is having adoption issues.
Thanks a lot! I have been trying for days to connect Aquara U200 to HA via matter (connected to Amazon ECHO). My IPV6 was disabled, enabling it did the trick!
I have registered Aqara U200 on a network without IPv6 enabled… it could be a coincidence but maybe it is due to problems with multicast traffic (mDNS) on your network?
Yes, router/firewall and switchs with ipv6 and MLD disabled, no DHCPv6 (statefull)
Despite having these functions disabled, HA, Matter server and Thread devices will automatically use ipv6 (stateless). should “autoconfigure”
all within the same VLAN.
Although I am really testing with virtualized HAOS inside a QNAP NAS and it does not seem that communication is established through stateless IPv6… I have to do some more testing and verify that the Zyxel ATP firewall does not block multicast traffic (mDNS)
OK, that’s what I thought you meant …
Its the Thread Border Router (TBR) that is sending out IPv6 SLAAC advertised prefixes over the LAN that HA (and others) uses to autoconfigure its IPv6 addresses and this is what makes Matter over Thread work. Note that if there is no TBR, then Matter over WiFi doesn’t work so well unless something like the home router has IPv6 enabled on its LAN side and sending out SLAAC advertised prefixes.
But the IPv6 communication between wifi/mobile and HA seems not to work to link a new device… I can ping with IPv6, on the network but not against HA… even with fixed IPv6 or setting a DHCPv6 server (statefull) with a prefix, HA seems not to acquire it… the curious thing is that the same virtual switch gives access with IPv4 without problem …
