I just got my first thread/matter door sensor (Aqara P2) to replace a failed Z-Wave sensor and have it working on Alexa and Google but can’t integrate it to HA.
I am using an Echo 4th gen as the TBR then shared it out to Google which works fine. I then shared it again to add to HA but can’t seem to get it to add. It goes through “generating credentials” with a picture of the device then “connecting device to HA” where it sits for a minute then errors out “something went wrong”.
My devices are Echo 4th gen as TBR then a nest mini and nest wi-fi. I think the nest mini is actually polling the Echo 4 since the nest wi-fi router does not have Matter enabled yet even though there is a Thread radio. My HA instance has both the Matter add-on(server) as well as the Matter integration. I do get a log from the add-on as shown
2023-10-13 09:18:44 core-matter-server matter_server.server.helpers.paa_certificates[126] INFO Fetched 0 PAA root certificates from Git.
2023-10-13 09:19:16 core-matter-server chip.DIS[126] ERROR Timeout waiting for mDNS resolution.
2023-10-13 09:19:30 core-matter-server chip.DIS[126] ERROR OperationalSessionSetup[1:0000000000000001]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:114: CHIP Error 0x00000032: Timeout
2023-10-13 09:20:01 core-matter-server chip.DIS[126] ERROR Timeout waiting for mDNS resolution.
2023-10-13 09:20:15 core-matter-server chip.DIS[126] ERROR OperationalSessionSetup[1:0000000000000001]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:114: CHIP Error 0x00000032: Timeout
2023-10-13 09:20:46 core-matter-server chip.DIS[126] ERROR Timeout waiting for mDNS resolution.
2023-10-13 09:21:00 core-matter-server chip.DIS[126] ERROR OperationalSessionSetup[1:0000000000000001]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:114: CHIP Error 0x00000032: Timeout
2023-10-13 09:21:00 core-matter-server matter_server.server.client_handler[126] ERROR [548078692688] Error handling message: CommandMessage(message_id='a9df203ba95449658dafb46d319c964e', command='commission_on_network', args={'setup_pin_code': 80840612})
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 1
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 1
2023-10-14 06:36:33 core-matter-server matter_server.server.client_handler[126] WARNING [548078693712] Disconnected: Received non-Text message.
2023-10-14 06:39:52 core-matter-server matter_server.server.helpers.paa_certificates[126] INFO Fetching the latest PAA root certificates from DCL.
2023-10-14 06:39:53 core-matter-server matter_server.server.helpers.paa_certificates[126] INFO Fetched 3 PAA root certificates from DCL.
2023-10-14 06:39:53 core-matter-server matter_server.server.helpers.paa_certificates[126] INFO Fetching the latest PAA root certificates from Git.
2023-10-14 06:39:53 core-matter-server matter_server.server.helpers.paa_certificates[126] INFO Fetched 0 PAA root certificates from Git.
2023-10-14 06:40:25 core-matter-server chip.DIS[126] ERROR Timeout waiting for mDNS resolution.
2023-10-14 06:40:39 core-matter-server chip.DIS[126] ERROR OperationalSessionSetup[1:0000000000000002]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:114: CHIP Error 0x00000032: Timeout
2023-10-14 06:41:10 core-matter-server chip.DIS[126] ERROR Timeout waiting for mDNS resolution.
2023-10-14 06:41:24 core-matter-server chip.DIS[126] ERROR OperationalSessionSetup[1:0000000000000002]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:114: CHIP Error 0x00000032: Timeout
2023-10-14 06:41:55 core-matter-server chip.DIS[126] ERROR Timeout waiting for mDNS resolution.
2023-10-14 06:42:09 core-matter-server chip.DIS[126] ERROR OperationalSessionSetup[1:0000000000000002]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:114: CHIP Error 0x00000032: Timeout
2023-10-14 06:42:09 core-matter-server matter_server.server.client_handler[126] ERROR [548123978320] Error handling message: CommandMessage(message_id='3e889cf96c6942e8a7fb3c0352be91ed', command='commission_on_network', args={'setup_pin_code': 13376426})
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 2
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 2