Stefan Agner

> /dev/root 0% free... is this normal? This is expected as HAOS uses a fixed size read-only root file system. The systemd-journald errors could be caused by an out-of-memory event....

The system health will report the Container architecture with the next release (see https://github.com/home-assistant/core/pull/147372). However, when running Home Assistant Core container, ultimately what architecture is supported natively depends on the...

@idominiki what Matter devices did you had connected (make/model, are they connected through Thread border routers? If so, what Thread border routers do you have? I guess Apple, but to...

> I have a Unifi network configure as mentioned here: https://community.home-assistant.io/t/configuration-unifi-for-matter/671315/12 What settings do you use for Multicast Enhancement and Multicase and Broadcast Control currently? Can you try with both...

> I’m seeing the same issue as soon as I restart the Matter Server. Matter Server version is 6.5.1 Devices being unavailable after restart is expected at first, but after...

> Thanks for answering. For me the problem was the system which runs HAOS: Virtualization Station on QNAP. Whatever happens over night, on a dedicated raspberry pi everything works fine....

> This is the output on QNAP shell: > `fd5c:ba51:384c:124c::/64 dev br0 proto kernel metric 256 expires 1794sec pref medium fe80::/64 dev br0 proto kernel metric 256 pref medium` How...

The Matter SDK Python bindings have quite some globals which do not allow to initialize the Matter stack twice. Our `MatterServer` class initializes and holds the Matter stack, which can...

We did consider adding WPA3 in the past, one reason we did not do it was lack of support from Raspberry Pi (see https://github.com/raspberrypi/linux/issues/4718). There are firmwares and combination of...

Are you sure this is still the case? At least since #5903 we reload the network info on every primary interface change. From your logs it seems that NetworkManager really...