Matter-Thread Via ATV4K / Yale Door Lock

[somber heath]

I have been at this for the better part of the day. I run HAOS as a KVM VM on top of a small home server. I run Unifi as my router. I have done/confirmed the following

• IPv6 is enabled. All of my devices get both a GUA and ULA address as well as a LL. My Apple TV has the same.
• I have verified that Multicast Enhancement, mDNS, and IGMP Snooping are disabled on the UDM
• Everything is on the same subnet. The ATV is Wi-Fi and the HAOS box is hard-wired
• Non-Thread devices work fine, I have a small ESP32 based Matter test and I can add it to either Apple Home or HA and share it to the other no problem

I can successfully, after a reset, add this Yale Matter lock to Apple Home. I can control the lock no problem.
I cannot add the lock to Home Assistant, either by sharing it from Apple Home (via code) to to HA, or by resetting the lock and adding it to HA directly.

This leads me to believe there’s and issue with ipv6/threads/thread bridge that I can’t seem to solve.

Here’s the log of me trying to add the device directly to HA: https://pastebin.com/6LnM0nvR
Here’s the log of me trying to add the device to HA once it’s been added to Apple Home first: https://pastebin.com/28y4sHMF

I can ping6 to a public host (e.g. google.com) and I can ping6 to my AppleTV from my HAOS console.

Any ideas?

Unfortunately, I also don’t have any other Matter/Thread combined devices to test with, only the Matter over WiFi ESP32 thing.

Some other info, the host is Ubuntu 24.04, Kernel 6.14. HAOS is running latest version of everything.

[somber heath]

2025-04-23 23:20:38.078 (Dummy-2) CHIP_ERROR [chip.native.EM] <<5 [E:34085i with Node: <0000000000000000, 0> S:0 M:213577762] (U) Msg Retransmission to 0:0000000000000000 failure (max retries:4)
2025-04-23 23:20:53.620 (Dummy-2) CHIP_ERROR [chip.native.SC] PASESession timed out while waiting for a response from the peer. Expected message type was 33```

[copper patrol]

You should be able to discover the device's service records via dnssd and ping its IPv6 address.

have you set the ATV's PAN as the preferred network in HA?

[somber heath]

Yes, it’s preferred and I’ve sent the credentials from my phone via the companion app

[somber heath]

it has to be something on my network or the device itself. I stood up a brand new HAOS on virtual box on my desktop pc and having the same issue adding it. I just don't know what the issue might be...

[somber heath]

ok we have something! It's a WiFi issue. I plugged my ATV into an ethernet port and it paired successfully

what does that mean though...

it's a route issue... my VM isn't getting the fd81 route via RA when the appletv is on wifi

[primal wolf]

Is this a U7 series Unifi AP perhaps ?

[somber heath]

it is....

please don't tell me that is the problem

[primal wolf]

Unifi in general are reported as troublesome, the whole industry is complaining about them and they dont care

The U7 series in general has mdns issues all around

[somber heath]

I know, if I could rip it all out and just do eero or something I would they've been garbage

as soon as I put the ATV back on wifi it all stops working

I wonder if it's also a WPA3 or MLO thing. I should try my ATV on my IoT SSID (same subnet just a dedicated IoT subnet)

same issue

[primal wolf]

I'm not sure. The U6 series should work with all their "optimizations" crap disabled pretty fine but U7 has been reported as not working at all, it even causes troubles with Ipv4 mdns so not specific to Matter (over Thread)

[somber heath]

that sucks, though I do have an old old in wall AC device, let me force the appletv to connect to that to test the theory

[primal wolf]

Try to bring it down as simple as possible and then enable features again one by one until it breaks

[somber heath]

Do you know which settings should be enabled for the SSID? Such as Multicast Enhancement, Multicast and Broadcast Control - and for the network IGMP Snooping or mDNS?

[primal wolf]

Everything Unifi calls an "enhancement" can actually be seen as a muticast killer

[somber heath]

ok so all off

[primal wolf]

Yes, exactly

[somber heath]

son of a bitch

I connected the appletv to my old in wall ac unit and it works perfectly

AP AC IW

wifi 5 or something

[primal wolf]

Those settings make sense in a high density corporate network where multicast is killing performance but not in a small residential network

[somber heath]

so it really is the U7 regardless of configuration...

[primal wolf]

Yeah, you are not the first to report issues with U7 series

[somber heath]

damn, I wasted SO much time yesterday

you are the legend of matter though so I appreciate the reply. I am going to try to downgrade the U7 to the non MLO release and see if that changes anything. I do suppose ~350mbps is enough for streaming and I can leave it force connected to the old AP though until something changes

hey just since you're here - I added the device to homekit first, asked me for a lock code. is t expected that when in HA i need to use the lock code to lock/unlock the device whereas in Home it lets me do so without the code?

[primal wolf]

Each controller you add it to can have its own security

[somber heath]

I see, how would I adjust the lock code from the HA side if initially paired to HK

[primal wolf]

So in HA, you need to enter the code in the lock settings

[somber heath]

is that defined in the device?

oh, default code, I see it in the lock entity properties

thanks!

honestly you saved my day I would've probably banged my head against that for the next 72 hours

OH Fixed a regression in which IPv6 Router Advertisements were not being forwarded from wireless clients to the UAP’s LAN side.

there's a bugfix for the exact problem I am having

it works, with the updated FW

[primal wolf]

Nice!

[copper patrol]

@somber heath - so the fix was with the lock, not in the U7? Asking, because I have two U7 Pro Wall on 8.0.19 in the mix, and generally have not experienced these issues (MLO turned off though).

[somber heath]

No the fix was in the U7.

The firmware I was on had a regression which was blocking RAs from WLAN to LAN

[true crystal]

I have 4 U7-Pros and 2 U7-Pro-Max. IGMP-Snooping, mDNS, mDNS Enhancement, Broadcast Control and Proxy ARP settings are disabled.

My 2 Apple TVs are connected via Ethernet. My 5 HomePods are connected via WPA2-PPSK (Private Pre-Shared Key). My iPhones are connected via WPA3-Enterprise. MLO is disabled.

udm-se: 4.1.13
network application: 9.0.114
u-lte-backup-pro: 7.0.96
1x usw-pro-aggregation: 7.1.26
1x usw-pro-max-48-poe: 7.1.26
1x usw-pro-max-16-poe: 7.1.26
2x u7-pro-max: 8.0.19
4x u7-pro: 8.0.19

No issues here.

There are some reports in the Unifi AP Beta firmware threads, that there are problems with IPv6 RAs, but those are also reported as solved with firmware 8.0.31. In the release notes you find the following bugfix:
————————
Fixed a regression in which IPv6 Router Advertisements were not being forwarded from wireless clients to the UAP’s LAN side.
————————

https://community.ui.com/releases/UniFi-Access-Point-all-U7-and-E7-models-8-0-31/e0cfae0b-5fc3-4023-9efe-cbf2036c1b8b#comment/0c9608c6-3c78-4930-8599-983e2d1233d2

I do not have the time for beta testing at the moment. 8.0.19 works fine.

[copper patrol]

@true crystal -- good to know, thanks for sharing.