Sven, do you wear sunglasses at night? If Homeys started burning down in masses, I sometimes think your answer would be: “But you know, you can put them in a fireproof box.”
Of course I know that I can repair devices. I’ve done it many times.
And it is great fun unmounting wall switches to reach the relay behind them, moving shelves to access plugs, or getting to devices that were never meant to be physically touched every few days.
But that completely misses the point of my post.
Homey and Home Assistant are using the same Thread network. The Matter devices are commissioned to both systems through Multi-Admin.
If a device remains fully operational in Home Assistant while Homey loses it, then a general Thread failure is extremely unlikely. The device is still reachable over Thread and its Matter implementation is obviously still functioning.
The failure is therefore on the Homey side of that communication — whether that means its Matter fabric, controller implementation or something around it is another question.
And independently of any Homey-versus-HA philosophy, my definition of a good smart-home system is simple:
Set it up and forget it.
Having to “repair” devices regularly is not normal operation. Neither is accepting that shutters occasionally stay closed in the morning or lights don’t turn on when it gets dark.
If that level of maintenance is acceptable to you, that’s fine. But please stop presenting every Homey problem as something the user should simply work around. That is exactly the kind of fixed-position defence this thread was explicitly not created for.
I think that should be the goal for a Thread-based smart home.
I currently have six Thread Border Routers, all participating in one Thread network. They include Apple, Homey and Home Assistant Border Routers.
That is exactly what Thread is designed for: multiple Border Routers cooperating on the same network, not separate Thread islands for every platform.
