Can't add Aquara Matter over Thread contact sensor to HA

[keen helm]

I have both an Apple TV and a HomePod Mini acting as TBRs, and I have the thread credentials for both copied into the iOS Companion App, but I can't get the sensor commissioned to HA. It doesn't matter if I try to commission it directly using HA as primary controller, or commissioning to Apple Home (which works) and then sharing it. The Matter error is always the same:

[matter_server.server.device_controller] Starting Matter commissioning with code using Node ID 20.
2025-10-02 16:05:52.420 (Dummy-2) CHIP_ERROR [chip.native.CTL] Discovery timed out
2025-10-02 16:06:16.540 (Dummy-2) CHIP_ERROR [chip.native.EM] <<5 [E:41891i with Node: <0000000000000000, 0> S:0 M:108217871] (U) Msg Retransmission to 0:0000000000000000 failure (max retries:4)
2025-10-02 16:06:27.085 (Dummy-2) CHIP_ERROR [chip.native.SC] PASESession timed out while waiting for a response from the peer. Expected message type was 33
2025-10-02 16:07:17.705 (Dummy-2) CHIP_ERROR [chip.native.EM] <<5 [E:41892i with Node: <0000000000000000, 0> S:0 M:108217872] (U) Msg Retransmission to 0:0000000000000000 failure (max retries:4)
2025-10-02 16:07:31.570 (Dummy-2) CHIP_ERROR [chip.native.SC] PASESession timed out while waiting for a response from the peer. Expected message type was 33

Any thoughts on why this won't work? This is the first Thread device I've tried to connect.

[keen helm]

I also have a SONOFF zigbee radio installed, if that matter.
RPi 4.

iOS version 26.1 beta

[dusty violet]

There’s a timeout; did you see any promotion on iOS UI? Which phase did you have issue with, while it is “setting up” or “connecting to device”?

[keen helm]

It error's out on the setting up phase of that modal scene that pops up: when I try to commission it using HA as the primary, the sensor seems like it responds to the discovery because it seems to exit pairing mode, almost like HA is missing a the final part of a handshake.

I'm not at home right now, but I can enable debug logging on the Matter server when I get back and try it again.

[dusty violet]

Is that the first time you add the device or you were trying to share it from Apple Home with HA?

If that’s the case you can try to add it to Apple Home first and share it with HA via pairing code generated by Apple Home

In that case you will know if it’s the Apple’s fault failing to attach your device to Thread network

[keen helm]

I've tried it both when commissioning via HA directly, or via share code while paired with HomeKit: it's the same error either way

[keen helm]

Here's the debug log:

2025-10-05 20:27:19.278 (MainThread) INFO [matter_server.server.device_controller] Starting Matter commissioning with code using Node ID 22.
2025-10-05 20:27:19.321 (ThreadPoolExecutor-0_0) DEBUG [matter_server.server.storage] Saved data to persistent storage
2025-10-05 20:27:19.599 (MainThread) DEBUG [matter_server.server.device_controller.mdns] Discovered commissionable Matter node: AsyncServiceInfo(type='_matterc._udp.local.', name='C72CF29422A6C66D._matterc._udp.local.', addresses=[], port=5540, weight=0, priority=0, server='8A3D0664BEC59ACC.local.', properties={b'VP': b'4447+8194', b'DT': b'21', b'SII': b'5800', b'SAI': b'1050', b'SAT': b'300', b'T': b'0', b'D': b'785', b'CM': b'2', b'RI': b'0200818A3591283AFDE1673ABC381BA9337E', b'PH': b'36', b'PI': None}, interface_index=None)
2025-10-05 20:27:49.298 (Dummy-2) CHIP_ERROR [chip.native.CTL] Discovery timed out
2025-10-05 20:28:11.661 (Dummy-2) CHIP_ERROR [chip.native.EM] <<5 [E:11491i with Node: <0000000000000000, 0> S:0 M:263252423] (U) Msg Retransmission to 0:0000000000000000 failure (max retries:4)
2025-10-05 20:28:23.893 (Dummy-2) CHIP_ERROR [chip.native.SC] PASESession timed out while waiting for a response from the peer. Expected message type was 33

This is what I get when directly commissioning it to HA

[keen helm]

This is the debug level output when trying to commision the sensor via share code after pairing to HomeKit

[errant mulch]

Can you update the contact sensor to Firmware 1.0.2.0 (via Apple Home or Aqara App)? What Firmware does Apple home show currently?

[keen helm]

Firmware on the sensor is 1.0.1.1; I don't see an option to update the firmware in Apple Home, but I will see what I can do

According to https://www.reddit.com/r/Aqara/comments/1n9tgvh/new_firmware_1020_for_aqara_door_and_window/, FW v1.0.2.0 was revoked

[exotic tusk]

Same exact problem I had

It's most likely that your router is preventing HA from talking to your border routers

What I did to resolve it was buy another zigbee stick and flash thread firmware on it

and use that as a local border router for the HA

literally had the exact error

[keen helm]

Hmm... Do you have an extender/mesh network? I was reading something that said if you routers break multicast it can mess this process up; I figured since the layer 2 net is all the same it should be fine, but now I'm starting to wonder

[exotic tusk]

Nope just a single ISP router

[keen helm]

Well crap. I already have a SONOFF stick on the HA RPi4, and I don't think I could fit another one, even if I wanted to spend the extra money. I'm fairly familiar with network auditing tools; if anyone would like a .pcap file for analysis just tell me what kind of traffic I'm looking for and I can submit.

[exotic tusk]

with luck you have a router that actually lets you change settings unlike mine

[exotic tusk]

if there's a "filter multicast" or "igmp snooping" toggle, allow snooping and do not filter multicast

make sure client isolation / AP isolation is also off

[keen helm]

Okay, so there was an option that was enabled that was called, "Disable IGMP Proxying." I disabled and I'll let you know what happens

Adding it via share code worked! I'm going to try resetting it and pairing it to HA