You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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)
Stop the server
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.
Watchdog and start-on-boot does not seem to affect it.
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
The text was updated successfully, but these errors were encountered:
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.
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.
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
System Health information
System Information
Home Assistant Community Store
Home Assistant Supervisor
Dashboards
Recorder
Anything in the Supervisor logs that might be useful for us?
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: