I enabled IPv6 support in my Synology after I installed SHS.
Now i see that IPv6 seems to be disabled in my host settings, could this be the reason for my problem with adding Thread devices?
IPv6 is 100% needed for Matter to work (especially with Thread, I’m not 100% sure if Matter over Wifi can be used with IPv4, buut I think thats not the case).
Your issue might be solved when you enable IPv6 on your synology host
Thanks.
I enabled IPV6 on Synology nettwork setting.
However, the IPv6 is still disabled under the host settings.
I guess this reflect the current nettwork settings when the SHS was installed.
And then I have to remove the project and reinstall SHS and bring the backup of data?
You might be able to restart the container, but I’m unfamiliar with Synology, sorry. Might also be just a visual thing in the UI, as the container should use host networking mode and the host has IPv6 enabled. BUT it could be that the docker network is created without IPv6 and you need to stop the container (and quite likely remove it) and then prune the networks to remove the non-IPv6 Network and have it recreate by re-adding the project after that
Thanks.
I guess it could be just a UI status problem.
Most likely it is missing support in SHS and that Athom must resolve this.
Is there anyone here that have managed to run Matter over Thread on their Synology NAS?
Synology IPv6 display is confusing on containers. Hosts should have the same IPv6 settings than the NAS itself. I have the same disabled display but It works. I had the issue that did not found the route to the devices, so I had to add it manually.
I did, it works perfectly now. See my previous post it might help you as well.
Many thanks.
I have been strugling around for a few hours, with help from ChatGPT 
No luck so far.
In your script you use eth0, but chatGPT suggests that ovs_eth0 is correct for Docker in host mode. However, eth0 worked for you on Synology?
Thanks.
Edit:
Also tested with VMware workstation on Windows.
The same result, not possible to add Thread devices.
Using Apple TV as TBR.
No problem adding devices when testing on HP23 and sharing devices from Apple Home.
Looks like an Athom issue.
UPDATE: I solved MY issue.
As suspected, it was an Issue with my setup. And as suspected in my last post: Its about the number of veth and br- interfaces on the host.
Seems like either Homey-SHS or the used matter library can’t handle too many IP Interfaces (According to this issue it has something todo with the UDP Socket Watch Pool beeing to smalll
This error leads to the matter daemon from homey-shs not initializing correctly on start, which leads to the 0x00ac error (the Matter fallback error in wrapMatterError()
How did I “fix” this FOR MY SETUP:
Most ip links I had are from running docker compose stacks (each producing a veth and a br IP Link. For testing purposes (and not at all the final fix, I guess the final fix must be merged by the matter dependency / homey-shs to ignore veth devices in the ip link lookup) I simply stopped ALL running compose stacks (besides my monitoring and my docker management stacks), then pruned my docker host (which in turn removes all orphaned networks), which then removes all unused veth IP links. This reduced the number from over 50 down to 18, which seems to be working. Then start homey-shs again AS THE FIRST STACK. Then start all other compose stacks.
When homey-shs is started, the number of ip links does NOT matter (Wordplay on purpose, ba dum tss) anymore and the pairing works (Tested with matter over wifi devices. For Thread I need a TBR, will check this at some other point in time).
More premanent fixes:
- Move homes-shs to its own host
- Reduce the number of docker networks by managing them yourself
Thanks all for the topic. I hope that this might also help others with their respective matter setups. If you have a lot of compose stacks running, try to shut them down and start homey as the first stack
2 Likes
good find. iuse the out of the box vm with configured docker. i wonder how many (unused) compose stacks are implemented. api,node etc) so hopefully in a next release fix they fix the udp pool then
Athom isn’t really responsible for the Compose stacks you have running. They only provide a container you can run in whatever environment you want.
You can check the running compose stacks (often also called projects) on a docker host by running
docker compose ls (might be docker-compose ls, depending on your docker host)
You can also cleanup orphaned networks (as well as all other resources) by running docker system prune, which will, when deleting the orphaned networks also clean the created veth and br network interfaces.
For all of this to work in the synology docker host VM, you ofcourse have to first ssh into that VM / open the terminal within the VM.
well, they sell a complete vmware vm with shs in there, that is what i purchased. so technically its a complete solution, with the only requirement is to have a vmware host with sufficient cpu and memory available on whatever hardware. i did not configure any docker infra cause it is already there and configured by athom. its similar to ha.
Or did you purchase a license?
yes i did
Then you know you didn’t purchase a “complete solution” 
Anyway, although Homey uses Docker internally, it only runs a few containers:
$ sudo docker container ls
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
d9eace5c7f82 homey-pro-homekit "node server.mjs" 12 days ago Up 12 days homey-pro-homekit
7170bd466915 homey-pro-sandbox "/init" 12 days ago Up 12 days homey-pro-sandbox
3ca28cbd1294 homey-pro:latest "node --dns-result-o…" 12 days ago Up 12 days homey-pro
(that’s on a HP2023)
There also aren’t that many network interfaces (6 in total, including loopback). So I doubt that this is caused by some pool running over.
not complete as in without hardware. you self host it ‘on your hardware’ now according the homey product page , it comes with matter which does not work. to implement shs, you can follow the cave route: install linux and docker yourself, or as they market it for windows, you get a vm without the spec of whats inside. like a virtual appliance.
if matter or any functionality as specified on the product page is not working, it must be fixed by means of updates. when you select the windows option, it never states that the buyer must be a linux/docker goof. it said ‘We’ve already set up a Debian virtual machine, pre-configured to automatically download the latest version of Homey Self-Hosted Server on every boot.’
we have to be careful here not to push the shs into the developer corner. it works outstanding without having to tune the engine, let the athom mechanics do that.
I have said this already in a different thread, to someone that had the same expectations that you have: Homey SHS cannot be a solution that automagically works for everyone, for the simple fact that the Athom mechanics have no control or say over the system it is installed on.
If your host has set up a firewall, or some sort of random antivirus software, that blocks certain traffic that is required for some protocol to work inside SHS, it cannot detect nor fix that.
Homey SHS is really an advanced product for people that know how to a) set up a machine properly and b) have some idea on how to debug issues when they occur. You can’t expect Athom to fix a crappy machine setup.
Thanks, problem solved at last!
“Out of the box, it supports devices that connect over Wi-Fi, Ethernet, Cloud, and Matter. Matter-over-Thread also works if you already have a Thread Border Router in your home”.
Thats true, but with reservations…
One weekend dealing with “out of the box” technology 
Due to my testing with both Ikea dirigera and Apple tv as TBR, made the search for the Thread network confusing.
It also turned out that I needed to use ovs_eth0, not eth0, on my Synology.
“ip -6 addr” revaled the correct network interface for me.
Seems to work now.
there seem to be a huge misunderstanding in the words that are used, as everyone is having problems with adding matter devices using thread
matter: Matter is the language used between devices and bridges and stuff.. as you have matter over wifi, bluetooth, thread.. and technically possible to even use zigbee and zwave, although that might never happen.
thread: is the logistics, the way this language is transferred from a device to another device and or hub/bridge.. its the network stuff
Athom delivers a package that is Matter enabled (the language).. it says nowhere on the product page it does anything with thread (the network) as it is positioned alongside the Homey Bridge, not the Homey Pro
edit: oh, and just for the record, i have Homey SHS running with Matter and Thread out of the box, no settings nothing changed. Just keep things simple, or know what you’re doing. I’ve kept it simple
Why do you call it the cave route?
Just because you’re unfamiliar with it, it’s a bit sad to label things like that.
Oh, Homey runs on Cave OS as well, in case you didn’t notice.
