Thanks for the link. I read it before but it was beneficial to read it again 
Still curious what others have worked out as a solution, because I don’t really need another Google display in my home 
1 Like
I’m running SHS on a Synology NAS. Tried to setup thread using my Google Nest Hub, but I couldn’t make it stable enough. Besides, I don’t want Google tech in the mix.
I ended up creating my own border router using OTBR on the same Synology, in combination with a Sonoff Dongle Max in RCP mode. In OTBR I created my own thread network.
When trying to commission IKEA and Aqara devices using Homey SHS nothing worked. Error: no border router found.
I ended up using Home Assistant only for adding devices to my thread network. Then sharing them with Homey, using multi-admin. Homey then adds them to the Homey Fabric. After that I can shut down home assistant again. Not ideal, but it’s working.
It’s stable for two weeks now.
Interesting.
I tried setting it up on my dad’s Synology over Christmas but had no luck.
I’d love to see a step by step guide if you ever have time. No rush!
I plan on giving it go using Docker over the next few weeks as I now have SHS running on an Asus NUC
Thread has been terrible on the SHS. Ive tried a few TBR now. Proved they all work well but I either cant get Thread Matter devices into Homey, or when i do they drop off a day or so later and are impossible to repair.
I too have had to bridge them using Home Assistant. Not ideal but works
I had a ticket open with Homey about the issue ans also the issue surrounding the red warning banner that id seen when you try to select thread in the menu with SHS. The ticket went un-answered and closed. I chased up a reply in another open ticket
They have told me the warning is erroneous and will be removed in time.
Today they replied to say that they cant help me more with Thread and to ask the community.
I have replied to say that some on the community are facing similar issues and that Thread / matter really isnt working as it should.
Bottom line, thread and matter just are not ready and it needs work. Id have more respect for them if they just said “ye your right, we will aim to fix it”
The irony is, many are having to use or have started using home assistant more. SHS could lead to a situation for Homey where many eventually jump ship and that the inception of SHS opens the door to HA for more people and less people will buy a lifetime license. Especially now HA has better dashboards and is getting easier.
Dont get me wrong. I really love homey, its flows, apps the community the whole lot. Id just rather they admitted its not quite right with thread now but it will be, washing their hands of it is not really acceptable but maybe im wrong.
I recently had 2 Thread devices become unavailable overnight in Home Assistant after months of working fine so Homey is not alone when it comes to issues with Thread devices.
No I agree but I bet you could add them back quickly - pairing is near instant and you can actually see the thread network HA is using. A feature thats missing on the SHS and apparently wont be fixed!
Ive tried Apple (most success) Aqara, Ikea and smartthings as my TBR. All work exceptionally in their own environment and for sharing to other services except homey. Homey just wont pair to thread/matter devices for hours, days sometimes and then suddenly it does work without any change or reason. Its so frustrating. But within a day or so, they are offline in homey but still working in HA or by their native controller.
Either way Ive given up and after the reply from support saying they cant help me with Thread any more, i kind of feel like they just not interested in improving it
Actually I can’t get them to pair again with HA. I even tried adding them to my AppleTV (which went fine) and then sharing to HA and nothing. I am using a ZBT-1 as my Thread antenna in HA so maybe I will delete it and start over since I only have 2 devices. I am also thinking of switching the ZBT-1 back to Zigbee and installing the Z2M and Homey SHS addons to play around with.
Multi-admin is done over Matter, not over Thread, so if you can pair a Thread device with your ATV and then share it with HA, the ZBT-1 isn’t getting involved in any way. The Thread radio in the ATV handles the Thread part, and the sharing is done over the network using Matter.
Which would suggest a Matter issue between the ATV and HA. You could try rebooting the ATV and try sharing the device with HA again.
I understand all that. I did a bad job of explaining. The reason I thought it was a Thread issue with HA is because my WiFi Matter devices are working just fine in HA. I don’t normally use the ATV for anything related to Matter or Thread. I thought I would give the ATV a try to see if I could get the devices working again in HA. The fact that they will not pair directly with HA or from the ATV is confusing to me.
