Network is unreachable error on Matter add-on #3453
Labels
Comments
|
I'm seeing the same issue since upgrading to HA 2024.2.0 and matter server 5.1.0 and 5.1.1. And maybe unrelated but likely not, my Nanoleaf Lightstrip thread (HomeKit, not Matter) device is unreachable (and rebooting does not help). It previously acted a thread router. Upgrading to the matter server pre-release version via the config options didn't help either: |
|
Same issue I was seeing with 5.1.1. I reverted to a backup of 5.0.4 to get it working again. Not sure if it makes a difference, but I do have all my matter devices on a separate IoT subnet/VLAN. I added an extra network interface for HA so it could communicate with the IPv6 devices on this IoT network, which all works fine on 5.0.4. |
|
Same with 5.1.1. |
|
+1 |
|
After enabling "Use the latest beta version" in the matter addon configuration panel and rebooting the entire server (Advanced Options -> Reboot system) my matter devices are now available again, even with 5.1.1 of the addon. But I also enabled NAT64 in the config options of OTBR, so I can't say which of these changes solved the issue. EDIT: The exact error message above didn't reappear in the matter log, but in the next hours devices went offline again for no explainable reason. My thread network was never so unstable as it was in the past few days. |
|
Same here |
|
Version 5.1.2 seemed to fix this issue for me. My devices took much longer to become available than they did in 5.0.4, but so far so good. |
|
The error message is still present on v5.1.2. In addition to the previous error message, this new message also appeared: |
|
Edit: Looks like my issue was unrelated. My multi-WAN setup (multi-IPv6-prefix) caused the startup of the Matter Server to get permanently stuck at With Matter Server 5.1.2 I still get lots of errors like |
|
I am still having this error with version 5.1.2 and also tried the latest beta version. |
+1 FWIW, I'm also trying to get this to work across VLANs, but haven't had any success when moving everything into one network either. |
|
The "Network is unreachable" error is harmless. It comes from zeroconf trying to bind on the IPv6 loopback address. If you have any issues with your Matter devices, its not because of that error. |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the issue you are experiencing
This is what the logs show:
Even though that error is shown, I'm still able to control my matter device with no problems.
What type of installation are you running?
Home Assistant OS
Which operating system are you running on?
Home Assistant Operating System
Which add-on are you reporting an issue with?
CEC Scanner
What is the version of the add-on?
5.1.1
Steps to reproduce the issue
...
System Health information
System Information
Home Assistant Community Store
Home Assistant Cloud
Home Assistant Supervisor
Dashboards
Recorder
Anything in the Supervisor logs that might be useful for us?
No response
Anything in the add-on logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: