Why not use C.A.F.E in HA and stay within HA?
C.A.F.E is already 90% as good as Homey flows and will improve even more.
Sorry. This might realy be off topic. But just couldn‘t help mentioning it.
As far as I know C.A.F.E is similar as advanced flows, but can’t be extended by third party cards like Homey. Homey is still the king in that category.
C.A.F.E is just producing (and reading back) native HA YAML code. - So it can do everything HA can do. That is the real power of C.A.F.E compared to e.g. Node Red. So, no specific apps or other stuff needed.
But lets stop here because it is really off topic.
Hi Doekse. i really appreciate it that you are in this thread, it show as that your care about helping!
But to be honest, i had a log journey over month with also always total Thread network failures, i did really everything, send day by day reports to Athom, provide Athom access to my system, send them screenshots all the time where i marked everything with time stamps and so on…but they never provide any new solution or knowledge of the analyzes which they made, it was a really really frustrated time for me and i was very disappointed from the Support, i know its not easy because aim also working on a technical Hotline, but not a single one result feedback after weeks of debugging and reporting???
I agree with many statements from Pascal_Nohl, specially with this because i invest also many time to provide Athom informations-reports-detail troubleshooting descriptions and at the end what was the output from my input???
Currently my system is running since i decide by myself to give the system a last chance with a complete reset and start with a clean isolated setup, but this could not be the claim from Athom that a Thread Network is running stable at the end, this are some bullet point of my changes..
- Don’t use Zigbee on Homey Pro 2026 anymore (Hue Bridge Pro manage all Hue devices, kick off all other zigbee devices ) - Multiprotocol-Firmware issue???
- Change the place from Homey and power supplier + usb-c cable - (weak Hardware)
- Change the channels (Thread-Zigbee-Wlan)
- Many changes of the internal UNIFI Network
- Use only Thread-Matter Network from Homey (Kick off Apple-Aqara-Alexa Devices)
- Delete all Thread-Matter keys from other systems which have saved it in there own Keychain
- All Thread-Matter devices (Meross-Eve-Aquara-Govee-Ikea…) directly learned into Homey without MultiAdmin (Delete-Reset all Devices and create a complete new Thread Setup)
- All Apple Boarder Router (4 Devices) which was the masters of the stable Thread Network years before and they should basically work together with Homey are off…they are only devices in Homey and do not have any lead function!
- …many small changes i cant remember:-)
Well, i hope Athom will fix the problems however they are because aim a convicted Homey User and it would be bad if more and more customers are frustrated of the current situation!
I’ve already spent the best part of a month troubleshooting Homey with Thread. Around 2-3 hours most week day evenings, which is time I’d rather spend doing actual life things during the summer time.
I just don’t have the appetite or energy to invest 50 hours into learning and transferring my current flows over to HA. My Thread network has been functioning perfectly and fully stable for three days now.
I just want an easy life and I also don’t want to have the conversation with my partner that she would have to stop using the Homey app to do what she wants to do around the house.
She loves Homey dashboards and it’s not just worth the hassle to learn and implement something new.
I’m open to returning my Thread network back to Homey in the future, but I’d have to be fully convinced stability wouldn’t be reduced in the future. That relies on Athom changing tac on external radios.
I had a very frustrating day with this again.
Most of my Matter-over-Thread devices did not come back, even after more than six Homey reboots. After every reboot I waited around 15 minutes to give Homey enough time to rebuild or stabilize the Thread network. Then, after one more reboot, almost everything suddenly came back — but three devices still had to be repaired before they worked again.
You may ask why I do not simply open another support ticket and send another diagnostic report.
The honest answer is: because at this point it feels like lost time.
I have done that before. I received the usual standard suggestions: check the cable, check the charger, use the dongle, change the position, move Homey somewhere else. I tried those things. They did not solve the problem.
Homey was even placed in the same location as my Apple TV at one point, while all Apple Thread border routers were disconnected. The same devices had worked reliably for around a year with Apple as the Thread border router. With Homey, they did not.
After that, there was no real conclusion, no clear proposal, and no meaningful feedback about what was actually going wrong. That is exactly what Rammstein described as well: it is frustrating, and eventually it makes people stop reporting problems or move on to another system.
I have developed five apps for Homey. I have spent a lot of time testing, reporting, explaining and trying to make things work. But at some point it starts to feel as if this effort does not really matter.
My decision is clear for now. I will not waste my summer making major changes to my setup again. But if the days get shorter and Homey is still not stable by then, I will move forward and migrate to another system.
I would still prefer Homey to work reliably. But right now, the experience with Matter-over-Thread is simply not good enough.
Again, the only way I can really help here is with a diagnostic report. Without that, my hands are tied.
I also quickly checked in with my colleagues from Support today. Your last ticket was closed because they didn’t receive any further response within seven days of their last message. The last message was about Homey Backup’s rather than Matter as far as I can see.
If you’ve made your decision and want to move on, that’s absolutely fine as well, and I’ll close this thread. But if you’d still like me or our Support team to look into this and figure out what’s going on, please give us the opportunity to do so by providing the diagnostic report.
Thank you for the kind words on my research post. That genuinely means a lot, especially coming while you are on holiday. I have tried to make this about contributing something rather than just complaining, so a reply at that level of detail is exactly the exchange I was hoping for. 
I appreciate you saying that, because it matches how mine started. Thread was genuinely rough for me early on, close to going out of the window more than once. It got a lot better over time and has stayed that way. I will call that experience rather than proof, but it was not subtle, so I recognise the picture you describe.
Thank you, that blessing was all I wanted before taking it anywhere. I will set it up in its own thread so this one stays on topic, open to anyone who has actually been through it. Fully understood on sticking to the Forum yourself, and give your girlfriend my regards 
I would like to answer these three in one go, because they are really one question: whether the Home Assistant comparisons are useful or just noise.
Thank you for framing it that way, robertklep. That is exactly what mine were for. It was never Homey versus Home Assistant as a contest, it was the one way I had to take the devices themselves off the suspect list.
And you are right, Hsd1965, we have landed there. The thing is that this conclusion is the output of those comparisons, not a sign they were pointless. It is the part I was trying to help pin down, and now that it is settled I am happy to drop the platform talk and get to the how.
And that is the right way to get to the how, Doekse. My EFR32MG24 on a dedicated RCP is a different implementation from the EFR32MG21 in Multi-PAN, and that difference is most of the point, so I tried to post my own setup at that resolution rather than at the platform level. If there is a specific characterisation your side would find useful, radio, topology or timing, tell me what to capture and I will capture it. And I still have issues with my MR3.
Happy to keep this on the Homey hardware from here.
Then let me be one of the people on the other side of that, Pascal. Not from Athom, just someone who has been exactly where you are.
I went back through your posts, and you have already done the hard part: the extra router plugs, the Wi-Fi tuning, the run of power supply swaps, the move onto a single Thread network off Apple Home, and now the whole Omada rebuild to take your own network off the suspect list. That is more elimination than most people ever do, and you have the one baseline that matters: the same devices ran reliably on Apple Home for over a year. I am not going to suggest you missed a setting, because you clearly did not.
What I would actually like to offer is a fresh pair of eyes on your setup, not a sales pitch for mine. I work in IT for a living, and I have spent a lot of hours on the Thread routing, the border router behaviour and the network underneath it, first on Homey and now on Home Assistant. Sometimes an outside look catches something the person living with it has stopped seeing.
So, a genuine offer rather than a suggestion: would you have time for a call, Teams or whatever suits you, to go through your setup together? Your screenshots, your logs, the Thread side, the network, whatever you want to put on the table. No agenda about which hub you end up on. You have said you would rather Homey worked, and honestly I would rather that for you too.
No rush at all, and after your summer is completely fine. The offer just stands whenever you want it.
I might have to hold you to that one. 
I turned debug logging on for my Thread border router less than a week ago. It has already written about 4.2 million lines, which is roughly 91% of everything that add-on has logged in three months. The Zigbee side is close to 60 million since April.
So if raw logs really are fun for the people who know what they are looking at, then you and your colleagues are very welcome to mine. I will bring the coffee, we can make an evening of it, and somewhere between us we can work out whether I am one of the people who knows what he is looking at. 
No pressure at all. But the haystack is enormous, it is genuinely yours if you want it, and I would enjoy the company while we go looking for lost packages. 
And in all seriousness to wrap this up: The day Homey opens SHS up to third party hardware, even in closed testing, you can put me straight at the front of the queue. Full logs, full access, all of it, whatever helps you work out what is going on. That is the setup where I could actually hand you something useful.
All the best from here either way, and thank you for actually showing up for this one.
Try rebooting all of your apple devices that are thread hubs. I moved everything to my Apple Thread network and everything has finally started working well. If you have Eeros cut off their thread radios — if you don’t you will have no end of problems
Matter Insights | Homey Matter Insights | Homey
Not sure how useful this app will be, but its worth sharing in this thread
More useful than it looks, I think. It adds one virtual device with six numbers: total Matter devices, online, offline, and a split into Wi-Fi, Thread and Bridge. Numeric capabilities normally log to Homey Insights on their own, so after a week you would have a graph of exactly the question this thread has been arguing about since January. Is it Matter in general, or is it Thread specifically. 
The same developer also made Zigbee Insights, which I think is the stronger of the two. Channel, PAN ID, node count, and the coordinator firmware version. @SunBeech, that last one is your #210 question about the Silicon Labs multi-PAN firmware, readable straight off your own hub. 
So @Pascal_Nohl, @smarthomesven, @Welshsmarthome and anyone else still living with this every day. Worth giving them a run first and seeing whether the numbers actually hold up. Neither app has Flow cards or anywhere to report a bug, so nobody should treat them as gospel on day one. But if they do hold up, post your numbers after a week or two. Zigbee channel, coordinator firmware, and the Matter offline graph split into Thread and Wi-Fi. Four or five people posting the same four values would give this thread its first shared dataset instead of another round of us describing how it feels. I hope some of you will share some insights
Thanks to @deejayreissue for posting. 
Yes, indeed. The firmware version is also shown in the Zigbee section of the Homey Developer Tools in the System Information section. So no need for an extra app to get that info:
The post I was referring to does not mention the actual firmware version that is supposed to help mitigate multi-PAN issues. Instead, as far as I understand, it talks about updated SDKs on which the newer firmware (with unknown version) is based. My question is whether Athom is looking into/evaluating the relevance of that updated SDK and the new firmware it produced for Homey Pro.
Thank you for the correction. Good to know it is already in there.
I should have checked that first. 
I do not have a Homey anymore, so I cannot verify anything on that side myself, and that is exactly how I got it wrong here.
Is it Matter in general, or is it Thread specifically.
To add my personal experience as a data point. I’ve been using Matter (both Thread and Wifi) devices with my Homey for almost 2 years. Since I’m running zigbee2mqtt the radio of my Homey is exclusively used for my 30+ Thread (Ikea, Aqara, Hue) devices, so I can rule this out as a potential error source.
With the exception of a botched Firmware Update in February 2025 that caused a bunch of people problems with Matter, I’ve never had a Wifi device drop and I also have some Thread devices that have never dropped a single time in those 2 years.
But there were certain battery powered Ikea devices that I couldn’t keep on the network for the life of me. The Bilresa remotes were the worst offenders, in contrast to the Klippbok water leak sensor that have been rock solid as well despite also being battery powered.
I also have 9 Hue essential bulbs and every few months one of them just decides to go AWOL which is usually fixed by “restarting” the bulb via a power cut.
But all that said, since the Homey version that finally allowed to update all my devices to their latest firmware version it has been nothing but 100% solid without a single device drop. So at least for me I can isolate my problems with Matter devices to a few specific battery powered Thread devices on outdated firmware.
Totally off-topic, but I do want to mention that this app gains full access to a Homey while being close sourced and there’s no clear way to get in contact with the developer.
Homey apps can be updated bypassing evaluation very easily, so any code can be added to this app without anyone noticing.
Just so you know.
But the same is true even if the app is open source, you can just publish whatever to the store
But at least a user will be able to check if it does anything nefarious (we can’t assume that Athom fully checks all files and dependencies of an app).
