Ya just looked at my IPv4/IPv6 settings | Home Assistant | Page 1

Can you ping your thread devices from a terminal in your HA container? Using the SSH app or similar. It should work like this:

PING fda7:948d:4455:1:4a90:882d:fa96:a7bd (fda7:948d:4455:1:4a90:882d:fa96:a7bd): 56 data bytes
64 bytes from fda7:948d:4455:1:4a90:882d:fa96:a7bd: seq=0 ttl=64 time=30.298 ms
64 bytes from fda7:948d:4455:1:4a90:882d:fa96:a7bd: seq=1 ttl=64 time=31.697 ms
64 bytes from fda7:948d:4455:1:4a90:882d:fa96:a7bd: seq=2 ttl=64 time=29.137 ms```

That's just the IP addresse of one of my matter over thread devices.

Note that I have a matching entry in my ipv6 routing table:

```➜  ~ ip -f inet6 route
2605:59c8:5257:100::/64 dev enp0s18  metric 100 
fd20:8b39:3aa1:1::/64 via fe80::a492:15b3:574f:8c3 dev enp0s18  metric 100 
fd9f:8c5e:3a97:5237::/64 dev wpan0  metric 64 
fda7:948d:4455:1::/64 dev wpan0  metric 64 
fdb5:ea33:16ce:da2::/64 dev enp0s18  metric 100 
fe80::/64 dev vethc23f629  metric 256 
fe80::/64 dev hassio  metric 256 
fe80::/64 dev docker0  metric 256 
fe80::/64 dev vethec51901  metric 256 
fe80::/64 dev veth36ecf40  metric 256 
fe80::/64 dev vethb12d79a  metric 256 
fe80::/64 dev vetheec6aa3  metric 256 
fe80::/64 dev veth1bbc8c7  metric 256 
fe80::/64 dev vethbf121fb  metric 256 
fe80::/64 dev vethd05a822  metric 256 
fe80::/64 dev veth6aa13a7  metric 256 
fe80::/64 dev veth94f2fce  metric 256 
fe80::/64 dev vethe44c364  metric 256 
fe80::/64 dev veth939f0e1  metric 256 
fe80::/64 dev veth599506f  metric 256 
fe80::/64 dev veth97a5b86  metric 256 
fe80::/64 dev vethcdc08fe  metric 256 
fe80::/64 dev wpan0  metric 256 
fe80::/64 dev veth3ec388a  metric 256 
fe80::/64 dev vethca80e7f  metric 256 
fe80::/64 dev vethaaa1417  metric 256 
fe80::/64 dev veth4a02deb  metric 256 
fe80::/64 dev enp0s18  metric 1024 
default via fe80::9c05:d6ff:fe53:c829 dev enp0s18  metric 100```

If you can't reach the device, then something is wrong with your thread border router or other network config, and the problem isn't with the new matter.js-server, so you will have to look for help in a different channel

#Ya just looked at my IPv4/IPv6 settings