I’ve been running Matter server for over a year now. HAOS, bare metal rpi3b. Been working relatively okay until last night.
Last night I noticed that all my Matter devices were offline. Restarting the integration didn’t help so went to the Matter server add-on, and saw that all my nodes are gone. Last evening I’ve upgraded to latest HA Core 2024.12.3, I can’t recall if the issues started directly after or are unrelated. No other update or change has taken place that I’m aware of.
I’ve read other posts that mentioned such issue but mostly it turned out the OPs reinstalled their add-on, which by design cleared all their devices’ data. I did not touch the add-on, except restarting it to try and resolve this, which didn’t help.
My latest back-up is from a couple of weeks ago, so I’d rather not restore unless there is absolutely no other way.
Even though I am very technical, I am really not a power user on this platform, and often get overwhelmed when reading proposed solutions. If you could be so kind as to respond as for a simple user I would appreciate it and provide any info necessary.
I’ve enabled trace logging for the add-on. Below are logs of the version, warnings and errors since last reboot, if I can provide additional traces around one of these please let me know.
Following the “network unreachable”, based on other posts, I went to HA network settings to ensure my ipv6 is still open. It is. However… I’ve been trying to wreck my brain if my network interface was always called by the strange name ENU1U1U1. Doesn’t sound familiar. Could it have been renamed in the last update and have any influence on this? Sorry if completely unrelated, I’m probably reaching in the dark here.
===
Add-on version: 6.6.1
You are running the latest version of this add-on.
System: Home Assistant OS 14.0 (aarch64 / raspberrypi3-64)
Home Assistant Core: 2024.12.3
Home Assistant Supervisor: 2024.11.4
===
2024-12-14 07:05:01.930 (MainThread) WARNING [py.warnings] /usr/local/lib/python3.12/site-packages/matter_server/server/helpers/paa_certificates.py:132: 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 X.509 certificate parsing error in v41.0.0, not observed in v38.0.4, v40.0.2 · Issue #8996 · pyca/cryptography · GitHub and Cryptography 41.0.2 fails to parse certificate signed with DSA · Issue #9253 · pyca/cryptography · GitHub for more details.
===
2024-12-14 07:05:05.055 (Dummy-2) CHIP_ERROR [chip.native.DIS] Failed to advertise records: src/inet/UDPEndPointImplSockets.cpp:416: OS Error 0x02000065: Network is unreachable
===
2024-12-14 07:05:05.101 (Dummy-2) CHIP_ERROR [chip.native.DL] Long dispatch time: 912 ms, for event type 2
===
2024-12-14 07:05:05.636 (MainThread) WARNING [zeroconf] Error with socket 49 ((‘::1’, 5353, 0, 0))): [Errno 101] Network is unreachable
Traceback (most recent call last):
File “/usr/local/lib/python3.12/asyncio/selector_events.py”, line 1275, in sendto
self._sock.sendto(data, addr)
OSError: [Errno 101] Network is unreachable
