core
core copied to clipboard
Published
20 hours ago •
home-assistant
home-assistant
Container of Matter-Server(5.5.1) stopped work after upgrade
The problem
I just update from 5.4.1 to current stable one 5.5.1
The log is:
[1707344510.628373][1:1] CHIP:CTL: Setting attestation nonce to random value
[1707344510.628436][1:1] CHIP:CTL: Setting CSR nonce to random value
[1707344510.629122][1:1] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_kvs
[1707344510.629202][1:1] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_factory.ini
[1707344510.629278][1:1] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_config.ini
[1707344510.629312][1:1] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_counters.ini
[1707344510.629436][1:1] CHIP:DL: writing settings to file (/data/chip_counters.ini-ldbeGh)
[1707344510.629579][1:1] CHIP:DL: renamed tmp file to file (/data/chip_counters.ini)
[1707344510.629590][1:1] CHIP:DL: NVS set: chip-counters/reboot-count = 21 (0x15)
[1707344510.630027][1:1] CHIP:DL: Failed to get Ethernet interface
[1707344510.630328][1:1] CHIP:DL: Failed to reset Ethernet statistic counts
[1707344510.630576][1:1] CHIP:DL: Got WiFi interface: wlo1
[1707344510.630589][1:1] CHIP:DL: Failed to reset WiFi statistic counts
2024-02-07 17:21:50 upstairs-server PersistentStorage[1] WARNING Initializing persistent storage from file: /data/chip.json
2024-02-07 17:21:50 upstairs-server PersistentStorage[1] WARNING Loading configuration from /data/chip.json...
2024-02-07 17:21:50 upstairs-server chip.DL[1] ERROR MDNS failed to join multicast group on vethc3d2917 for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2024-02-07 17:21:50 upstairs-server CertificateAuthorityManager[1] WARNING Loading certificate authorities from storage...
2024-02-07 17:21:50 upstairs-server CertificateAuthority[1] WARNING New CertificateAuthority at index 1
2024-02-07 17:21:50 upstairs-server CertificateAuthority[1] WARNING Loading fabric admins from storage...
2024-02-07 17:21:50 upstairs-server FabricAdmin[1] WARNING New FabricAdmin: FabricId: 0x0000000000000001, VendorId = 0xFFF1
2024-02-07 17:21:50 upstairs-server matter_server.server.stack[1] INFO CHIP Controller Stack initialized.
2024-02-07 17:21:50 upstairs-server matter_server.server.server[1] INFO Starting the Matter Server...
2024-02-07 17:21:50 upstairs-server matter_server.server.helpers.paa_certificates[1] INFO Fetching the latest PAA root certificates from DCL.
/usr/local/lib/python3.11/concurrent/futures/thread.py:58: CryptographyDeprecationWarning: The parsed certificate contains a NULL parameter value in its signature algorithm parameters. This is invalid and will be rejected in a future version of cryptography. If this certificate was created via Java, please upgrade to JDK21+ or the latest JDK11/17 once a fix is issued. If this certificate was created in some other fashion please report the issue to the cryptography issue tracker. See https://github.com/pyca/cryptography/issues/8996 and https://github.com/pyca/cryptography/issues/9253 for more details.
result = self.fn(*self.args, **self.kwargs)
2024-02-07 17:21:56 upstairs-server matter_server.server.helpers.paa_certificates[1] INFO Fetched 124 PAA root certificates from DCL.
2024-02-07 17:21:56 upstairs-server matter_server.server.helpers.paa_certificates[1] INFO Fetching the latest PAA root certificates from Git.
2024-02-07 17:21:56 upstairs-server matter_server.server.helpers.paa_certificates[1] INFO Fetched 2 PAA root certificates from Git.
2024-02-07 17:21:56 upstairs-server FabricAdmin[1] WARNING Allocating new controller with CaIndex: 1, FabricId: 0x0000000000000001, NodeId: 0x000000000001B669, CatTags: []
2024-02-07 17:21:56 upstairs-server matter_server.server.device_controller[1] INFO Loaded 8 nodes from stored configuration
2024-02-07 17:21:56 upstairs-server matter_server.server.vendor_info[1] INFO Loading vendor info from storage.
2024-02-07 17:21:56 upstairs-server matter_server.server.vendor_info[1] INFO Loaded 160 vendors from storage.
2024-02-07 17:21:56 upstairs-server matter_server.server.vendor_info[1] INFO Fetching the latest vendor info from DCL.
2024-02-07 17:21:56 upstairs-server zeroconf[1] WARNING Error with socket 38 (('::1', 5353, 0, 0))): [Errno 101] Network is unreachable
Traceback (most recent call last):
File "/usr/local/lib/python3.11/asyncio/selector_events.py", line 1196, in sendto
self._sock.sendto(data, addr)
OSError: [Errno 101] Network is unreachable
2024-02-07 17:21:56 upstairs-server matter_server.server.vendor_info[1] INFO Fetched 158 vendors from DCL.
2024-02-07 17:21:56 upstairs-server matter_server.server.vendor_info[1] INFO Saving vendor info to storage.
I returned to 5.4.1 and now is working. It something on new version.
What version of Home Assistant Core has the issue?
2024.2.0
What was the last working version of Home Assistant Core?
2024.2.0
What type of installation are you running?
Home Assistant Container
Integration causing the issue
Matter
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
Hey there @home-assistant/matter, mind taking a look at this issue as it has been labeled with an integration (matter) you are listed as a code owner for? Thanks!
Code owner commands
Code owners of matter can trigger bot actions by commenting:
-
@home-assistant closeCloses the issue. -
@home-assistant rename Awesome new titleRenames the issue. -
@home-assistant reopenReopen the issue. -
@home-assistant unassign matterRemoves the current integration label and assignees on the issue, add the integration domain after the command. -
@home-assistant add-label needs-more-informationAdd a label (needs-more-information, problem in dependency, problem in custom component) to the issue. -
@home-assistant remove-label needs-more-informationRemove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.
(message by CodeOwnersMention)
matter documentation matter source (message by IssueLinks)
![home-assistant[bot] avatar](https://avatars.githubusercontent.com/in/97978?v=4 "Published by a pub.dev verified publisher"){kind=small}
I was having the same issue after the update. I selected "Add Entry" then added it again and it started working. i didn't delete anything, just kinda reconfigured the integration. I'm using the Matter Server add-on though...
I was having the same issue after the update. I selected "Add Entry" then added it again and it started working. i didn't delete anything, just kinda reconfigured the integration. I'm using the Matter Server add-on though...
I tried this and I still get the same error. I even tried to latest beta toggle in the add on and that also did not work.
It's a bitt different for me. I have an Aqara Hub added via matter and all the devices and entities became unavailable. They still work in the Home.app. I've tried deleting and readding, restarting both the hub and HA. No dice.
Adding my log:
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service banner: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
-----------------------------------------------------------
Add-on: Matter Server
Matter WebSocket Server for Home Assistant Matter support.
-----------------------------------------------------------
Add-on version: 5.1.0
You are running the latest version of this add-on.
System: Home Assistant OS 11.5 (aarch64 / raspberrypi5-64)
Home Assistant Core: 2024.2.0
Home Assistant Supervisor: 2024.01.1
-----------------------------------------------------------
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service banner successfully started
s6-rc: info: service matter-server: starting
s6-rc: info: service matter-server successfully started
s6-rc: info: service legacy-services: starting
[08:45:28] INFO: Starting Matter Server...
s6-rc: info: service legacy-services successfully started
[08:45:28] INFO: Using 'end0' as primary network interface.
[08:45:28] INFO: Successfully send discovery information to Home Assistant.
2024-02-08 08:45:30 core-matter-server matter_server.server.stack[126] INFO Initializing CHIP/Matter Controller Stack...
[1707381930.079854][126:126] CHIP:CTL: Setting attestation nonce to random value
[1707381930.079950][126:126] CHIP:CTL: Setting CSR nonce to random value
[1707381930.080719][126:126] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_kvs
[1707381930.080890][126:126] CHIP:DL: writing settings to file (/tmp/chip_kvs-pZJ3NJ)
[1707381930.080957][126:126] CHIP:DL: renamed tmp file to file (/tmp/chip_kvs)
[1707381930.081039][126:126] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_factory.ini
[1707381930.081168][126:126] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_config.ini
[1707381930.081209][126:126] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_counters.ini
[1707381930.081358][126:126] CHIP:DL: writing settings to file (/data/chip_counters.ini-FfNoPH)
[1707381930.081514][126:126] CHIP:DL: renamed tmp file to file (/data/chip_counters.ini)
[1707381930.081526][126:126] CHIP:DL: NVS set: chip-counters/reboot-count = 26 (0x1A)
[1707381930.081926][126:126] CHIP:DL: Got Ethernet interface: end0
[1707381930.082134][126:126] CHIP:DL: Found the primary Ethernet interface:end0
[1707381930.082334][126:126] CHIP:DL: Got WiFi interface: wlan0
[1707381930.082356][126:126] CHIP:DL: Failed to reset WiFi statistic counts
2024-02-08 08:45:30 core-matter-server PersistentStorage[126] WARNING Initializing persistent storage from file: /data/chip.json
2024-02-08 08:45:30 core-matter-server PersistentStorage[126] WARNING Loading configuration from /data/chip.json...
2024-02-08 08:45:30 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
2024-02-08 08:45:30 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on veth2e87b18 for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2024-02-08 08:45:30 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on veth881785b for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2024-02-08 08:45:30 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on veth7b51f0d for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2024-02-08 08:45:30 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on veth05d3dd3 for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2024-02-08 08:45:30 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on veth8d18b6d for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2024-02-08 08:45:30 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on vethd1820d9 for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2024-02-08 08:45:30 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on veth9871fa6 for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2024-02-08 08:45:30 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on veth851a04d for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2024-02-08 08:45:30 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
2024-02-08 08:45:30 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on veth7ec8e40 for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2024-02-08 08:45:30 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on vethc7ec38d for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2024-02-08 08:45:30 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on veth52c4c4e for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2024-02-08 08:45:30 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on veth29b3eda for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2024-02-08 08:45:30 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on veth065ef6e for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2024-02-08 08:45:30 core-matter-server CertificateAuthorityManager[126] WARNING Loading certificate authorities from storage...
2024-02-08 08:45:30 core-matter-server CertificateAuthority[126] WARNING New CertificateAuthority at index 1
2024-02-08 08:45:30 core-matter-server CertificateAuthority[126] WARNING Loading fabric admins from storage...
2024-02-08 08:45:30 core-matter-server FabricAdmin[126] WARNING New FabricAdmin: FabricId: 0x0000000000000002, VendorId = 0x134B
2024-02-08 08:45:30 core-matter-server matter_server.server.stack[126] INFO CHIP Controller Stack initialized.
2024-02-08 08:45:30 core-matter-server matter_server.server.server[126] INFO Starting the Matter Server...
2024-02-08 08:45:30 core-matter-server matter_server.server.helpers.paa_certificates[126] INFO Fetching the latest PAA root certificates from DCL.
/usr/local/lib/python3.11/concurrent/futures/thread.py:58: CryptographyDeprecationWarning: The parsed certificate contains a NULL parameter value in its signature algorithm parameters. This is invalid and will be rejected in a future version of cryptography. If this certificate was created via Java, please upgrade to JDK21+ or the latest JDK11/17 once a fix is issued. If this certificate was created in some other fashion please report the issue to the cryptography issue tracker. See https://github.com/pyca/cryptography/issues/8996 and https://github.com/pyca/cryptography/issues/9253 for more details.
result = self.fn(*self.args, **self.kwargs)
2024-02-08 08:45:40 core-matter-server matter_server.server.helpers.paa_certificates[126] INFO Fetched 124 PAA root certificates from DCL.
2024-02-08 08:45:40 core-matter-server matter_server.server.helpers.paa_certificates[126] INFO Fetching the latest PAA root certificates from Git.
2024-02-08 08:45:41 core-matter-server matter_server.server.helpers.paa_certificates[126] INFO Fetched 2 PAA root certificates from Git.
2024-02-08 08:45:41 core-matter-server FabricAdmin[126] WARNING Allocating new controller with CaIndex: 1, FabricId: 0x0000000000000002, NodeId: 0x000000000001B669, CatTags: []
2024-02-08 08:45:41 core-matter-server matter_server.server.device_controller[126] INFO Loaded 1 nodes from stored configuration
2024-02-08 08:45:41 core-matter-server matter_server.server.vendor_info[126] INFO Loading vendor info from storage.
2024-02-08 08:45:41 core-matter-server matter_server.server.vendor_info[126] INFO Loaded 160 vendors from storage.
2024-02-08 08:45:41 core-matter-server matter_server.server.vendor_info[126] INFO Fetching the latest vendor info from DCL.
2024-02-08 08:45:41 core-matter-server zeroconf[126] WARNING Error with socket 70 (('::1', 5353, 0, 0))): [Errno 101] Network is unreachable
Traceback (most recent call last):
File "/usr/local/lib/python3.11/asyncio/selector_events.py", line 1196, in sendto
self._sock.sendto(data, addr)
OSError: [Errno 101] Network is unreachable
2024-02-08 08:45:41 core-matter-server matter_server.server.vendor_info[126] INFO Fetched 158 vendors from DCL.
2024-02-08 08:45:41 core-matter-server matter_server.server.vendor_info[126] INFO Saving vendor info to storage.
I have the same problem. I downgraded from a backup to previous version (5.1.0) and it works. Every time there is a matter upgrade there is a problem, it's a nightmare
I'm using Home Assistant OS in a VM on Unraid. Upgrading caused my Matter to quit working too. Error from Home Assistant is "Failed to connect to matter server".
I suspect the error is a result of this change:
Matter Server Logs
s6-rc: info: service legacy-services: starting
[02:22:01] INFO: Starting Matter Server...
s6-rc: info: service legacy-services successfully started
[02:22:01] INFO: Using 'enp1s0' as primary network interface.
[02:22:01] INFO: Successfully send discovery information to Home Assistant.
2024-02-08 02:22:02 core-matter-server matter_server.server.stack[126] INFO Initializing CHIP/Matter Controller Stack...
[1707384122.609636][126:126] CHIP:CTL: Setting attestation nonce to random value
[1707384122.609732][126:126] CHIP:CTL: Setting CSR nonce to random value
[1707384122.610210][126:126] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_kvs
[1707384122.610285][126:126] CHIP:DL: writing settings to file (/tmp/chip_kvs-6BjQWG)
[1707384122.610339][126:126] CHIP:DL: renamed tmp file to file (/tmp/chip_kvs)
[1707384122.610408][126:126] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_factory.ini
[1707384122.610627][126:126] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_config.ini
[1707384122.610756][126:126] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_counters.ini
[1707384122.610858][126:126] CHIP:DL: writing settings to file (/data/chip_counters.ini-zEpUfJ)
[1707384122.610958][126:126] CHIP:DL: renamed tmp file to file (/data/chip_counters.ini)
[1707384122.610973][126:126] CHIP:DL: NVS set: chip-counters/reboot-count = 4 (0x4)
[1707384122.611224][126:126] CHIP:DL: Got Ethernet interface: enp1s0
[1707384122.611350][126:126] CHIP:DL: Found the primary Ethernet interface:enp1s0
[1707384122.611598][126:126] CHIP:DL: Failed to get WiFi interface
[1707384122.611611][126:126] CHIP:DL: Failed to reset WiFi statistic counts
2024-02-08 02:22:02 core-matter-server PersistentStorage[126] WARNING Initializing persistent storage from file: /data/chip.json
2024-02-08 02:22:02 core-matter-server PersistentStorage[126] WARNING Loading configuration from /data/chip.json...
2024-02-08 02:22:02 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on veth5372da5 for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2024-02-08 02:22:02 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on vethf9a6e6a for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2024-02-08 02:22:02 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on veth19b53bf for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2024-02-08 02:22:02 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on veth5400ee8 for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2024-02-08 02:22:02 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on veth7d6663d for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2024-02-08 02:22:02 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on vethe9e085e for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2024-02-08 02:22:02 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on vethba80776 for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2024-02-08 02:22:02 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on veth41896fd for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2024-02-08 02:22:02 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on vethb5e3360 for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2024-02-08 02:22:02 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
2024-02-08 02:22:02 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on veth3e83116 for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2024-02-08 02:22:02 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on vetha096412 for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2024-02-08 02:22:02 core-matter-server CertificateAuthorityManager[126] WARNING Loading certificate authorities from storage...
2024-02-08 02:22:02 core-matter-server CertificateAuthority[126] WARNING New CertificateAuthority at index 1
2024-02-08 02:22:02 core-matter-server CertificateAuthority[126] WARNING Loading fabric admins from storage...
2024-02-08 02:22:02 core-matter-server FabricAdmin[126] WARNING New FabricAdmin: FabricId: 0x0000000000000002, VendorId = 0x134B
2024-02-08 02:22:02 core-matter-server matter_server.server.stack[126] INFO CHIP Controller Stack initialized.
2024-02-08 02:22:02 core-matter-server matter_server.server.server[126] INFO Starting the Matter Server...
2024-02-08 02:22:02 core-matter-server matter_server.server.helpers.paa_certificates[126] INFO Fetching the latest PAA root certificates from DCL.
/usr/local/lib/python3.11/concurrent/futures/thread.py:58: CryptographyDeprecationWarning: The parsed certificate contains a NULL parameter value in its signature algorithm parameters. This is invalid and will be rejected in a future version of cryptography. If this certificate was created via Java, please upgrade to JDK21+ or the latest JDK11/17 once a fix is issued. If this certificate was created in some other fashion please report the issue to the cryptography issue tracker. See https://github.com/pyca/cryptography/issues/8996 and https://github.com/pyca/cryptography/issues/9253 for more details.
result = self.fn(*self.args, **self.kwargs)
2024-02-08 02:22:08 core-matter-server matter_server.server.helpers.paa_certificates[126] INFO Fetched 124 PAA root certificates from DCL.
2024-02-08 02:22:08 core-matter-server matter_server.server.helpers.paa_certificates[126] INFO Fetching the latest PAA root certificates from Git.
2024-02-08 02:22:08 core-matter-server matter_server.server.helpers.paa_certificates[126] INFO Fetched 2 PAA root certificates from Git.
2024-02-08 02:22:08 core-matter-server FabricAdmin[126] WARNING Allocating new controller with CaIndex: 1, FabricId: 0x0000000000000002, NodeId: 0x000000000001B669, CatTags: []
2024-02-08 02:22:08 core-matter-server matter_server.server.device_controller[126] INFO Loaded 10 nodes from stored configuration
2024-02-08 02:22:08 core-matter-server matter_server.server.vendor_info[126] INFO Loading vendor info from storage.
2024-02-08 02:22:08 core-matter-server matter_server.server.vendor_info[126] INFO Loaded 155 vendors from storage.
2024-02-08 02:22:08 core-matter-server matter_server.server.vendor_info[126] INFO Fetching the latest vendor info from DCL.
2024-02-08 02:22:08 core-matter-server zeroconf[126] WARNING Error with socket 75 (('::1', 5353, 0, 0))): [Errno 101] Network is unreachable
Traceback (most recent call last):
File "/usr/local/lib/python3.11/asyncio/selector_events.py", line 1196, in sendto
self._sock.sendto(data, addr)
OSError: [Errno 101] Network is unreachable
2024-02-08 02:22:08 core-matter-server matter_server.server.device_controller[126] INFO Node 16 discovered on MDNS
2024-02-08 02:22:08 core-matter-server matter_server.server.device_controller.[node 16][126] INFO Setting up attributes and events subscription.
2024-02-08 02:22:08 core-matter-server matter_server.server.vendor_info[126] INFO Fetched 158 vendors from DCL.
2024-02-08 02:22:08 core-matter-server matter_server.server.vendor_info[126] INFO Saving vendor info to storage.
2024-02-08 02:22:08 core-matter-server matter_server.server.device_controller[126] INFO Node 1 discovered on MDNS
2024-02-08 02:22:08 core-matter-server matter_server.server.device_controller.[node 1][126] INFO Setting up attributes and events subscription.
2024-02-08 02:22:08 core-matter-server matter_server.server.device_controller[126] INFO Node 5 discovered on MDNS
2024-02-08 02:22:08 core-matter-server matter_server.server.device_controller.[node 5][126] INFO Setting up attributes and events subscription.
2024-02-08 02:22:08 core-matter-server matter_server.server.device_controller[126] INFO Node 15 discovered on MDNS
2024-02-08 02:22:08 core-matter-server matter_server.server.device_controller.[node 15][126] INFO Setting up attributes and events subscription.
2024-02-08 02:22:08 core-matter-server matter_server.server.device_controller[126] INFO Node 3 discovered on MDNS
2024-02-08 02:22:08 core-matter-server matter_server.server.device_controller.[node 3][126] INFO Setting up attributes and events subscription.
2024-02-08 02:22:08 core-matter-server matter_server.server.device_controller[126] INFO Node 6 discovered on MDNS
2024-02-08 02:22:08 core-matter-server matter_server.server.device_controller.[node 6][126] INFO Setting up attributes and events subscription.
2024-02-08 02:22:08 core-matter-server matter_server.server.device_controller[126] INFO Node 12 discovered on MDNS
2024-02-08 02:22:08 core-matter-server matter_server.server.device_controller.[node 12][126] INFO Setting up attributes and events subscription.
2024-02-08 02:22:08 core-matter-server matter_server.server.device_controller[126] INFO Node 14 discovered on MDNS
2024-02-08 02:22:08 core-matter-server matter_server.server.device_controller.[node 14][126] INFO Setting up attributes and events subscription.
2024-02-08 02:22:10 core-matter-server matter_server.server.device_controller.[node 16][126] INFO Subscription succeeded
2024-02-08 02:22:12 core-matter-server matter_server.server.device_controller.[node 1][126] INFO Subscription succeeded
2024-02-08 02:22:15 core-matter-server matter_server.server.device_controller.[node 5][126] INFO Subscription succeeded
2024-02-08 02:22:16 core-matter-server matter_server.server.device_controller.[node 15][126] INFO Subscription succeeded
2024-02-08 02:22:18 core-matter-server matter_server.server.device_controller.[node 3][126] INFO Subscription succeeded
2024-02-08 02:22:31 core-matter-server chip.EM[126] ERROR Failed to Send CHIP MessageCounter:98420999 on exchange 27220i sendCount: 4 max retries: 4
2024-02-08 02:22:32 core-matter-server matter_server.server.device_controller.[node 6][126] INFO Subscription succeeded
2024-02-08 02:22:33 core-matter-server matter_server.server.device_controller.[node 12][126] INFO Subscription succeeded
2024-02-08 02:23:02 core-matter-server chip.SC[126] ERROR CASESession timed out while waiting for a response from the peer. Current state was 3
2024-02-08 02:23:05 core-matter-server matter_server.server.device_controller[126] INFO Attempting to resolve node 14... (attempt 2 of 2)
2024-02-08 02:23:18 core-matter-server chip.SC[126] ERROR CASESession timed out while waiting for a response from the peer. Current state was 1
2024-02-08 02:23:18 core-matter-server matter_server.server.device_controller[126] WARNING Unable to subscribe to Node 14 as it is unavailable
2024-02-08 02:36:28 core-matter-server chip.DMG[126] ERROR Subscription Liveness timeout with SubscriptionID = 0x443bba24, Peer = 01:0000000000000006
2024-02-08 02:36:28 core-matter-server matter_server.server.device_controller.[node 6][126] INFO Previous subscription failed with Error: 50, re-subscribing in 0 ms...
2024-02-08 02:36:35 core-matter-server root[126] INFO Re-subscription succeeded!
2024-02-08 02:36:35 core-matter-server matter_server.server.device_controller.[node 6][126] INFO Re-Subscription succeeded
2024-02-08 02:40:58 core-matter-server matter_server.server.device_controller[126] INFO Node 1 vanished according to MDNS
2024-02-08 02:40:58 core-matter-server matter_server.server.device_controller[126] INFO Marked node 1 as offline
2024-02-08 03:06:12 core-matter-server matter_server.server.device_controller[126] INFO Node 14 discovered on MDNS
2024-02-08 03:06:12 core-matter-server matter_server.server.device_controller.[node 14][126] INFO Setting up attributes and events subscription.
2024-02-08 03:06:18 core-matter-server matter_server.server.device_controller.[node 14][126] INFO Subscription succeeded
2024-02-08 03:08:08 core-matter-server chip.DMG[126] ERROR Subscription Liveness timeout with SubscriptionID = 0x447fa479, Peer = 01:0000000000000006
2024-02-08 03:08:08 core-matter-server matter_server.server.device_controller.[node 6][126] INFO Previous subscription failed with Error: 50, re-subscribing in 0 ms...
2024-02-08 03:08:16 core-matter-server root[126] INFO Re-subscription succeeded!
2024-02-08 03:08:16 core-matter-server matter_server.server.device_controller.[node 6][126] INFO Re-Subscription succeeded
I fixed my problem. I had to edit the file .storage/core.config_entries and change ws://localhost:5580/ws to ws://core-matter-server:5580/ws in order to match the host name shown on the add-on page.
Then did a full reboot of Home Assistant, and my Matter devices are back online.
Pretty silly for a release to change the network configuration for everyone. Retaining settings for existing users would have been nice.
I fixed my problem. I had to edit the file
.storage/core.config_entriesand changews://localhost:5580/wstows://core-matter-server:5580/wsin order to match the host name shown on the add-on page.Then did a full reboot of Home Assistant, and my Matter devices are back online.
Pretty silly for a release to change the network configuration for everyone. Retaining settings for existing users would have been nice.
Mine is unchanged. It is still core-matter-server and hasn't changed. I'm going to try and restore from a backup.
HA 2024.2.1 will fix some issues introduced in 2024.2.0. For the Matter server we already released a patch release
I fixed my problem. I had to edit the file
.storage/core.config_entriesand changews://localhost:5580/wstows://core-matter-server:5580/wsin order to match the host name shown on the add-on page.Then did a full reboot of Home Assistant, and my Matter devices are back online.
Pretty silly for a release to change the network configuration for everyone. Retaining settings for existing users would have been nice.
Can you remember how you first configured Matter ? Did you just used the defaults and let the integration install the addon or did you manually specify the address ?
@MitchTalmadge the add-on by default sens out discover information with the URL ws://core-matter-server:5580/ws. Have you maybe removed the integration once and re-added with localhost instead?
Pretty silly for a release to change the network configuration for everyone. Retaining settings for existing users would have been nice.
Having the (unauthenticated) WebSocket open on all interfaces is from a security perspective not nice. The WebSocket service listening on all interfaces was a (temporary) missing feature of the Matter Server. Early versions of the Python Matter server (and add-on) listened on the internal interface only, and recently we've added back the capability to the Python Matter server. So this effectively just a fix, but for manually configured integration it might need action on users side, sorry about that :cry:
I already have ws://core-matter-server:5580/ws but it doesn't work.
Version: 5.1.1
@mattiaggg can you be a bit more specific what doesn't work? Is the integration not able to connect? If so, can you share the Python Matter Server logs?
@mattiaggg can you be a bit more specific what doesn't work? Is the integration not able to connect? If so, can you share the Python Matter Server logs?
yes, the matter devices are not available
This is the log:
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service banner: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
-----------------------------------------------------------
Add-on: Matter Server
Matter WebSocket Server for Home Assistant Matter support.
-----------------------------------------------------------
Add-on version: 5.1.1
You are running the latest version of this add-on.
System: Home Assistant OS 11.5 (aarch64 / raspberrypi4-64)
Home Assistant Core: 2024.2.0
Home Assistant Supervisor: 2024.01.1
-----------------------------------------------------------
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service banner successfully started
s6-rc: info: service matter-server: starting
s6-rc: info: service matter-server successfully started
s6-rc: info: service legacy-services: starting
[15:01:28] INFO: Starting Matter Server...
s6-rc: info: service legacy-services successfully started
[15:01:30] INFO: Using 'end0' as primary network interface.
[15:01:31] INFO: Successfully send discovery information to Home Assistant.
2024-02-08 15:01:35 core-matter-server matter_server.server.stack[126] INFO Initializing CHIP/Matter Controller Stack...
[1707400896.020843][126:126] CHIP:CTL: Setting attestation nonce to random value
[1707400896.021252][126:126] CHIP:CTL: Setting CSR nonce to random value
[1707400896.025434][126:126] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_kvs
[1707400896.027298][126:126] CHIP:DL: writing settings to file (/tmp/chip_kvs-kopYkH)
[1707400896.027837][126:126] CHIP:DL: renamed tmp file to file (/tmp/chip_kvs)
[1707400896.028218][126:126] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_factory.ini
[1707400896.029189][126:126] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_config.ini
[1707400896.029719][126:126] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_counters.ini
[1707400896.030385][126:126] CHIP:DL: writing settings to file (/data/chip_counters.ini-RDLBNH)
[1707400896.031634][126:126] CHIP:DL: renamed tmp file to file (/data/chip_counters.ini)
[1707400896.031740][126:126] CHIP:DL: NVS set: chip-counters/reboot-count = 14 (0xE)
[1707400896.032922][126:126] CHIP:DL: Got Ethernet interface: end0
[1707400896.033709][126:126] CHIP:DL: Found the primary Ethernet interface:end0
[1707400896.034422][126:126] CHIP:DL: Got WiFi interface: wlan0
[1707400896.034509][126:126] CHIP:DL: Failed to reset WiFi statistic counts
2024-02-08 15:01:36 core-matter-server PersistentStorage[126] WARNING Initializing persistent storage from file: /data/chip.json
2024-02-08 15:01:36 core-matter-server PersistentStorage[126] WARNING Loading configuration from /data/chip.json...
2024-02-08 15:01:36 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
2024-02-08 15:01:36 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on vethc7fe3e4 for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2024-02-08 15:01:36 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on vethe6fc199 for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2024-02-08 15:01:36 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on vethfdbb563 for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2024-02-08 15:01:36 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on veth05b8e78 for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2024-02-08 15:01:36 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on vethc45d3f2 for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2024-02-08 15:01:36 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on veth467886b for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2024-02-08 15:01:36 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on vethc3febde for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2024-02-08 15:01:36 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on veth20d940c for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2024-02-08 15:01:36 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on vethc74b233 for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2024-02-08 15:01:36 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on veth0376ca0 for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2024-02-08 15:01:36 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on vethb8d1cb1 for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2024-02-08 15:01:36 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on vethb7349f9 for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2024-02-08 15:01:36 core-matter-server CertificateAuthorityManager[126] WARNING Loading certificate authorities from storage...
2024-02-08 15:01:36 core-matter-server CertificateAuthority[126] WARNING New CertificateAuthority at index 1
2024-02-08 15:01:36 core-matter-server CertificateAuthority[126] WARNING Loading fabric admins from storage...
2024-02-08 15:01:36 core-matter-server FabricAdmin[126] WARNING New FabricAdmin: FabricId: 0x0000000000000002, VendorId = 0x134B
2024-02-08 15:01:36 core-matter-server matter_server.server.stack[126] INFO CHIP Controller Stack initialized.
2024-02-08 15:01:36 core-matter-server matter_server.server.server[126] INFO Starting the Matter Server...
2024-02-08 15:01:36 core-matter-server matter_server.server.helpers.paa_certificates[126] INFO Fetching the latest PAA root certificates from DCL.
/usr/local/lib/python3.11/concurrent/futures/thread.py:58: CryptographyDeprecationWarning: The parsed certificate contains a NULL parameter value in its signature algorithm parameters. This is invalid and will be rejected in a future version of cryptography. If this certificate was created via Java, please upgrade to JDK21+ or the latest JDK11/17 once a fix is issued. If this certificate was created in some other fashion please report the issue to the cryptography issue tracker. See https://github.com/pyca/cryptography/issues/8996 and https://github.com/pyca/cryptography/issues/9253 for more details.
result = self.fn(*self.args, **self.kwargs)
2024-02-08 15:01:47 core-matter-server matter_server.server.helpers.paa_certificates[126] INFO Fetched 124 PAA root certificates from DCL.
2024-02-08 15:01:47 core-matter-server matter_server.server.helpers.paa_certificates[126] INFO Fetching the latest PAA root certificates from Git.
2024-02-08 15:01:48 core-matter-server matter_server.server.helpers.paa_certificates[126] INFO Fetched 2 PAA root certificates from Git.
2024-02-08 15:01:48 core-matter-server FabricAdmin[126] WARNING Allocating new controller with CaIndex: 1, FabricId: 0x0000000000000002, NodeId: 0x000000000001B669, CatTags: []
2024-02-08 15:01:48 core-matter-server matter_server.server.device_controller[126] INFO Loaded 2 nodes from stored configuration
2024-02-08 15:01:48 core-matter-server matter_server.server.vendor_info[126] INFO Loading vendor info from storage.
2024-02-08 15:01:48 core-matter-server matter_server.server.vendor_info[126] INFO Loaded 158 vendors from storage.
2024-02-08 15:01:48 core-matter-server matter_server.server.vendor_info[126] INFO Fetching the latest vendor info from DCL.
2024-02-08 15:01:48 core-matter-server zeroconf[126] WARNING Error with socket 75 (('::1', 5353, 0, 0))): [Errno 101] Network is unreachable
Traceback (most recent call last):
File "/usr/local/lib/python3.11/asyncio/selector_events.py", line 1200, in sendto
self._sock.sendto(data, addr)
OSError: [Errno 101] Network is unreachable
2024-02-08 15:01:48 core-matter-server matter_server.server.vendor_info[126] INFO Fetched 158 vendors from DCL.
2024-02-08 15:01:48 core-matter-server matter_server.server.vendor_info[126] INFO Saving vendor info to storage
please wait for the HA update 2024.2.1 and let us know if you still have issues after updating. In the meanwhile you can restore a backup and return to HA 2024.1.x and the previous matter server if you need a working situation.
Please re-open if you still run into issues after updating to HA core 2024.2.1 Thanks!
hi @marcelveldt , I updated to last matter-server (5.5.2), still same problem. I believe it is on that log:
Traceback (most recent call last):
File "/usr/local/lib/python3.11/asyncio/selector_events.py", line 1200, in sendto
self._sock.sendto(data, addr)
OSError: [Errno 101] Network is unreachable
on version 5.4.1 is working and do not show that log error output.
You can ignore that warning, that is unrelated.
You will have to wait for HA core 2024.2.1, like I told above.
@felipefdl this is a warning, and I've analyzed it extensively, it is not the culprit (see https://github.com/python-zeroconf/python-zeroconf/issues/1357).
From your initial logs, I don't see an issue. The add-on seems to have started correctly. At this point the Core integration should connect to the add-on. Is it saying "Failed setup, will retry? If so, I'd suggest to remove the integration and readd it with the URL ws://core-matter-server:5580/ws.
@MitchTalmadge the add-on by default sens out discover information with the URL
ws://core-matter-server:5580/ws. Have you maybe removed the integration once and re-added with localhost instead?
I guess my situation is a weird one, I started in Home Assistant container with a Matter container alongside it, both on the host network. Then I migrated to Home Assistant OS. So it stayed as localhost and just kept working til now. Never really thought of it that way.
Having the (unauthenticated) WebSocket open on all interfaces is from a security perspective not nice. The WebSocket service listening on all interfaces was a (temporary) missing feature of the Matter Server. Early versions of the Python Matter server (and add-on) listened on the internal interface only, and recently we've added back the capability to the Python Matter server. So this effectively just a fix, but for manually configured integration it might need action on users side, sorry about that 😢
That makes sense, I see how my case is abnormal and I take the blame for it after reading your explanation. Thanks!
I fixed my problem. I had to edit the file
.storage/core.config_entriesand changews://localhost:5580/wstows://core-matter-server:5580/wsin order to match the host name shown on the add-on page.Then did a full reboot of Home Assistant, and my Matter devices are back online.
Pretty silly for a release to change the network configuration for everyone. Retaining settings for existing users would have been nice.
In my case this was the already present configuration, I had to downgrade the matter server to 5.0.2 to fix my issue.
after the update to 2024.2.1 the error is the same, and the devices are in "unknow state". I will go back to 5.0.4
`s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service banner: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
-----------------------------------------------------------
Add-on: Matter Server
Matter WebSocket Server for Home Assistant Matter support.
-----------------------------------------------------------
Add-on version: 5.1.1
You are running the latest version of this add-on.
System: Home Assistant OS 11.5 (aarch64 / raspberrypi4-64)
Home Assistant Core: 2024.2.1
Home Assistant Supervisor: 2024.01.1
-----------------------------------------------------------
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service banner successfully started
s6-rc: info: service matter-server: starting
s6-rc: info: service matter-server successfully started
s6-rc: info: service legacy-services: starting
[14:20:08] INFO: Starting Matter Server...
s6-rc: info: service legacy-services successfully started
[14:20:09] INFO: Using 'end0' as primary network interface.
[14:20:09] INFO: Successfully send discovery information to Home Assistant.
2024-02-09 14:20:14 core-matter-server matter_server.server.stack[126] INFO Initializing CHIP/Matter Controller Stack...
[1707484814.156585][126:126] CHIP:CTL: Setting attestation nonce to random value
[1707484814.157332][126:126] CHIP:CTL: Setting CSR nonce to random value
[1707484814.159446][126:126] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_kvs
[1707484814.161532][126:126] CHIP:DL: writing settings to file (/tmp/chip_kvs-JxfeMH)
[1707484814.162050][126:126] CHIP:DL: renamed tmp file to file (/tmp/chip_kvs)
[1707484814.162695][126:126] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_factory.ini
[1707484814.163541][126:126] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_config.ini
[1707484814.164386][126:126] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_counters.ini
[1707484814.165341][126:126] CHIP:DL: writing settings to file (/data/chip_counters.ini-POV9WI)
[1707484814.166256][126:126] CHIP:DL: renamed tmp file to file (/data/chip_counters.ini)
[1707484814.166621][126:126] CHIP:DL: NVS set: chip-counters/reboot-count = 16 (0x10)
[1707484814.167825][126:126] CHIP:DL: Got Ethernet interface: end0
[1707484814.168840][126:126] CHIP:DL: Found the primary Ethernet interface:end0
[1707484814.170156][126:126] CHIP:DL: Got WiFi interface: wlan0
[1707484814.170488][126:126] CHIP:DL: Failed to reset WiFi statistic counts
2024-02-09 14:20:14 core-matter-server PersistentStorage[126] WARNING Initializing persistent storage from file: /data/chip.json
2024-02-09 14:20:14 core-matter-server PersistentStorage[126] WARNING Loading configuration from /data/chip.json...
2024-02-09 14:20:14 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
2024-02-09 14:20:14 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on vethc7fe3e4 for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2024-02-09 14:20:14 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on vethe6fc199 for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2024-02-09 14:20:14 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on vethfdbb563 for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2024-02-09 14:20:14 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on veth05b8e78 for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2024-02-09 14:20:14 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on vethc45d3f2 for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2024-02-09 14:20:14 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on veth467886b for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2024-02-09 14:20:14 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on vethc3febde for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2024-02-09 14:20:14 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on veth20d940c for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2024-02-09 14:20:14 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on vethc74b233 for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2024-02-09 14:20:14 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on veth0376ca0 for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2024-02-09 14:20:14 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on vethb8d1cb1 for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2024-02-09 14:20:14 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on vethb7349f9 for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found
2024-02-09 14:20:14 core-matter-server CertificateAuthorityManager[126] WARNING Loading certificate authorities from storage...
2024-02-09 14:20:14 core-matter-server CertificateAuthority[126] WARNING New CertificateAuthority at index 1
2024-02-09 14:20:14 core-matter-server CertificateAuthority[126] WARNING Loading fabric admins from storage...
2024-02-09 14:20:14 core-matter-server FabricAdmin[126] WARNING New FabricAdmin: FabricId: 0x0000000000000002, VendorId = 0x134B
2024-02-09 14:20:14 core-matter-server matter_server.server.stack[126] INFO CHIP Controller Stack initialized.
2024-02-09 14:20:14 core-matter-server matter_server.server.server[126] INFO Starting the Matter Server...
2024-02-09 14:20:14 core-matter-server matter_server.server.helpers.paa_certificates[126] INFO Fetching the latest PAA root certificates from DCL.
/usr/local/lib/python3.11/concurrent/futures/thread.py:58: CryptographyDeprecationWarning: The parsed certificate contains a NULL parameter value in its signature algorithm parameters. This is invalid and will be rejected in a future version of cryptography. If this certificate was created via Java, please upgrade to JDK21+ or the latest JDK11/17 once a fix is issued. If this certificate was created in some other fashion please report the issue to the cryptography issue tracker. See https://github.com/pyca/cryptography/issues/8996 and https://github.com/pyca/cryptography/issues/9253 for more details.
result = self.fn(*self.args, **self.kwargs)
2024-02-09 14:20:26 core-matter-server matter_server.server.helpers.paa_certificates[126] INFO Fetched 125 PAA root certificates from DCL.
2024-02-09 14:20:26 core-matter-server matter_server.server.helpers.paa_certificates[126] INFO Fetching the latest PAA root certificates from Git.
2024-02-09 14:20:26 core-matter-server matter_server.server.helpers.paa_certificates[126] INFO Fetched 2 PAA root certificates from Git.
2024-02-09 14:20:26 core-matter-server FabricAdmin[126] WARNING Allocating new controller with CaIndex: 1, FabricId: 0x0000000000000002, NodeId: 0x000000000001B669, CatTags: []
2024-02-09 14:20:26 core-matter-server matter_server.server.device_controller[126] INFO Loaded 2 nodes from stored configuration
2024-02-09 14:20:26 core-matter-server matter_server.server.vendor_info[126] INFO Loading vendor info from storage.
2024-02-09 14:20:26 core-matter-server matter_server.server.vendor_info[126] INFO Loaded 160 vendors from storage.
2024-02-09 14:20:26 core-matter-server matter_server.server.vendor_info[126] INFO Fetching the latest vendor info from DCL.
2024-02-09 14:20:26 core-matter-server zeroconf[126] WARNING Error with socket 73 (('::1', 5353, 0, 0))): [Errno 101] Network is unreachable
Traceback (most recent call last):
File "/usr/local/lib/python3.11/asyncio/selector_events.py", line 1200, in sendto
self._sock.sendto(data, addr)
OSError: [Errno 101] Network is unreachable
2024-02-09 14:20:27 core-matter-server matter_server.server.vendor_info[126] INFO Fetched 158 vendors from DCL.
2024-02-09 14:20:27 core-matter-server matter_server.server.vendor_info[126] INFO Saving vendor info to storage.`
I can confirm. Updated to 2024.2.1 and then updated to matter server 5.1.1 and all devices are still not available.
Can you guys please join the conversation on discord ? We're discussing this issue there. Some people have this issue while it works just fine for others. We're trying to debug what is going on.
Ofcourse if you are dependent on the Matter server, revert to Matter server 5.0.4 and HA core 2024.1.x to have a working setup.
We found the issue - a new version of the matter server will now be published!