Matter Server 5.1.1 Failed Setup, will retry

[iamharuhi]

The problem

After updating the Matter Server to the latest version 5.1.1 Matter is unable to setup and connect to my existing devices.

After restoring to version 5.0.4 via a backup, all my devices reconnect and work correctly again

What version of Home Assistant Core has the issue?

core-2024.2.0

What was the last working version of Home Assistant Core?

core-2024.2.0

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Matter Server

Link to integration documentation on our website

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

Diagnostics information

home-assistant_matter_2024-02-08T21-12-30.042Z.log

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

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 close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign matter` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove 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)}}

[BlackVQ35HR]

I am also experiencing this same problem. I have so far tried

• Restarting the Matter Server
• Rebooting HA
• Turning on beta functions in the Matter Server
• Changing network settings

None of the above worked.

I did however restore from backups to get my Matter devices working again

[Mausbiber]

same problem here, but i have no backup because of a new installation. Any chance to downgrade the matter server?

[RayKiss]

I have the same problem with the Matter update from 5.0.4 to 5.1.1. Restarts of the Matter server and HA were unsuccessful. A restore from 5.0.4 helped.

[Neokimx]

I have the same problem. After updating from 5.0.4 to 5.1.x all my Matter devices are offline. I also tried the usual steps like Rebooting, Waiting, Reinstalling Matter Server Addon etc. Nothing works. Only restoring a backup from 5.0.4 works and the devices are available again. I thought I'm the only one with problems but it seems like there is some bug

[bastianrickmann]

I am having the same issue on the same version of Core 2024.2

Rolling back to 5.0.4 made my devices come back.

[ayshfm1]

Possibly a multicast problem? I moved everything to home kit. Have not restored matter server yet, still using 5.1.1 whilst I look around

[1707476800.569902][126:126] CHIP:DL: Got Ethernet interface: enp0s18 [1707476800.570120][126:126] CHIP:DL: Found the primary Ethernet interface:enp0s18 [1707476800.570335][126:126] CHIP:DL: Failed to get WiFi interface [1707476800.570345][126:126] CHIP:DL: Failed to reset WiFi statistic counts 2024-02-09 11:06:40 core-matter-server PersistentStorage[126] WARNING Loading configuration from /data/chip.json... 2024-02-09 11:06:40 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on vethdc987a4 for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found 2024-02-09 11:06:40 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on vethf72a45e for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found 2024-02-09 11:06:40 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on vethd977b54 for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found 2024-02-09 11:06:40 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on veth5cdf7f5 for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found 2024-02-09 11:06:40 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on veth7d001d9 for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found 2024-02-09 11:06:40 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on vethd737d4c for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found 2024-02-09 11:06:40 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on vethc67fd92 for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found 2024-02-09 11:06:40 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on veth36e0220 for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found 2024-02-09 11:06:40 core-matter-server chip.DL[126] ERROR MDNS failed to join multicast group on veth967de07 for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:777: Inet Error 0x00000110: Address not found 2024-02-09 11:06:40 core-matter-server CertificateAuthorityManager[126] WARNING Loading certificate authorities from storage... 2024-02-09 11:06:40 core-matter-server CertificateAuthority[126] WARNING New CertificateAuthority at index 1 2024-02-09 11:06:40 core-matter-server CertificateAuthority[126] WARNING Loading fabric admins from storage... 2024-02-09 11:06:40 core-matter-server FabricAdmin[126] WARNING New FabricAdmin: FabricId: 0x0000000000000002, VendorId = 0x134B 2024-02-09 11:06:40 core-matter-server matter_server.server.stack[126] INFO CHIP Controller Stack initialized. 2024-02-09 11:06:40 core-matter-server matter_server.server.server[126] INFO Starting the Matter Server... 2024-02-09 11:06:40 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 11:06:49 core-matter-server matter_server.server.helpers.paa_certificates[126] INFO Fetched 125 PAA root certificates from DCL. 2024-02-09 11:06:49 core-matter-server matter_server.server.helpers.paa_certificates[126] INFO Fetching the latest PAA root certificates from Git. 2024-02-09 11:06:49 core-matter-server matter_server.server.helpers.paa_certificates[126] INFO Fetched 2 PAA root certificates from Git. 2024-02-09 11:06:49 core-matter-server FabricAdmin[126] WARNING Allocating new controller with CaIndex: 1, FabricId: 0x0000000000000002, NodeId: 0x000000000001B669, CatTags: [] 2024-02-09 11:06:49 core-matter-server matter_server.server.device_controller[126] INFO Loaded 1 nodes from stored configuration 2024-02-09 11:06:49 core-matter-server matter_server.server.vendor_info[126] INFO Loading vendor info from storage. 2024-02-09 11:06:49 core-matter-server matter_server.server.vendor_info[126] INFO Loaded 160 vendors from storage. 2024-02-09 11:06:49 core-matter-server matter_server.server.vendor_info[126] INFO Fetching the latest vendor info from DCL. 2024-02-09 11:06:49 core-matter-server zeroconf[126] WARNING Error with socket 55 (('::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

[ayshfm1]

Restored to 5.0.4 and it's all working again.

This error the dissappears 2024-02-09 12:00:59 core-matter-server zeroconf[127] WARNING Error with socket 60 (('::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 12:00:59 core-matter-server matter_server.server.vendor_info[127] INFO Fetched 158 vendors from DCL. 2024-02-09 12:00:59 core-matter-server matter_server.server.vendor_info[127] INFO Saving vendor info to storage.

[fuomag9]

This is related to #109926

[iamharuhi]

Update

Issue persists after I tried updating the Home Assistant Core to core-2024.2.1 and also updating Matter Server to 5.1.2

Updated Debug Log home-assistant_matter_2024-02-09T20-21-19.379Z.log

Stayed on core-2024.2.1 but again restored Matter Server from backup to 5.0.4 and my devices work again.

[BlackVQ35HR]

Can confirm that updating to 5.1.2 also did not work. I also restored from backups.

[patelht]

My apologies for a basic question. Can some one post a step by step on how to install from an older version for matter server? I have HA Green

[JCummings49]

I’m having the same issue. Log show:

2024-02-10 07:46:08 core-matter-server chip.DIS[126] ERROR Failed to parse mDNS query 2024-02-10 07:46:08 core-matter-server chip.DIS[126] ERROR Failed to parse mDNS query 2024-02-10 07:47:38 core-matter-server chip.DIS[126] ERROR Failed to parse mDNS query 2024-02-10 07:47:38 core-matter-server chip.DIS[126] ERROR Failed to parse mDNS query 2024-02-10 07:49:08 core-matter-server chip.DIS[126] ERROR Failed to parse mDNS query 2024-02-10 07:49:08 core-matter-server chip.DIS[126] ERROR Failed to parse mDNS query 2024-02-10 07:50:38 core-matter-server chip.DIS[126] ERROR Failed to parse mDNS query 2024-02-10 07:50:38 core-matter-server chip.DIS[126] ERROR Failed to parse mDNS query 2024-02-10 07:52:08 core-matter-server chip.DIS[126] ERROR Failed to parse mDNS query 2024-02-10 07:52:08 core-matter-server chip.DIS[126] ERROR Failed to parse mDNS query 2024-02-10 08:22:08 core-matter-server chip.DIS[126] ERROR Failed to parse mDNS query 2024-02-10 08:22:08 core-matter-server chip.DIS[126] ERROR Failed to parse mDNS query 2024-02-10 08:52:08 core-matter-server chip.DIS[126] ERROR Failed to parse mDNS query 2024-02-10 08:52:08 core-matter-server chip.DIS[126] ERROR Failed to parse mDNS query 2024-02-10 09:17:32 core-matter-server chip.DMG[126] ERROR Subscription Liveness timeout with SubscriptionID = 0xde41755d, Peer = 01:0000000000000001 2024-02-10 09:17:32 core-matter-server matter_server.server.device_controller.[node 1][126] INFO Previous subscription failed with Error: 50, re-subscribing in 0 ms... 2024-02-10 09:17:32 core-matter-server chip.-[126] ERROR src/inet/UDPEndPointImplSockets.cpp:417: OS Error 0x02000065: Network is unreachable at src/app/OperationalSessionSetup.cpp:226 2024-02-10 09:17:32 core-matter-server chip.DMG[126] ERROR Failed to establish CASE for re-subscription with error 'src/inet/UDPEndPointImplSockets.cpp:417: OS Error 0x02000065: Network is unreachable' 2024-02-10 09:17:32 core-matter-server matter_server.server.device_controller.[node 1][126] INFO Previous subscription failed with Error: 33554533, re-subscribing in 5858 ms... 2024-02-10 09:17:32 core-matter-server matter_server.server.device_controller[126] INFO Marked node 1 as offline 2024-02-10 09:17:32 core-matter-server matter_server.server.device_controller[126] INFO Node 1 discovered on MDNS 2024-02-10 09:17:32 core-matter-server matter_server.server.device_controller.[node 1][126] INFO Setting up attributes and events subscription. 2024-02-10 09:17:33 core-matter-server chip.-[126] ERROR src/inet/UDPEndPointImplSockets.cpp:417: OS Error 0x02000065: Network is unreachable at src/app/OperationalSessionSetup.cpp:226 2024-02-10 09:17:36 core-matter-server matter_server.server.device_controller[126] INFO Attempting to resolve node 1... (attempt 2 of 2) 2024-02-10 09:17:36 core-matter-server chip.-[126] ERROR src/inet/UDPEndPointImplSockets.cpp:417: OS Error 0x02000065: Network is unreachable at src/app/OperationalSessionSetup.cpp:226 2024-02-10 09:17:36 core-matter-server matter_server.server.device_controller[126] WARNING Unable to subscribe to Node 1 as it is unavailable 2024-02-10 09:22:08 core-matter-server chip.DIS[126] ERROR Failed to parse mDNS query 2024-02-10 09:22:08 core-matter-server chip.DIS[126] ERROR Failed to parse mDNS query 2024-02-10 09:22:08 core-matter-server matter_server.server.device_controller[126] INFO Node 1 discovered on MDNS 2024-02-10 09:22:08 core-matter-server matter_server.server.device_controller.[node 1][126] INFO Setting up attributes and events subscription. 2024-02-10 09:22:08 core-matter-server chip.-[126] ERROR src/inet/UDPEndPointImplSockets.cpp:417: OS Error 0x02000065: Network is unreachable at src/app/OperationalSessionSetup.cpp:226 2024-02-10 09:22:11 core-matter-server matter_server.server.device_controller[126] INFO Attempting to resolve node 1... (attempt 2 of 2) 2024-02-10 09:22:11 core-matter-server chip.-[126] ERROR src/inet/UDPEndPointImplSockets.cpp:417: OS Error 0x02000065: Network is unreachable at src/app/OperationalSessionSetup.cpp:226 2024-02-10 09:22:11 core-matter-server matter_server.server.device_controller[126] WARNING Unable to subscribe to Node 1 as it is unavailable 2024-02-10 09:22:11 core-matter-server matter_server.server.device_controller[126] INFO Node 1 discovered on MDNS 2024-02-10 09:22:11 core-matter-server matter_server.server.device_controller.[node 1][126] INFO Setting up attributes and events subscription. 2024-02-10 09:22:12 core-matter-server chip.-[126] ERROR src/inet/UDPEndPointImplSockets.cpp:417: OS Error 0x02000065: Network is unreachable at src/app/OperationalSessionSetup.cpp:226 2024-02-10 09:22:15 core-matter-server matter_server.server.device_controller[126] INFO Attempting to resolve node 1... (attempt 2 of 2) 2024-02-10 09:22:15 core-matter-server chip.-[126] ERROR src/inet/UDPEndPointImplSockets.cpp:417: OS Error 0x02000065: Network is unreachable at src/app/OperationalSessionSetup.cpp:226 2024-02-10 09:22:15 core-matter-server matter_server.server.device_controller[126] WARNING Unable to subscribe to Node 1 as it is unavailable 2024-02-10 09:33:07 core-matter-server matter_server.server.device_controller[126] INFO Node 1 discovered on MDNS 2024-02-10 09:33:07 core-matter-server matter_server.server.device_controller.[node 1][126] INFO Setting up attributes and events subscription. 2024-02-10 09:33:07 core-matter-server chip.-[126] ERROR src/inet/UDPEndPointImplSockets.cpp:417: OS Error 0x02000065: Network is unreachable at src/app/OperationalSessionSetup.cpp:226 2024-02-10 09:33:10 core-matter-server matter_server.server.device_controller[126] INFO Attempting to resolve node 1... (attempt 2 of 2) 2024-02-10 09:33:11 core-matter-server chip.-[126] ERROR src/inet/UDPEndPointImplSockets.cpp:417: OS Error 0x02000065: Network is unreachable at src/app/OperationalSessionSetup.cpp:226 2024-02-10 09:33:11 core-matter-server matter_server.server.device_controller[126] WARNING Unable to subscribe to Node 1 as it is unavailable 2024-02-10 09:33:11 core-matter-server matter_server.server.device_controller[126] INFO Node 1 discovered on MDNS 2024-02-10 09:33:11 core-matter-server matter_server.server.device_controller.[node 1][126] INFO Setting up attributes and events subscription. 2024-02-10 09:33:11 core-matter-server chip.-[126] ERROR src/inet/UDPEndPointImplSockets.cpp:417: OS Error 0x02000065: Network is unreachable at src/app/OperationalSessionSetup.cpp:226 2024-02-10 09:33:14 core-matter-server matter_server.server.device_controller[126] INFO Attempting to resolve node 1... (attempt 2 of 2) 2024-02-10 09:33:14 core-matter-server chip.-[126] ERROR src/inet/UDPEndPointImplSockets.cpp:417: OS Error 0x02000065: Network is unreachable at src/app/OperationalSessionSetup.cpp:226 2024-02-10 09:33:14 core-matter-server matter_server.server.device_controller[126] WARNING Unable to subscribe to Node 1 as it is unavailable 2024-02-10 09:33:14 core-matter-server matter_server.server.device_controller[126] INFO Node 1 discovered on MDNS 2024-02-10 09:33:14 core-matter-server matter_server.server.device_controller.[node 1][126] INFO Setting up attributes and events subscription. 2024-02-10 09:33:14 core-matter-server chip.-[126] ERROR src/inet/UDPEndPointImplSockets.cpp:417: OS Error 0x02000065: Network is unreachable at src/app/OperationalSessionSetup.cpp:226 2024-02-10 09:33:17 core-matter-server matter_server.server.device_controller[126] INFO Attempting to resolve node 1... (attempt 2 of 2) 2024-02-10 09:33:17 core-matter-server chip.-[126] ERROR src/inet/UDPEndPointImplSockets.cpp:417: OS Error 0x02000065: Network is unreachable at src/app/OperationalSessionSetup.cpp:226 2024-02-10 09:33:17 core-matter-server matter_server.server.device_controller[126] WARNING Unable to subscribe to Node 1 as it is unavailable

[bastianrickmann]

Also for me the update didn't resolve the issue

[simps100]

Suffering the same issue since last update - 5.1.2 don’t seem to solve the issue.

[upthinkweb]

Same issue! 5.1.2 not working

[marcelveldt]

You will need to remove the Matter integration from HA and re-add it. Unfortunately there is no other solution.

If you still experience issues after re-adding the integration, please open a new issue with an exact description of the issue you're experiencing.

[bastianrickmann]

@marcelveldt so what exactly is the bug that causes a different behavior. Upgrading vs re-adding. This shouldn't be solution. Publishing new version also means properly migrating data/configs. If it cause different behavior then there is something odd that should be looked into.

There must be a change that cause a conflict. So the right way would be to write a correct migration. I am not really interested in re-adding most of my devices also the change log doesn't really provide informations about the changes. Also "bump to version" could be extended by its change log at least if it's only that one dependency .

This isn't meant to be rant or anything but a request of improvement for new versions and releases.

[marcelveldt]

Well, problem is that the config in your case is a bit messed up. It can be solved by manually editing the config entries file under the hood but that is not really something I'd like to propose. You wont loose your devices. Just remove the integration and re-add it, it will connect to the existing server and you keep your devices.

While we're still in BETA (and we clearly state everywhere this is not ready for production!) we think stuff like this can happen. We try to prevent it but with so many changes still happening, its unavoidable sometimes.

[bastianrickmann]

@marcelveldt I see. I am aware of the BETA state, but for me this just seemed to be an issue that could be resolved in some way. For me a BETA state means it can happen to have bugs and issues. I am a developer myself and have those issues too. And I am totally fine that I had to rollback to 5.0.4 twice.

But since 5.0.4 is running totally fine and in combination with the latest Core version I didn't had the stress to upgrade even tho I would love too. BETA means for me you got the time to fix stuff and that we as a community can contribute to resolve issues together. Still I assume there might be missing migration process in general to prevent this kind of problems in the future? Missing Tests? (End-to-End-Test | Migrating from previous version to next one ?)

After all we are all doing this work together also for those who aren't on GitHub or less tech related.

[bastianrickmann]

@marcelveldt since you state about the "not production environment" I would be interested in your personal setup and how to test out features like this in a more personal private real life environment? In my opinion at home and private almost everything is a production environment.

[marcelveldt]

Only a very small amount of people is affected by this. We closed down the websocket port to the matter server on HAOS installs. By default we use the internal url to talk to the matter server but some people have used the advanced options to configure the url manually and those are affected by this. As I said, a very limited amount of people. Solution is to remove the integration for Matter and re-add it right away. That way nothing gets lost.

We dont have any way to migrate the server url or change it afterwards. Something that is coming at some point but just not yet. We are very limited on resources and also user contributions on matter are very sparse so its a bit of challenge sometimes, sorry.

Please let me know if you still run into issues after re-adding the Matter integration, thanks!

[iamharuhi]

I tried completely removing the Matter integration and re-adding it, but it's still having the same issue. Also updated to core-2024.2.2

home-assistant_matter_2024-02-15T13-23-12.393Z.log

[Gillingham]

I'm still having the same issue as well, when I uninstall the addon it reinstalls itself, but still devices are offline.

Feb 17 20:02:29 homeassistant hassio_supervisor[476]: 24-02-17 12:02:29 INFO (MainThread) [supervisor.discovery] Delete discovery to Home Assistant matter from core_matter_server
Feb 17 20:02:29 homeassistant hassio_supervisor[476]: 24-02-17 12:02:29 INFO (MainThread) [supervisor.addons.manager] Add-on 'core_matter_server' successfully removed
Feb 17 20:02:29 homeassistant hassio_supervisor[476]: 24-02-17 12:02:29 INFO (MainThread) [supervisor.discovery] Discovery eb33335b7a46408991f7c9c308ff02a8 message send
Feb 17 20:02:30 homeassistant homeassistant[476]: 2024-02-17 12:02:30.588 INFO (MainThread) [homeassistant.components.matter] Matter Server add-on is not installed. Installing add-on
Feb 17 20:02:30 homeassistant hassio_supervisor[476]: 24-02-17 12:02:30 INFO (MainThread) [supervisor.addons.addon] Creating Home Assistant add-on data folder /data/addons/data/core_matter_server
Feb 17 20:02:30 homeassistant hassio_supervisor[476]: 24-02-17 12:02:30 INFO (MainThread) [supervisor.docker.interface] Downloading docker image homeassistant/amd64-addon-matter-server with tag 5.1.2.
Feb 17 20:02:38 homeassistant systemd[1]: var-lib-docker-overlay2-191745e6e9de01750156a79797df11762eb8d426c62f472f4336e15867ae21e3-merged.mount: Deactivated successfully.
Feb 17 20:02:38 homeassistant systemd[1]: mnt-data-docker-overlay2-191745e6e9de01750156a79797df11762eb8d426c62f472f4336e15867ae21e3-merged.mount: Deactivated successfully.
Feb 17 20:02:38 homeassistant hassio_supervisor[476]: 24-02-17 12:02:38 INFO (MainThread) [supervisor.addons.manager] Add-on 'core_matter_server' successfully installed
Feb 17 20:02:38 homeassistant homeassistant[476]: 2024-02-17 12:02:38.467 ERROR (MainThread) [homeassistant.components.matter] Failed to set the Matter Server add-on options: not a valid value for dictionary value @ data['options']. Got {}
Feb 17 20:02:40 homeassistant homeassistant[476]: 2024-02-17 12:02:40.668 INFO (MainThread) [homeassistant.components.matter] Matter Server add-on is not running. Starting add-on

[countrock]

On HA 2024.2.2 and still have the same issue. Removed the integration and the addon and still have the same issue after reinstall. Not sure what to do next.

[bluefunoodle311]

I removed the integration as suggested above and can't get it to reinstall. If I uninstall the Matter Server add-on, will I lose my devices and have to re-add them?

Core 2024.2.2 Matter 5.1.2

[marcelveldt]

I removed the integration as suggested above and can't get it to reinstall. If I uninstall the Matter Server add-on, will I lose my devices and have to re-add them?

Core 2024.2.2 Matter 5.1.2

If you reinstall the Matter integration nothing gets lost. If you uninstall the Matter add-on then you loose your data and you need to repair your devices. So you removed the integration and then re-installed it ? select the default option to use the add-on (it should pick up the existing addon). Can you tell me step by step what you did and where you get stuck now ?

[marcelveldt]

I'm still having the same issue as well, when I uninstall the addon it reinstalls itself, but still devices are offline.

The add-on is managed by the integration. Uninstalling will make you loose your data so don't. You just remove Matter from HA --> Integrations and services. If you then quickly re-add it, it will use the existing running add-on.

[bluefunoodle311]

I removed the integration as suggested above and can't get it to reinstall. If I uninstall the Matter Server add-on, will I lose my devices and have to re-add them? Core 2024.2.2 Matter 5.1.2

If you reinstall the Matter integration nothing gets lost. If you uninstall the Matter add-on then you loose your data and you need to repair your devices. So you removed the integration and then re-installed it ? select the default option to use the add-on (it should pick up the existing addon). Can you tell me step by step what you did and where you get stuck now ?

I removed the integration and finally got it to re-add, but all my devices were lost. I had to remove the HA Matter ID from either Google Home or Alexa to get them re-added through the HA mobile app. However, it resulted in the same symptoms of devices going unavailable after a short period of time. It seems that a full reboot restores them for a while then they drop off. They're all operating fine and showing status on both Alexa and Google Home apps.

I have since updated to Matter Server 5.2.0, HAOS 12, and Core 2024.2.3 and still experiencing the same problem.

I should add: In my case, all my Matter devices are operating on Thread.

[marcelveldt]

have since updated to Matter Server 5.2.0, HAOS 12, and Core 2024.2.3 and still experiencing the same problem.

Please create a new issue report for that behavior and make sure to include full logs of the server.

[marcelveldt]

@iamharuhi sorry for the late reply, your report got completely hijacked by others making it impossible for me to follow anymore. I will focus on your report. So, can you tell me if the Matter add-on is installed currently ? And if so, is is running ? What version?

Hoem Assistant --> settings --> Add-ons -> Matter Server

[akzov]

The only option I have is Disable or Delete so I used delete. Does this mean I have to wipe everything and setup from scratch?

[marcelveldt]

The only option I have is Disable or Delete so I used delete. Does this mean I have to wipe everything and setup from scratch?

If you deleted the integration and you add it right back, the data is still present in the matter server (make sure to select the option to use the official addon!)

[Mutley247365]

Morning all, I to have just update the matter server today to 5.6.0 (2/5/24) along with core 2024.4.4 to find that the matter server "failed to start up" I have attempted to reload the configuration and also restart the add on, to no avail. has anyone else encountered this of late? if so, have you been successful in re launching this serer?

[marcelveldt]

Morning all, I to have just update the matter server today to 5.6.0 (2/5/24) along with core 2024.4.4 to find that the matter server "failed to start up" I have attempted to reload the configuration and also restart the add on, to no avail. has anyone else encountered this of late? if so, have you been successful in re launching this serer?

https://github.com/home-assistant/core/issues/116566