#Matter server restarting almost every hour, sometimes more

1 messages · Page 1 of 1 (latest)

slender hearth
#

I'm new to matter but have been using HA for many years, I recently added two new matter over Wi-Fi bulbs to one of my HA deployments and noticed they go offline frequently after spending an age troubleshooting my LAN/Wi-Fi I then noticed the matter add-on logs show the matter server exiting with msg "matter-server service exited with code 134 (by signal 6)." It then restarts, sometime the bulbs come online again or I have to restart the WiFi AP they're connected to. I have no idea what the exit code is for or what I should troubleshoot next. I'm running HA as HAOS with a bridge network interface from a Windows 11 host under Oracle VirtualBox, I don't have any other issues with this HA deployment. Any advice/pointers would be great.

Add-on version: 7.0.0
System: Home Assistant OS 14.1 (amd64 / qemux86-64)
Home Assistant Core: 2025.1.2
Home Assistant Supervisor: 2024.12.3

log sample - I've had 16 restarts in the ~5 hours alone

[16:03:54] WARNING: matter-server service exited with code 134 (by signal 6).
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service matter-server: stopping
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 legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs 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

wraith holly
#

I think you should start by running HA on a dedicated hardware box or a linux based VM host.

#

I'm afraid that Windows + VirtualBox is a NO-GO for running Matter which depends on a functional IPv6 stack.

slender hearth
#

So are you saying that even though the VirtualBox HA VM has a bridged network interface and all other IPV6 (like accessing .local to and from it) can still cause an issue with the matter/mDNS ?

wraith holly
#

Exactly

slender hearth
#

Do you know if I use Proxmox on the bare metal as my hypervisor for a HA OS VM, if that would resolve my issues?

fringe shale
#

I think that's how most of us use haos. Works well for me

wraith holly
#

Proxmox is fine indeed