xee

The tip with the “User Scrip” plugin is great, it worked immediately for me. Now the Matter Server is fully operational and I was able to deactivate the VM and now have everything on Docker. Many thanks to you all.

Yes, I can confirm that the two commands also solved the problem for me. Now I am only faced with the challenge of how to persist these commands so that the setting is retained after a reboot. Unfortunately my Linux knowledge is not so good.

Unfortunately no, I also tried the beta of Unraid 7 once but unfortunately this did not work either. I can't get unraid itself or Docker running on Unraid to connect to the Matter devices. I have now accepted that it only works in a VM. That's ok for now and you can live with the workaround.

I have now run tests on the HA and Matter server combinations. TL;DR: the HA has no influence on the Device <-> Matter-server connection. So the test setup is: HA-Docker (network type set custom) Matter-Server-Docker (network type set Host) HA-VM Matter-Server-VM Combinations with result: HA-Docker & Matter-Server-VM (working) HA-VM & Matter-Server-VM (working) HA-Docker & Matter-Server-Docker (NOT working) HA-VM & Matter-Server-Docker (NOT working) It only works if the Matter server is running in the VM with its own network stack. If it is running in the Docker with the Unraid network stack, the Matter server can no longer reach the devices. It is not important whether the HA itself is running in a VM or Docker, nor does the Docker network type play a role. The connection between HA and the Matter server worked without any problems in all combinations.

Yes 192.168.1.100 is the unraid system. The HA docker is set to host is just not shown in the UI for the docker, no idea why that is, but it is the same for other setups I have seen. To clarify, the problem is that the Matter server cannot communicate with the devices (lamps and sensors) in the ipv6 network behind the boarder router. HA has nothing to do with this problem. The interaction between HA and matter Server also runs without any problems. The aim is for the matter server to be able to "see" the devices.

Gladly here is my docker list:

Unfortunately, my further attempts have not yielded any results yet. I have the "unconfirmed" feeling that it might have something to do with the Router Advertisements. I am unable to ping the IPv6 addresses of the individual Thread devices behind the Border Router from Unraid (though it works from the Windows PC), but I can ping the Border Router using IPv6. I have also tried some steps from this documentation, but without success. So, the situation remains that all devices in my network can ping the Thread devices using IPv6, only Unraid cannot.

Yes exactly I have installed both Docker (HA and Matter Server) from the "App Store" of unraid. I have read the post in the support forum and see that there are several people who have a connection problem, unfortunately no solution seems to have been found here. My guess is that I have to make some settings in the Linux substructure so that the Thread Boarder routers are recognized correctly. Since the entire ipv6 network which is in the thread network is not accessible for unraid. For WinPC, iPhone and VMs however already.

Oh I think there is a misunderstanding. I am using HA (Docker) and I am currently using a VM with HAOS in it but only the Matter server. However, I want to use the Matter server in Docker to get rid of the VM. Current state: HA (docker), Matter (VM with HAOS) <- Works Target state: HA (docker), Matter (docker) <- Works Not PS: all combinations of HA and Matter can be connected to each other without any problems. The problem is that Unraid itself cannot access the ipv6 devices in the thread network (ping) and therefore the docker cannot either. However, the VM on the Unraid can access the devices, just like all other devices I have on the network, such as PC or iPhone.

Hi bmartino1, thanks for the reply i have tried the settings: Unfortunately, it had no effect on the problem. Even after setting it up and waiting a few minutes, neither the Unraid system nor the Docker could ping any of my devices, nor could I add them to the Matter server.

Goal: Using Docker: Matter Server with Home Assistant (Docker). Current State: Using Home Assistant (Docker) with Matter Server (VM with HAOS). Problem: The Matter Server cannot connect devices from an existing Thread network. Possible Cause: Unraid cannot access the IPv6 addresses of devices in the Thread network. However, VMs installed on the Unraid server can access the IPv6 addresses of the devices. Infrastructure: Unifi network with an Apple TV (Thread Border Router), 5 HomePod Minis (Thread Border Router), and the Unraid server, all in the same flat network with no additional VLANs. Free Text: Hi everyone, I am currently running Home Assistant (HA) in Docker and have installed a VM where HAOS is running just to use the Matter plugin (which is also a Docker in HAOS). I would now like to use Matter Server Docker from Unraid, but unfortunately, Unraid cannot route to the IPv6 addresses of the individual devices and therefore cannot connect them. If I ping one of these devices from my Windows PC, Mac, iPhone, or the HAOS VM running on Unraid, it works immediately, and the device responds. However, if I ping from the Unraid terminal directly, I get "Destination unreachable: No route". My question is, what do I need to configure in Unraid so that I can reach these devices? Unfortunately, IPv6 is still new to me, and I have some knowledge gaps in this area. Network Config: