core All matter devices are unavailable over night

The problem

Since latest 2024.10 update, all my matter devices are unavailable.

I don’t change my network configuration since latest update.

Reinstall of Matter Server addon doesn’t help. Adding matter devices fails with this error:

What version of Home Assistant Core has the issue?

core-2024.10.0

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

No response

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

Oct 04 '24 16:10 idominiki

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)}}

Oct 04 '24 16:10 home-assistant[bot]

Update: Also after restoring to 2024.9.3, all Matter devices are offline.

All matter devices are Matter over Thread devices (Eve).

I have a Unifi network configure as mentioned here: https://community.home-assistant.io/t/configuration-unifi-for-matter/671315/12

Nothing changed to my configuration, since 2 days over night, all devices are unavailable.

Devices in Apple Home are working well.

Oct 04 '24 18:10 idominiki

I’m seeing the same issue as soon as I restart the Matter Server. Matter Server version is 6.5.1

Oct 05 '24 12:10 adamf83

Update: Clean installed Home Assistant: Same behavior.

Also with latest beta Matter Server addon.

Oct 05 '24 12:10 idominiki

@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 get a better picture of your setup, please specify what devices you have and how they are distributed).

Oct 07 '24 13:10 agners

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 disabled?

Oct 07 '24 13:10 agners

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 setting up the subscription things should slowly become online again. Do your devices stay offline for more than say 10 minutes? If so, can you also describe your setup a bit more in detail (BR, make model, devices, type etc...)

Oct 07 '24 13:10 agners

Hi @agners 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.

I just tested again: IPv6 is disabled for network configuration on my QNAP. HAOS OVA imported to Virtualization Station. Same problem in the Matter Server Addon log:

2024-10-07 20:40:45.889 (Dummy-2) CHIP_ERROR [chip.native.-] src/inet/UDPEndPointImplSockets.cpp:416: OS Error 0x02000065: Network is unreachable at src/controller/SetUpCodePairer.cpp:280

Oct 07 '24 18:10 idominiki

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.

I just tested again: IPv6 is disabled for network configuration on my QNAP. HAOS OVA imported to Virtualization Station. Same problem in the Matter Server Addon log:

Uh, this could be a IPv6 ND issue, specifically that multicasts don't make it through the bridge or similar. Check and compare the routing tables on the OS shell (ip -6 route).

Depending on how the kernel is on QNAP you might suffer this issue still.

In any case, QNAP is not really a supported virtualization environment.

Oct 07 '24 21:10 agners

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

What makes me curious, why it doesn't work from one day to the next.

Oct 08 '24 05:10 idominiki

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 many Thread BR do you have? It seems only one from this output.

By QNAP shell you mean the QNAP Linux system, or the HAOS virtual system through QNAP?

Comparing the output with the output on the dedicated Raspberry Pi. Also try to connect them as similar as possible (through same switch etc).

What makes me curious, why it doesn't work from one day to the next.

Hard to tell. Maybe another machine which was running reconfigured the bridge, or something else influenced the bridges behavior, so IPv6 ND packets didn't go through anymore.

Oct 08 '24 12:10 agners

I have 4 HomePod mini's and one Apple TV 4K.

I tested a few more IP routes.

This is the output from QNAP Linux system:

This is the output from a freshly installed HAOS on QNAP NAS:

This is the output from working HAOS on RPi:

Both, QNAP NAS and RPi are connected to the same Network Switch.

Other VMs on the QNAP NAS are Pi-hole and RaspberryMatic. All connected to the same Virtual Switch on QNAP and get its own local IPv4 address.

Oct 08 '24 12:10 idominiki

I have 7 Heiman thread devices with Apple broad router, it didn't become unavailable.

my core of HA is 2024.10.0b1 and Matter Server Adds on is 6.5.1

Oct 14 '24 01:10 Leo2442926161

Closing this issue here as QNAP is not a supported environment to run Matter (not even virtualized). Better join discord or the forums to discuss this with community members.

Oct 29 '24 15:10 marcelveldt