core: Cannot add Matter devices

The problem

I am not able to connect any Matter Device. When starting the Matter Server, the errors and warnings about MDNS below appear in the log (though I don’t think it has anything to do with it). When I initiate the pairing process, the errors further down in the log appear, which seem to have something to do with BLE and timeouts.

What version of Home Assistant Core has the issue?

core-2023.11.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Matter

Link to integration documentation on our website

https://www.home-assistant.io/integrations/matter/

Diagnostics information

{ “home_assistant”: { “installation_type”: “Home Assistant OS”, “version”: “2023.11.3”, “dev”: false, “hassio”: true, “virtualenv”: false, “python_version”: “3.11.6”, “docker”: true, “arch”: “aarch64”, “timezone”: “Europe/Berlin”, “os_name”: “Linux”, “os_version”: “6.1.21-v8”, “supervisor”: “2023.11.6”, “host_os”: “Home Assistant OS 11.1”, “docker_version”: “24.0.6”, “chassis”: “embedded”, “run_as_root”: true }, “custom_components”: { “alexa_media”: { “version”: “4.8.0”, “requirements”: [ “alexapy==1.27.10”, “packaging>=20.3”, “wrapt>=1.14.0” ] }, “circadian_lighting”: { “version”: “2.1.4”, “requirements”: [] }, “hacs”: { “version”: “1.33.0”, “requirements”: [ “aiogithubapi>=22.10.1” ] } }, “integration_manifest”: { “domain”: “matter”, “name”: “Matter (BETA)”, “codeowners”: [ “@home-assistant/matter” ], “config_flow”: true, “dependencies”: [ “websocket_api” ], “documentation”: “https://www.home-assistant.io/integrations/matter”, “iot_class”: “local_push”, “requirements”: [ “python-matter-server==4.0.2” ], “is_built_in”: true }, “data”: { “server”: { “info”: { “fabric_id”: 2, “compressed_fabric_id”: 9525509635650634147, “schema_version”: 4, “min_supported_schema_version”: 2, “sdk_version”: “2023.10.2”, “wifi_credentials_set”: false, “thread_credentials_set”: false }, “nodes”: [], “events”: [] } } }

Example YAML snippet

No response

Anything in the logs that might be useful for us?

2023-12-02 16:49:03 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on wlan0 for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2023-12-02 16:49:04 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on veth449f29e for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2023-12-02 16:49:04 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on vethf8f2135 for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2023-12-02 16:49:04 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on veth272ee1f for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2023-12-02 16:49:04 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on vethe8fdcc4 for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2023-12-02 16:49:04 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on veth7b66f80 for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2023-12-02 16:49:04 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on vethb6609e8 for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2023-12-02 16:49:04 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on veth9535d6f for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2023-12-02 16:49:04 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on veth7944fda for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2023-12-02 16:49:04 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on veth28f112c for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2023-12-02 16:49:04 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on veth7f78f30 for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2023-12-02 16:49:04 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on wpan0 for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2023-12-02 16:49:05 core-matter-server CertificateAuthorityManager[126] WARNING Loading certificate authorities from storage...
2023-12-02 16:49:05 core-matter-server CertificateAuthority[126] WARNING New CertificateAuthority at index 1
2023-12-02 16:49:05 core-matter-server CertificateAuthority[126] WARNING Loading fabric admins from storage...

...
...
...

2023-12-02 16:55:19 core-matter-server matter_server.server.helpers.paa_certificates[126] INFO Fetching the latest PAA root certificates from DCL.
2023-12-02 16:55:20 core-matter-server matter_server.server.helpers.paa_certificates[126] INFO Fetched 0 PAA root certificates from DCL.
2023-12-02 16:55:20 core-matter-server matter_server.server.helpers.paa_certificates[126] INFO Fetching the latest PAA root certificates from Git.
2023-12-02 16:55:20 core-matter-server matter_server.server.helpers.paa_certificates[126] INFO Fetched 0 PAA root certificates from Git.
2023-12-02 16:55:20 core-matter-server chip.DL[126] ERROR Long dispatch time: 298 ms, for event type 2
2023-12-02 16:55:30 core-matter-server chip.CTL[126] ERROR Commissioning discovery over BLE failed: src/platform/Linux/bluez/ChipDeviceScanner.cpp:173: CHIP Error 0x00000032: Timeout
2023-12-02 16:55:30 core-matter-server chip.-[126] ERROR src/platform/Linux/bluez/ChipDeviceScanner.cpp:173: CHIP Error 0x00000032: Timeout at src/controller/SetUpCodePairer.cpp:324
2023-12-02 16:55:30 core-matter-server chip.BLE[126] ERROR BLE scan error: src/platform/Linux/bluez/ChipDeviceScanner.cpp:173: CHIP Error 0x00000032: Timeout
2023-12-02 16:55:31 core-matter-server chip.EM[126] ERROR Failed to Send CHIP MessageCounter:111146596 on exchange 37781i sendCount: 4 max retries: 4
2023-12-02 16:55:50 core-matter-server chip.CTL[126] ERROR Discovery timed out
2023-12-02 16:56:02 core-matter-server chip.SC[126] ERROR PASESession timed out while waiting for a response from the peer. Expected message type was 35
2023-12-02 16:56:02 core-matter-server chip.ZCL[126] ERROR Secure Pairing Failed
2023-12-02 16:56:02 core-matter-server matter_server.server.client_handler[126] ERROR [547916403344] Error handling message: CommandMessage(message_id='505b3325ca24476fbf19f157d7daa2f8', command='commission_with_code', args={'code': '11397736342'})
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 173, in commission_with_code
    raise NodeCommissionFailed(
matter_server.common.errors.NodeCommissionFailed: Commission with code failed for node 8

Additional information

No response

About this issue

  • Original URL
  • State: closed
  • Created 7 months ago
  • Reactions: 1
  • Comments: 18 (4 by maintainers)

Most upvoted comments

@CaliLuke The advice is generally to make sure you have no mDNS responders. I thought I was following that advice, but then did some more looking and realized that Apple Bojour is a mDNS responder that is common in Windows PCs with iTunes

So, if you’re a Windows / iTunes user, check your installed Windows programs from the control panel and remove Bonjour.

Once I did that, I had greatly improved luck adding sensors and devices.

I have a house full of Macs, an Apple TV and a Google Home screen. If other devices capable or hearing multicast are an issue then the Matter integration is pointless as it’s not built for realistic scenarios.

Nuked (stopped it from running, it’s still on the computer) Avahi-daemon on all my Linux servers and now I can add Matter devices when before I was getting core-matter-server chip.DIS[126] ERROR Failed to parse mDNS query

systemctl mask avahi-daemon

https://ubuntuforums.org/showthread.php?t=2425530 https://ccm.net/computing/linux/2253-disabling-the-avahi-daemon/