Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Matter devices always offline after power outage #3666

Closed
ManiacMouse opened this issue Jun 27, 2024 · 4 comments
Closed

Matter devices always offline after power outage #3666

ManiacMouse opened this issue Jun 27, 2024 · 4 comments
Labels

Comments

@ManiacMouse
Copy link

Describe the issue you are experiencing

I have two Eve Energy devices connected using Matter. Its been working just fine for about half a year. During a power outage a couple of months ago, I had similar issues with the network being unreachable for the Matter Server, but it was resolved by just restarting HA and my Border-routers and its been working since even after regular updates of HA and the Matter Server addon.

Last night, I unpowered my whole house as that is the only way for me to unpower and reboot my solar panel inverter which was having issues unrelated to this. When starting everything up again, my two Eve Energy devices remain constantly offline and the Matter Server complains about the network being unreachable, but I have not made a single change to my network configuration or HA configuration, I just unpowered everything and then powered everything back on.

I have four Border-routers, three of them are Apple Homepod mini's and the other is a Google Nest Hub. They all show up in the HA Thread integration. If I restart them, they disappear and pop up again so clearly connectivity is there. Both Eve Energy devices are paired directly with HA. The Matter Server does discover the devices on MDNS, but fails to connect to them.

To solve this, I have tried restoring older backups of the Matter Server integration but with no luck. I've restarted HA, the Matter Server, the Eve Energy devices and the Border-routers many times. I have a UniFi based network which is configured according to recommendations with IGMP snooping and mDNS turned off and everything is on the same VLAN. I've even tried disabling all UniFi security features that could potentially block, but still no luck. I even enabled IPv6 on my LAN just cause, why not, but its made no difference either. My HA OS does not acquire an IPv6 address even it says IPv6 is enabled, but I also cannot see any IPv6 support in the /etc configuration files. But either way, things where working just fine without IPv6 on my LAN before so IPv6 should not be the issue here.

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?

Matter Server

What is the version of the add-on?

6.1.2

Steps to reproduce the issue

I don't know how to reproduce it. It was working for half a year, and now it is not. So I guess the steps are:

  1. Power off everything
  2. Power on everything

System Health information

System Information

version core-2024.6.4
installation_type Home Assistant OS
dev false
hassio true
docker true
user root
virtualenv false
python_version 3.12.2
os_name Linux
os_version 6.6.33-haos
arch x86_64
timezone Europe/Stockholm
config_dir /config
Home Assistant Cloud
logged_in false
can_reach_cert_server ok
can_reach_cloud_auth ok
can_reach_cloud ok
Home Assistant Supervisor
host_os Home Assistant OS 12.4
update_channel stable
supervisor_version supervisor-2024.06.2
agent_version 1.6.0
docker_version 26.1.4
disk_total 97.7 GB
disk_used 10.3 GB
healthy true
supported true
host_connectivity true
supervisor_connectivity true
ntp_synchronized true
virtualization kvm
board ova
supervisor_api ok
version_api ok
installed_addons Let's Encrypt (5.0.22), Studio Code Server (5.15.0), Piper (1.5.0), Z-Wave JS (0.6.2), Mosquitto broker (6.4.1), Matter Server (6.1.2)
Dashboards
dashboards 2
resources 0
views 1
mode storage
Recorder
oldest_recorder_run 19 juni 2024 kl. 02:30
current_recorder_run 26 juni 2024 kl. 04:27
estimated_db_size 361.46 MiB
database_engine sqlite
database_version 3.44.2
Spotify
api_endpoint_reachable ok

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?

-----------------------------------------------------------
 Add-on: Matter Server
 Matter WebSocket Server for Home Assistant Matter support.
-----------------------------------------------------------
 Add-on version: 6.1.2
 You are running the latest version of this add-on.
 System: Home Assistant OS 12.4  (amd64 / qemux86-64)
 Home Assistant Core: 2024.6.4
 Home Assistant Supervisor: 2024.06.2
-----------------------------------------------------------
 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
[01:42:53] INFO: Starting Matter Server...
s6-rc: info: service legacy-services successfully started
[01:42:53] INFO: Using 'enp0s2' as primary network interface.
[01:42:53] INFO: Successfully send discovery information to Home Assistant.
2024-06-27 01:42:54.323 (MainThread) INFO [matter_server.server.stack] Initializing CHIP/Matter Logging...
2024-06-27 01:42:54.323 (MainThread) INFO [matter_server.server.stack] Initializing CHIP/Matter Controller Stack...
[1719445374.341505][126:126] CHIP:CTL: Setting attestation nonce to random value
[1719445374.341686][126:126] CHIP:CTL: Setting CSR nonce to random value
[1719445374.342305][126:126] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_kvs
[1719445374.342473][126:126] CHIP:DL: writing settings to file (/tmp/chip_kvs-G49m2I)
[1719445374.342538][126:126] CHIP:DL: renamed tmp file to file (/tmp/chip_kvs)
[1719445374.342738][126:126] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_factory.ini
[1719445374.342861][126:126] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_config.ini
[1719445374.342961][126:126] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_counters.ini
[1719445374.343108][126:126] CHIP:DL: writing settings to file (/data/chip_counters.ini-pN4EzK)
[1719445374.343343][126:126] CHIP:DL: renamed tmp file to file (/data/chip_counters.ini)
[1719445374.343355][126:126] CHIP:DL: NVS set: chip-counters/reboot-count = 47 (0x2F)
[1719445374.343717][126:126] CHIP:DL: Got Ethernet interface: enp0s2
[1719445374.343949][126:126] CHIP:DL: Found the primary Ethernet interface:enp0s2
[1719445374.344352][126:126] CHIP:DL: Failed to get WiFi interface
[1719445374.344361][126:126] CHIP:DL: Failed to reset WiFi statistic counts
2024-06-27 01:42:54.344 (MainThread) WARNING [PersistentStorage] Initializing persistent storage from file: /data/chip.json
2024-06-27 01:42:54.344 (MainThread) WARNING [PersistentStorage] Loading configuration from /data/chip.json...
2024-06-27 01:42:54.385 (MainThread) WARNING [CertificateAuthorityManager] Loading certificate authorities from storage...
2024-06-27 01:42:54.385 (MainThread) WARNING [CertificateAuthority] New CertificateAuthority at index 1
2024-06-27 01:42:54.386 (MainThread) WARNING [CertificateAuthority] Loading fabric admins from storage...
2024-06-27 01:42:54.386 (MainThread) WARNING [FabricAdmin] New FabricAdmin: FabricId: 0x0000000000000002, VendorId = 0x134B
2024-06-27 01:42:54.386 (MainThread) INFO [matter_server.server.stack] CHIP Controller Stack initialized.
2024-06-27 01:42:54.386 (MainThread) INFO [matter_server.server.server] Starting the Matter Server...
2024-06-27 01:42:54.388 (MainThread) INFO [matter_server.server.helpers.paa_certificates] Skip fetching certificates (already fetched within the last 24h).
2024-06-27 01:42:54.388 (MainThread) WARNING [FabricAdmin] Allocating new controller with CaIndex: 1, FabricId: 0x0000000000000002, NodeId: 0x000000000001B669, CatTags: []
2024-06-27 01:42:54.464 (MainThread) INFO [matter_server.server.device_controller] Loaded 2 nodes from stored configuration
2024-06-27 01:42:54.467 (MainThread) INFO [matter_server.server.vendor_info] Loading vendor info from storage.
2024-06-27 01:42:54.469 (MainThread) INFO [matter_server.server.vendor_info] Loaded 212 vendors from storage.
2024-06-27 01:42:54.469 (MainThread) INFO [matter_server.server.vendor_info] Fetching the latest vendor info from DCL.
2024-06-27 01:42:54.826 (MainThread) INFO [matter_server.server.vendor_info] Fetched 210 vendors from DCL.
2024-06-27 01:42:54.826 (MainThread) INFO [matter_server.server.vendor_info] Saving vendor info to storage.
2024-06-27 01:42:55.284 (MainThread) INFO [matter_server.server.device_controller.mdns] Node 2 discovered on MDNS
2024-06-27 01:42:55.284 (MainThread) INFO [matter_server.server.device_controller.mdns] Node 1 discovered on MDNS
2024-06-27 01:42:55.284 (MainThread) INFO [matter_server.server.device_controller.node_2] Setting-up node...
2024-06-27 01:42:55.285 (MainThread) INFO [matter_server.server.device_controller.node_1] Setting-up node...
2024-06-27 01:42:55.486 (Dummy-2) CHIP_ERROR [chip.native.-] src/inet/UDPEndPointImplSockets.cpp:416: OS Error 0x02000065: Network is unreachable at src/app/OperationalSessionSetup.cpp:246
2024-06-27 01:42:55.487 (Dummy-2) CHIP_ERROR [chip.native.-] src/inet/UDPEndPointImplSockets.cpp:416: OS Error 0x02000065: Network is unreachable at src/app/OperationalSessionSetup.cpp:246
2024-06-27 01:42:55.489 (Dummy-2) CHIP_ERROR [chip.native.-] src/inet/UDPEndPointImplSockets.cpp:416: OS Error 0x02000065: Network is unreachable at src/app/OperationalSessionSetup.cpp:246
2024-06-27 01:42:55.490 (Dummy-2) CHIP_ERROR [chip.native.-] src/inet/UDPEndPointImplSockets.cpp:416: OS Error 0x02000065: Network is unreachable at src/app/OperationalSessionSetup.cpp:246
2024-06-27 01:42:55.492 (Dummy-2) CHIP_ERROR [chip.native.-] src/inet/UDPEndPointImplSockets.cpp:416: OS Error 0x02000065: Network is unreachable at src/app/OperationalSessionSetup.cpp:246
2024-06-27 01:42:58.493 (MainThread) INFO [matter_server.server.sdk.node_2] Attempting to establish CASE session... (attempt 2 of 2)
2024-06-27 01:42:58.494 (MainThread) INFO [matter_server.server.sdk.node_1] Attempting to establish CASE session... (attempt 2 of 2)
2024-06-27 01:42:58.764 (Dummy-2) CHIP_ERROR [chip.native.-] src/inet/UDPEndPointImplSockets.cpp:416: OS Error 0x02000065: Network is unreachable at src/app/OperationalSessionSetup.cpp:246
2024-06-27 01:42:58.766 (Dummy-2) CHIP_ERROR [chip.native.-] src/inet/UDPEndPointImplSockets.cpp:416: OS Error 0x02000065: Network is unreachable at src/app/OperationalSessionSetup.cpp:246
2024-06-27 01:42:58.766 (MainThread) WARNING [matter_server.server.device_controller.node_2] Setup for node failed: Unable to establish CASE session with Node 2
2024-06-27 01:42:58.766 (MainThread) WARNING [matter_server.server.device_controller.node_1] Setup for node failed: Unable to establish CASE session with Node 1

Additional information

No response

Copy link

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.

@github-actions github-actions bot added the stale label Jul 27, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 3, 2024
@ManiacMouse
Copy link
Author

ManiacMouse commented Aug 15, 2024

I gave up on getting my matter devices working again. Unresolved.

@idominiki
Copy link

Same problem suddenly appears by me.

@ManiacMouse
Copy link
Author

Yeah, I never got any help or response at all, unfortunately. No resolution found as of yet, but I've not tried either. For now, I replaced the two matter devices I had, but matter is supposed to be the future so sooner or later I probably need it working again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants