…
Perhaps not add to the confusion by listing Zigbee and Z-Wave as Matter “transporters” 
1 Like
you’re right as that might be a bit of a stretch… but you only need a translator to add all zigbee and zwave devices to a Matter enviroment. There is even an Homey app for to do just that and its how the aqara hub works as well.
That’s the same as saying that Zigbee devices support MQTT, or the HomeKit protocol, or WiFi, because there are translators 
I have adjusted my text
Matter depends on IPv6, which both Zigbee and Z-Wave do not and will not ever support
1 Like
Yeah, might be, but Chatgpt said “…”
1 Like
Exactly the confusion sigh
Matter does not.. its Thread that depends on IPV6
Matter is the Application Layer, not the network 
I’m also receiving a 0x00ac error after trying to repair the dirigera hub (which I earlier linked through matter, through an Apple 4K as hub). Though since I tried to repair, it throws that error.
I’ve tried the following so far:
- Re-boot homey
- Hard-reboot the actual container
- Reboot my phone
- Reboot Apple TV
- Removed the Dirigera HUB (and therefore, all devices)
- I now of course do not have that HUB in my Homey anymore.
If anyone that has it still working, know a work-around, that would be amazing 
Can you check the Homey-SHS Container Logs? For me, I have to restart my containers in a specific order now to make sure that only a small amount Network Adapters are present when homey starts. Sounds like a similar Problem, as it only appeared after some time (maybe the container restarted inbetween, currently there is no error in the UI when the Matter daemon can’t start, something that Athom might be able to improve)
I currently have Matter (over Thread using the OTBR Addon in Home Assistant and over Wifi) running without any issue).
Now that you say this, it stopped working after a mass reboot of my home server with an automated script, I added the possibility to include some pre-required apps but homey wasn’t in that, but all the apps adding seperate networks were. Will try that, thank you very much for the tip!
1 Like
@Etone this is 100% the issue. I have followed your reasoning. Created a script that
-
stops all my containers.
-
prunes all (networks)
-
recreates the networks I need
-
ensure that the homey-shs container starts first
-
starts all other containers after
-
openend Homey app on my iPhone.
-
add a matter device.
-
Scan QR code
-
Boom! Done.
I bestow you 
7.10 kudos! 
Awesome job. 
1 Like
“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.”
Do I feel that this is an Athom issue?
Start Homey-shs as second or third, matter does not work.
Start it as a first and all is well.
Congratulations on fixing the issue with your Docker setup!
1 Like
anyway…. today, and completely unrelated, release v12.11
Homey Self-Hosted Server Changelog | Homey
Matter
- Improved error handling in case Matter could not start.
Restarted docker container last, 3rd, 11th, 2nd, 1st. Doesn’t matter, works every time.
Happy camper here.
1 Like
Found this article this morning: https://support.homey.app/hc/en-us/articles/24629602740892-Using-Matter-over-Thread-with-Homey-Self-Hosted-Server
I am unable to find the mentioned menu item in the Homey iOS app: More (…) → Settings → Thread
Same worked for me. I have 60 containers running on my NAS server. if i stopped all and started Homey SHS as the first i did not get “Endpoint pool full” anymore
- depends on your phone. Does your phone have a Thread antenna (iPhone16e for e.g. does not).
- depends on your Homey. Homey-Pro and Mini have a Thread antenna. Homey-SHS or Bridge do not.
but is it still an issue after v12.11. Not for me, but I don’t have 60 containers. Could you test what happens if you start it last?
