6 ms·
Vendor lock in. https://news.ycombinator.com/item?id=45658056 https://news.ycombinator.com/item?id=45658056 edit: Feel free to down but the evidence is in the
by WaitWaitWha 11mo ago
Vendor lock in.
https://news.ycombinator.com/item?id=45658056 https://news.ycombinator.com/item?id=45658056
edit: Feel free to down but the evidence is in the products.
Zigbee will work with any other Zigbee device if it is properly implemented. not so with Thread.
- deleted 11mo ago[deleted]
- RealStickman_ 11mo agoPlease enlighten me how the ip-network-using mattress in any way relates to a Matter and Thread network
- WaitWaitWha 11mo ago>I can only speak to my experience, certified devices by the largest firms will mostly not interoperate (fails around authN). >Apple: Keeps Thread credentials locked to HomeKit's border routers. >Google: Shares some credentials, but only within Google Account environment. >Amazon: TBD, but their Matter implementation is mostly cloud-tied. >Samsung: Hybrid approach; still best when used inside SmartThings, their 1.4 update seems to support for joining existing Thread networks. Still have to test it. >So, even though Thread theoretically allows full interoperability, no vendor wants to be reduced to a dumb router in someone else’s ecosystem. >there is no easy way to bridge Apple Thread to Home Assistant or Google Thread, even though it is theoretically supposed to be possible from a protocol standpoint. >If you have such solutions, let me know, because I would take full advantage of it, and will regale your contributions in multiple home automation threads.