Hi, I installed Homey on Synology NAS, my problem is that it can’t use matter with Apple HomePod so it doesn’t connect the devices, if I go to the thread settings it gives me this error:
That 404 appears to be sent by Homey’s internal webserver.
Are both the SHS and the mobile app on the latest version?
This photo is from the Thread settings under system in the Homey app for you phone?
Several others, including me, have the same result with the button for the thread settings, it’s must be a bug.
Regarding the problem with using thread in Synology:
Your Wi-Fi must be IPv6 enabled.
And have you read this: Issue with Matter on self hosted Homey - #33 by majorzoltanpepe
Same. Ipv6 is set all things up to date
I have the same issue when accessing the Thread settings on the mobile app, my SHS is running on Ubuntu in a docker container.
Bug Report: GET /manager/thread/active-dataset returns no response
Environment:
- Platform: Proxmox with Docker
- Image: Package homey-shs · GitHub
- Network mode: host
- Privileged: true
Description:
When navigating to the Thread menu item in the Homey app, an error is displayed: Cannot GET /api/manager/thread/active-dataset.
Steps to reproduce:
- Open the Homey app
- Navigate to the Thread menu section
- Error appears immediately
Expected behavior:
The Thread manager should return a valid response (e.g. Success 200) with the active dataset.
Actual behavior:
The server receives the request but never responds to it. No success, no error, no 404 — the request is simply silently ignored by the server.
This can be confirmed in the Docker logs:
Server HTTP GET /manager/thread/active-dataset
[no response logged]
For comparison, all other endpoints respond correctly, for example:
Server HTTP GET /manager/system/ping → Success 200
Server HTTP GET /manager/apps/app → Success 200
All other functionality (devices, flows, zones, apps, notifications) works perfectly.
Conclusion:
The /manager/thread/active-dataset endpoint appears to not be implemented on the server side yet, while the UI is already calling it. Everything else on the self-hosted server is working fine.
Please let me know if you need any additional logs or information.
Thank you for your post to the Homey Community, but it seems that you may need to report this issue to Athom support.
Please, first have a look at [Tip] Problems with Homey?
When you need direct support from Athom please visit Homey Support for our new help center.
- It is very important to report all issues you find: Submit a support request.
If you need help you can read more about how to submit a support request.
Homey dont seem to reply at the moment
Please tell ChatGPT that SDK issues should be posted here: GitHub · Where software is built
I have the same problem. Already tried everything in host seeing if IPV6 is ok and firewall and the problem persists. Hope they can resolve this problem.
PS I also created a Home Assistant docker in the same server with similar docker configuration and Thread worked, so it seems it’s a Homey Self-Hosted bug. The image below is from Home Assistant just to show my thread border router.
Have you raised a ticket?
Homey have had my ticket but not replied. They asked me to confirm i had a thread network and told me to check settings to view that network/available network.
Im not sure they realise thsts the issue
Hopefully sorted soon
I just raised a ticket in GitHub in Network-Manager (couldn’t do it in homey-shs because it’s a package):
GET /manager/thread/active-dataset returns no response · Issue #2 · athombv/network-manager
I’m having the same issue. Did anybody find a solution?
According to Athom this is expected as SHS does not support Thread.
I raised tickets to get this clarified, here’s their response:
"It seems like you are having SHS. SHS doesn’t have his own Thread network. That’s why you get this error message.
In principle, this is where we display the Homey Thread network, but as SHS doesn’t have one, it’s not working at the moment. It’s not (at present) a screen that shows all Thread networks. Perhaps that will change in the future."
I found the following link then here:
When I pointed out that their documentation states otherwise I was advised:
“You are completely right!
That’s a fault at our website. Thank you for bringing this to our attention! We will change this.”
Oh my… that guide was the whole reason why I bought a nanoleaf shapes with TBR, and now you are telling me, that homey is telling you that the whole guide is a lie and that it’s not supported 
@Doekse can you or a team member elaborate on this. Does thread (with external border router) work with Homey shs or not?
As the guide says as well, Matter over Thread can be used with Homey Self-Hosted Server as long as you have a Thread Border Router on the same network of which the credentials are synced with your mobile phone.
Thanks for the quick reply. Why is the error in the UI happening then, is it because the graphical interface is not implemented on shs, but it uses the same interface as the pro models?
Because according to the guide, I should be able to see my thread network in the tab, and i would like to verify that my homey instance can see and communicate with the thread network before investing more money into the project.
Just to clarify, my thread network is up and running, and I have verified it with the official Thread app. Homey works with matter over wifi, so there should be no error on my part.
The UI bug has nothing to do with whether SHS can work with your Thread network.
As Athom support says, that screen in the app (in the case of a Homey Pro) would show the details of Homey’s own Thread network. In the case of SHS, that network simply doesn’t exist. Most likely that screen will just disappear soon. Then they’ll have fixed that.
If you have a border router running in your home, you should (in theory) be able to add Matter over Thread devices by using the standard functionality of your smartphone. An iPhone will do this through its own built-in HomeKit functionality, an Android phone will do this through Google Home functionality.
Your phone then adds the device to your Thread network and to its own fabric. After that, the phone tries to share the device (via LAN/Wi-Fi) with Homey and add it to the Homey fabric. Your device communicates over Thread with your border router, and your border router reaches your Homey via LAN/Wi-Fi.
This process of sharing the device with Homey is where, in practice, many error messages occur. And that part happens over LAN/Wi-Fi, and this is the point where your own network, routers, and server configuration make things difficult. This is IPv6 communication that uses specific protocols. And a lot can go wrong there.
Regarding your Nanoleaf border router: are you able to add Matter over Thread devices to this border router? If that works, it should be possible to share those devices through the Nanoleaf app. You’ll then receive a new Matter pin code. Next, try adding the device to Homey through the Homey app using that pin code (so not the QR code on the device). That way, you should (if all goes well) be able to share the device with your Homey via LAN/Wi-Fi.
Thanks for the in deep answer, that was just the kind I was looking for 
Haven’t bought any thread only devices yet, as I wanted to get the router setup first, to make sure every thing was working.
Thinking of buying the aqara u200 smart lock, as it has relative low entry price compared to Yale’s offerings. But as I understand it only works over thread, if you wanne skip the aqara hub.
Ive had a support ticket in for a while about Matter over Thread.
Homey said the red warning banner is something they will remove and although indicates a problem, its not
As for all the other thread matter issues ( devices jot pairing, dropping offline after a day or so etc) they said they cant t help and to ask the community.
