Can't stop Matter Server

[WallyDW]

Describe the issue you are experiencing

I have the issue with updating Eve Energy Matter devices to 3.2.1 and wanted to to try to stop the Matter Server addon for some time to see if that helped, but it just restarts right away instead.

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.4.1

Steps to reproduce the issue

1. Start the Matter server (I have an OTBR with SkyConnect as only BR and currently only 2 Eve Energy Matter devices and some Onvis plugs. No idea if this has an effect though)
2. Stop the server
3. Sometimes it looks like the server is stopped on the Info page, but refreshing the page will then show it as running and the logs will confirm it too.
4. Watchdog and start-on-boot does not seem to affect it.

System Health information

System Information

version	core-2024.8.2
installation_type	Home Assistant OS
dev	false
hassio	true
docker	true
user	root
virtualenv	false
python_version	3.12.4
os_name	Linux
os_version	6.6.46-haos
arch	x86_64
timezone	Europe/Copenhagen
config_dir	/config

Home Assistant Community Store

GitHub API	ok
GitHub Content	ok
GitHub Web	ok
HACS Data	ok
GitHub API Calls Remaining	5000
Installed Version	2.0.0
Stage	running
Available Repositories	1401
Downloaded Repositories	41

Home Assistant Supervisor

host_os	Home Assistant OS 13.1
update_channel	stable
supervisor_version	supervisor-2024.08.0
agent_version	1.6.0
docker_version	26.1.4
disk_total	97.7 GB
disk_used	71.8 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	Node-RED (18.0.5), Log Viewer (0.17.0), Mosquitto broker (6.4.1), Samba share (12.3.2), Grafana (10.0.0), Glances (0.21.1), Studio Code Server (5.15.0), Samba Backup (5.2.0), MariaDB (2.7.1), Advanced SSH & Web Terminal (18.0.0), ESPHome (2024.8.0), InfluxDB (5.0.0), Let's Encrypt (5.1.1), OpenThread Border Router (2.9.1), Matter Server (6.4.1)

Dashboards

dashboards	3
resources	26
views	21
mode	yaml

Recorder

oldest_recorder_run	26 July 2024 at 06:29
current_recorder_run	22 August 2024 at 21:43
estimated_db_size	145.43 MiB
database_engine	sqlite
database_version	3.45.3

Anything in the Supervisor logs that might be useful for us?

This might be caused by me trying to stop the addon several times and sometimes quickly after each other.

2024-08-24 09:59:13.552 INFO (SyncWorker_2) [supervisor.docker.manager] Stopping addon_core_matter_server application
2024-08-24 09:59:15.142 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.32.1:5580 ssl:default [Connect call failed ('172.30.32.1', 5580)]
2024-08-24 09:59:17.936 INFO (SyncWorker_2) [supervisor.docker.manager] Cleaning addon_core_matter_server application
2024-08-24 09:59:18.079 INFO (MainThread) [supervisor.docker.addon] Starting Docker add-on homeassistant/amd64-addon-matter-server with version 6.4.1
2024-08-24 09:59:18.605 INFO (MainThread) [supervisor.api.middleware.security] /network/info access from core_matter_server
2024-08-24 09:59:20.298 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.32.1:5580 ssl:default [Connect call failed ('172.30.32.1', 5580)]

and

2024-08-24 10:30:13.509 INFO (SyncWorker_5) [supervisor.docker.manager] Stopping addon_core_matter_server application
2024-08-24 10:30:17.834 INFO (SyncWorker_5) [supervisor.docker.manager] Cleaning addon_core_matter_server application
2024-08-24 10:30:17.845 ERROR (SyncWorker_4) [supervisor.docker.manager] Can't read stats from addon_core_matter_server: Expecting value: line 1 column 1 (char 0)
2024-08-24 10:30:17.974 INFO (MainThread) [supervisor.docker.addon] Starting Docker add-on homeassistant/amd64-addon-matter-server with version 6.4.1
2024-08-24 10:30:18.480 INFO (MainThread) [supervisor.api.middleware.security] /network/info access from core_matter_server
2024-08-24 10:30:30.418 INFO (SyncWorker_0) [supervisor.docker.manager] Stopping addon_core_matter_server application
2024-08-24 10:30:34.677 INFO (SyncWorker_0) [supervisor.docker.manager] Cleaning addon_core_matter_server application
2024-08-24 10:30:34.810 INFO (MainThread) [supervisor.docker.addon] Starting Docker add-on homeassistant/amd64-addon-matter-server with version 6.4.1
2024-08-24 10:30:35.323 INFO (MainThread) [supervisor.api.middleware.security] /network/info access from core_matter_server

Anything in the add-on logs that might be useful for us?

This is the Matter Server addon logs set to Verbose output.

2024-08-24 10:45:50.132 (MainThread) INFO [aiorun] Leaving. Bye!
[08:45:50] INFO: matter-server service exited with code 0 (by signal 0).
s6-rc: info: service matter-server successfully stopped
s6-rc: info: service banner: stopping
s6-rc: info: service banner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
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: 6.4.1
 You are running the latest version of this add-on.
 System: Home Assistant OS 13.1  (amd64 / qemux86-64)
 Home Assistant Core: 2024.8.2
 Home Assistant Supervisor: 2024.08.0
-----------------------------------------------------------
 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
[10:45:55] INFO: Starting Matter Server...
s6-rc: info: service legacy-services successfully started
[10:45:56] INFO: Using 'enp0s18' as primary network interface.
[10:45:56] INFO: Successfully send discovery information to Home Assistant.

Additional information

No response

[blue-hound]

I stumbled on this while looking for something else and checked to see what my system would do. Attempting to stop the server with watchdog off just results in a restart.

[github-actions[bot]]

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.

[WallyDW]

Now at version 6.5.1 and still same issue

[github-actions[bot]]

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.

[brnhffmnn]

Seeing the same. Even stopping via SSH using docker stop the container comes back after some time. I disabled watchdog and start on boot.

... even deinstalling the addon brings it back. Might this behavior related to the companion matter integration?

[kengr0]

I had the same issue. I removed Matter Integration and HA Supervisor stopped reinstalling Matter server. I suspect ultimately it was Matter Integration which was managing Matter Add-On as during installation Matter Integration has "Use the official Matter Server Supervisor add-on" checkbox, so uninstalling Matter Add-On from Add-On section would create "split brain" and Matter Integration would reinstall Add-On. Yes, that is confusing and it would be good in Matter Add-On have a label/setting is it was installed/managed by Matter Integration.

[WallyDW]

Matter server should be able to be stopped, even if you have the Matter integration installed and set to use it. The Matter integration should just make it happen and then maybe throw an error in the log and maybe set a repair issue. There can be times where you need the Matter server to be down.

[Ultra-Meloncrafter]

same issue, just want to stop the matter server, since i don't use it and want to save the RAM, but when i stop it instantly restart it and when i try to delete it, it reinstalls itself right after

[phenixar]

To stop matter server, you need to remove the matter device before.