Matter (Beta) integration

Hi HA community,

I am trying to integrate a KASA/TAPO matter-based smart switch KP125M to the HA Matter (Beta) integration. I have a flat network behind the router. Yet, adding a device fails. I am able to add this same switch (and another matter dimmer) to the Samsung SmartThings station without any issues - so it is unlikely that my network is the issue. Can someone help?

HA info:
Home Assistant 2023.8.4
Supervisor 2023.08.1
Operating System 10.5
Frontend 20230802.1 - latest

Matter server version: 4.9.0

Here’s the Matter Server log:

‘’’
2023-09-01 13:25:05 core-matter-server chip.DMG[126] DEBUG ICR moving to [AddedComma]
2023-09-01 13:25:05 core-matter-server chip.EM[126] INFO <<< [E:39086i S:17259 M:15537546] (S) Msg TX to 0:FFFFFFFB00000000 [0000] — Type 0001:08 (IM:InvokeCommandRequest)
2023-09-01 13:25:05 core-matter-server chip.IN[126] INFO (S) Sending msg 15537546 on secure session with LSID: 17259
2023-09-01 13:25:05 core-matter-server chip.DMG[126] DEBUG ICR moving to [CommandSen]
2023-09-01 13:25:05 core-matter-server chip.DMG[126] DEBUG ICR moving to [AwaitingDe]
2023-09-01 13:25:11 core-matter-server chip.EM[126] DEBUG Retransmitting MessageCounter:15537546 on exchange 39086i Send Cnt 1
2023-09-01 13:25:11 core-matter-server chip.IN[126] INFO (S) Sending msg 15537546 on secure session with LSID: 17259
2023-09-01 13:25:16 core-matter-server chip.EM[126] DEBUG Retransmitting MessageCounter:15537546 on exchange 39086i Send Cnt 2
2023-09-01 13:25:16 core-matter-server chip.IN[126] INFO (S) Sending msg 15537546 on secure session with LSID: 17259
2023-09-01 13:25:27 core-matter-server chip.EM[126] DEBUG Retransmitting MessageCounter:15537546 on exchange 39086i Send Cnt 3
2023-09-01 13:25:27 core-matter-server chip.IN[126] INFO (S) Sending msg 15537546 on secure session with LSID: 17259
2023-09-01 13:25:35 core-matter-server chip.DIS[126] ERROR DNSSD packet parsing failed (for SRV records)
2023-09-01 13:25:35 core-matter-server chip.DIS[126] ERROR DNSSD packet parsing failed (for non-srv records)
2023-09-01 13:25:35 core-matter-server chip.DIS[126] ERROR DNSSD packet parsing failed (for SRV records)
2023-09-01 13:25:35 core-matter-server chip.DIS[126] ERROR DNSSD packet parsing failed (for non-srv records)
2023-09-01 13:25:35 core-matter-server chip.DIS[126] ERROR DNSSD packet parsing failed (for SRV records)
2023-09-01 13:25:35 core-matter-server chip.DIS[126] ERROR DNSSD packet parsing failed (for non-srv records)
2023-09-01 13:25:35 core-matter-server chip.DIS[126] ERROR DNSSD packet parsing failed (for SRV records)
2023-09-01 13:25:35 core-matter-server chip.DIS[126] ERROR DNSSD packet parsing failed (for non-srv records)
2023-09-01 13:25:35 core-matter-server chip.DIS[126] ERROR DNSSD packet parsing failed (for SRV records)
2023-09-01 13:25:35 core-matter-server chip.DIS[126] ERROR DNSSD packet parsing failed (for non-srv records)
2023-09-01 13:25:35 core-matter-server chip.DIS[126] ERROR DNSSD packet parsing failed (for SRV records)
2023-09-01 13:25:35 core-matter-server chip.DIS[126] ERROR DNSSD packet parsing failed (for non-srv records)
2023-09-01 13:25:41 core-matter-server chip.EM[126] DEBUG Retransmitting MessageCounter:15537546 on exchange 39086i Send Cnt 4
2023-09-01 13:25:41 core-matter-server chip.IN[126] INFO (S) Sending msg 15537546 on secure session with LSID: 17259
2023-09-01 13:26:06 core-matter-server chip.EM[126] ERROR Failed to Send CHIP MessageCounter:15537546 on exchange 39086i sendCount: 4 max retries: 4
2023-09-01 13:26:18 core-matter-server chip.DMG[126] INFO Time out! failed to receive invoke command response from Exchange: 39086i
2023-09-01 13:26:18 core-matter-server chip.CTL[126] INFO Received failure response when disarming failsafesrc/app/CommandSender.cpp:248: CHIP Error 0x00000032: Timeout
2023-09-01 13:26:18 core-matter-server chip.CTL[126] INFO Successfully finished commissioning step ‘Cleanup’
2023-09-01 13:26:18 core-matter-server chip.IN[126] DEBUG SecureSession[0xffff6c01aba0]: MarkForEviction Type:1 LSID:17259
2023-09-01 13:26:18 core-matter-server matter_server.server.device_controller[126] DEBUG Interviewing node: 7
2023-09-01 13:26:18 core-matter-server chip.SC[126] INFO SecureSession[0xffff6c01aba0]: Moving from state ‘kActive’ → ‘kPendingEviction’
2023-09-01 13:26:18 core-matter-server matter_server.server.device_controller[126] DEBUG Attempting to resolve node 7…
2023-09-01 13:26:18 core-matter-server chip.IN[126] DEBUG SecureSession[0xffff6c01aba0]: Released - Type:1 LSID:17259
2023-09-01 13:26:18 core-matter-server chip.DMG[126] DEBUG ICR moving to [AwaitingDe]
2023-09-01 13:26:18 core-matter-server chip.CSM[126] DEBUG FindOrEstablishSession: PeerId = [1:0000000000000007]
2023-09-01 13:26:18 core-matter-server chip.CSM[126] DEBUG FindOrEstablishSession: No existing OperationalSessionSetup instance found
2023-09-01 13:26:18 core-matter-server chip.DIS[126] DEBUG OperationalSessionSetup[1:0000000000000007]: State change 1 → 2
2023-09-01 13:26:18 core-matter-server chip.DIS[126] INFO Checking node lookup status after 200 ms
2023-09-01 13:26:49 core-matter-server chip.DIS[126] ERROR Timeout waiting for mDNS resolution.
2023-09-01 13:27:03 core-matter-server chip.DIS[126] INFO Checking node lookup status after 45010 ms
2023-09-01 13:27:03 core-matter-server chip.DIS[126] ERROR OperationalSessionSetup[1:0000000000000007]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:114: CHIP Error 0x00000032: Timeout
2023-09-01 13:27:03 core-matter-server matter_server.server.device_controller[126] DEBUG Attempting to resolve node 7…
2023-09-01 13:27:03 core-matter-server chip.CSM[126] DEBUG FindOrEstablishSession: PeerId = [1:0000000000000007]
2023-09-01 13:27:03 core-matter-server chip.CSM[126] DEBUG FindOrEstablishSession: No existing OperationalSessionSetup instance found
2023-09-01 13:27:03 core-matter-server chip.DIS[126] DEBUG OperationalSessionSetup[1:0000000000000007]: State change 1 → 2
2023-09-01 13:27:03 core-matter-server chip.DIS[126] INFO Checking node lookup status after 201 ms
2023-09-01 13:27:34 core-matter-server chip.DIS[126] ERROR Timeout waiting for mDNS resolution.
2023-09-01 13:27:48 core-matter-server chip.DIS[126] INFO Checking node lookup status after 45003 ms
2023-09-01 13:27:48 core-matter-server chip.DIS[126] ERROR OperationalSessionSetup[1:0000000000000007]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:114: CHIP Error 0x00000032: Timeout
2023-09-01 13:27:48 core-matter-server matter_server.server.device_controller[126] DEBUG Attempting to resolve node 7…
2023-09-01 13:27:48 core-matter-server chip.CSM[126] DEBUG FindOrEstablishSession: PeerId = [1:0000000000000007]
2023-09-01 13:27:48 core-matter-server chip.CSM[126] DEBUG FindOrEstablishSession: No existing OperationalSessionSetup instance found
2023-09-01 13:27:48 core-matter-server chip.DIS[126] DEBUG OperationalSessionSetup[1:0000000000000007]: State change 1 → 2
2023-09-01 13:27:48 core-matter-server chip.DIS[126] INFO Checking node lookup status after 201 ms
2023-09-01 13:28:19 core-matter-server chip.DIS[126] ERROR Timeout waiting for mDNS resolution.
2023-09-01 13:28:33 core-matter-server chip.DIS[126] INFO Checking node lookup status after 45002 ms
2023-09-01 13:28:33 core-matter-server chip.DIS[126] ERROR OperationalSessionSetup[1:0000000000000007]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:114: CHIP Error 0x00000032: Timeout
2023-09-01 13:28:33 core-matter-server matter_server.server.client_handler[126] ERROR [281472721071888] Error handling message: CommandMessage(message_id=‘31085f1fcc824888a457c9122878620c’, command=‘commission_on_network’, args={‘setup_pin_code’: 99225754})
Traceback (most recent call last):
File “/usr/local/lib/python3.11/site-packages/matter_server/server/device_controller.py”, line 889, in _resolve_node
await self._call_sdk(
File “/usr/local/lib/python3.11/site-packages/matter_server/server/device_controller.py”, line 766, in _call_sdk
await self.server.loop.run_in_executor(
File “/usr/local/lib/python3.11/concurrent/futures/thread.py”, line 58, in run
result = self.fn(*self.args, **self.kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/local/lib/python3.11/site-packages/chip/ChipDeviceCtrl.py”, line 491, in ResolveNode
self.GetConnectedDeviceSync(nodeid, allowPASE=False)
File “/usr/local/lib/python3.11/site-packages/chip/ChipDeviceCtrl.py”, line 731, in GetConnectedDeviceSync
returnErr.raise_on_error()
File “/usr/local/lib/python3.11/site-packages/chip/native/init.py”, line 67, in raise_on_error
raise self.to_exception()
chip.exceptions.ChipStackError: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:114: CHIP Error 0x00000032: Timeout
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File “/usr/local/lib/python3.11/site-packages/matter_server/server/device_controller.py”, line 304, in interview_node
await self._resolve_node(node_id=node_id)
File “/usr/local/lib/python3.11/site-packages/matter_server/server/device_controller.py”, line 897, in _resolve_node
await self._resolve_node(node_id=node_id, retries=retries - 1)
File “/usr/local/lib/python3.11/site-packages/matter_server/server/device_controller.py”, line 897, in _resolve_node
await self._resolve_node(node_id=node_id, retries=retries - 1)
File “/usr/local/lib/python3.11/site-packages/matter_server/server/device_controller.py”, line 896, in _resolve_node
raise NodeNotResolving(f"Unable to resolve Node {node_id}") from err
matter_server.common.errors.NodeNotResolving: Unable to resolve Node 7
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File “/usr/local/lib/python3.11/site-packages/matter_server/server/client_handler.py”, line 188, in _run_handler
result = await result
^^^^^^^^^^^^
File “/usr/local/lib/python3.11/site-packages/matter_server/server/device_controller.py”, line 221, in commission_on_network
await self.interview_node(node_id)
File “/usr/local/lib/python3.11/site-packages/matter_server/server/device_controller.py”, line 314, in interview_node
raise NodeInterviewFailed(f"Failed to interview node {node_id}") from err
matter_server.common.errors.NodeInterviewFailed: Failed to interview node 7
‘’’

Thanks in advance

I am having this exact same issue. I had other Kasa switches and bought this thinking it would work the same. It does not unfortunately. I saw someone posted an GitHub Issue on this but then closed it. I am using the Docker container but it has host networking access so I don’t understand what the issue is. I am able to add the matter-server docker container as an integration. When I try to scan the QR code to add a device it fails. The funny thing is the device does get added. When I open the Kasa app it had already found it.