Level Lock Failed Commissioning

Configuration Matter/Thread
1

I am running Home Assistant in a Docker setup, configured OTBR, Thread, and Matter. Using a Sonoff Zigbee Dongle flashed with the OpenThread RCP firmware. All containers are up, no obvious errors that I can see. I’ve created the Thread network, connected the OTBR. I go to pair the Level lock with the Companion App on Android and it finds the device, connects, passes all the credentials, and then eventual fails with a “Something went wrong” error.

The Matter logs below:

2025-10-18 17:28:27.450 (MainThread) INFO [matter_server.server.stack] Initializing CHIP/Matter Logging...
2025-10-18 17:28:27.451 (MainThread) INFO [matter_server.server.stack] Initializing CHIP/Matter Controller Stack...
[1760808507.483459][1:1] CHIP:CTL: Setting attestation nonce to random value
[1760808507.483740][1:1] CHIP:CTL: Setting CSR nonce to random value
[1760808507.484576][1:1] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_kvs
[1760808507.489556][1:1] CHIP:DL: Wrote settings to /tmp/chip_kvs
[1760808507.489964][1:1] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_factory.ini
[1760808507.490169][1:1] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_config.ini
[1760808507.490324][1:1] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_counters.ini
[1760808507.494014][1:1] CHIP:DL: Wrote settings to /data/chip_counters.ini
[1760808507.494206][1:1] CHIP:DL: NVS set: chip-counters/reboot-count = 95 (0x5F)
[1760808507.494687][1:1] CHIP:DL: Got Ethernet interface: enp1s0
[1760808507.495006][1:1] CHIP:DL: Found the primary Ethernet interface:enp1s0
[1760808507.495272][1:1] CHIP:DL: Got WiFi interface: wlp2s0
[1760808507.495573][1:1] CHIP:DL: Found the primary WiFi interface:wlp2s0
[1760808507.495640][1:1] CHIP:PAF: WiFiPAF: WiFiPAFLayer::Init()
2025-10-18 17:28:27.495 (MainThread) INFO [chip.storage] Initializing persistent storage from file: /data/chip.json
2025-10-18 17:28:27.496 (MainThread) INFO [chip.storage] Loading configuration from /data/chip.json...
2025-10-18 17:28:27.593 (MainThread) INFO [chip.CertificateAuthority] Loading certificate authorities from storage...
2025-10-18 17:28:27.593 (MainThread) INFO [chip.CertificateAuthority] New CertificateAuthority at index 1
2025-10-18 17:28:27.594 (MainThread) INFO [chip.CertificateAuthority] Loading fabric admins from storage...
2025-10-18 17:28:27.594 (MainThread) INFO [chip.FabricAdmin] New FabricAdmin: FabricId: 0x0000000000000001, VendorId = 0xFFF1
2025-10-18 17:28:27.595 (MainThread) INFO [matter_server.server.stack] CHIP Controller Stack initialized.
2025-10-18 17:28:27.595 (MainThread) INFO [matter_server.server.server] Matter Server initialized
2025-10-18 17:28:27.595 (MainThread) INFO [matter_server.server.server] Using 'enp1s0' as primary interface (for link-local addresses)
2025-10-18 17:28:27.596 (MainThread) INFO [matter_server.server.server] Starting the Matter Server...
2025-10-18 17:28:27.600 (MainThread) INFO [matter_server.server.helpers.paa_certificates] Skip fetching certificates (already fetched within the last 24h).
2025-10-18 17:28:27.600 (MainThread) INFO [chip.FabricAdmin] Allocating new controller with CaIndex: 1, FabricId: 0x0000000000000001, NodeId: 0x000000000001B669, CatTags: []
2025-10-18 17:28:27.652 (Dummy-2) CHIP_ERROR [chip.native.DIS] Failed to advertise records: src/inet/UDPEndPointImplSockets.cpp:417: OS Error 0x02000065: Network is unreachable
2025-10-18 17:28:27.667 (MainThread) INFO [matter_server.server.vendor_info] Loading vendor info from storage.
2025-10-18 17:28:27.671 (MainThread) INFO [matter_server.server.vendor_info] Loaded 358 vendors from storage.
2025-10-18 17:28:27.671 (MainThread) INFO [matter_server.server.vendor_info] Fetching the latest vendor info from DCL.
2025-10-18 17:28:27.909 (MainThread) INFO [matter_server.server.vendor_info] Fetched 357 vendors from DCL.
2025-10-18 17:28:27.909 (MainThread) INFO [matter_server.server.vendor_info] Saving vendor info to storage.
2025-10-18 17:28:27.912 (MainThread) INFO [matter_server.server.device_controller] Loaded 0 nodes from stored configuration
2025-10-18 17:28:27.942 (MainThread) INFO [matter_server.server.server] Matter Server successfully initialized.
2025-10-18 17:42:35.642 (MainThread) INFO [matter_server.server.device_controller] Starting Matter commissioning using Node ID 11 and IP fdff:ceb9:fbdf:1:f3ae:43fd:f1b6:e534.
2025-10-18 17:42:37.354 (Dummy-2) INFO [chip.ChipDeviceCtrl] Established secure session with Device
2025-10-18 17:43:32.218 (Dummy-2) CHIP_ERROR [chip.native.CTL] Error on commissioning step 'SendPAICertificateRequest': 'src/app/CommandSender.cpp:354: CHIP Error 0x00000032: Timeout'
2025-10-18 17:43:32.561 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to send Solitary ack for MessageCounter:222097813 on exchange 33107i with Node: <0000000000000000, 0>:src/messaging/ExchangeContext.cpp:99: CHIP Error 0x00000002: Connection aborted
2025-10-18 17:43:32.562 (Dummy-2) WARNING [chip.ChipDeviceCtrl] Failed to commission: src/app/CommandSender.cpp:354: CHIP Error 0x00000032: Timeout
2025-10-18 17:43:32.563 (MainThread) ERROR [matter_server.server.client_handler] [140438453292832] Error while handling: commission_on_network: Commissioning failed for node 11.

I then have to factory reset to get it to attempt to pair again. I have IPv6 working. I don’t have any other Matter devices on the network. I have tried both the HASS version of the OTRB and the vanilla version. It seems like the network isn’t the issue as it looks like to has an established connection. But failing on the handshake/exchange.

2

Scrapped the container based install and went HAOS route. Was it’s own little nightmare but finally got it working. After restoring the backup there was some phantom setting someplace that was holding on to the old Thread network. Even after re-installing the add-ons and everything, removing the Thread network, re-setting, etc, etc, etc any time I tried to add the Level lock with my phone (Android) it would tell me that it couldn’t connect to the very much deleted Thread network. I used the troubleshooting section of the companion app to resync the Thread credentials, I remove the companion app and re-installed, I deleted cache and data from Google Play Store…finally just installed the companion app on my wife’s phone, synced the credentials in the troubleshooting section of the app, then added the lock through the Matter integration (add device)…and that finally got it working.

So…all of my configurations matched between my own container build and the HOAS build, but there is something certainly off someplace…either way, its working.

3

And…then it failed…my lock was dropping off every couple of hours. It became available and nothing could really get it to come back online. And then it would magically re-appear work for a couple hours and then become unavailable. Repeat.

I noticed that IPv6 addresses were showing as not-reachable, and what I noticed is that I could ping any IPv6 that was issued from my router (Unifi devices)…none of the link-local IPs could be reached. I suspected that there was a bridging issue between my LAN and the Matter / Thread network. I saw in another post that IPv6 was not required on the LAN, just on the Matter network, so I disabled IPv6 on my LAN, restarted the OTBR and the Matter integration and then restarted the lock, and after a minute or so it was fine…and then became unavailable an hour or so later. I gave up on it for a bit and let it sit and after about 4 hours it suddenly became pretty solid through the rest of the night. As of this morning the device became unavailable for a few minutes but has otherwise been fine. I’m not sure if moving the Home Assistant device closer will solve this. Debating about moving it closer just to see what happens.

4

I’m curious why some folks are getting responses from the team for similar issues while others (such as me) are essentially getting ignored.

5

Just an update, talking to the clouds, I guess…complete fail on the entire matter network yesterday. Made sure IPv6 was enabled on the LAN interface but I do not have IPv6 enable on my LAN (meaning the Unifi network). My entire HA host hard locked at some point, did a reboot (forced) and everything came back up except for Matter and tons of errors on the border router. Stopped both of them, check configs, restarted border router, and then matter, the device was still not connecting…restarted that lock (weird to say that). And after an hour it finally connected, and things have been fine since 730 last night.