3 ms·
> The biggest blocker is that thread border routers have no vendor interoperability (you have to buy a bridge for every vendor) Why? They all work ~fine on zig
by tjoff 3y ago
> The biggest blocker is that thread border routers have no vendor interoperability (you have to buy a bridge for every vendor)
Why? They all work ~fine on zigbee which is pretty much the exact same thing just with even less oversight.
I haven't bought into matter/thread because I haven't found a single device I want yet.
- ianburrell 3y agoZigbee and Thread are not the same thing. They use the same 802.15.4 radio. Zigbee does its own wireless mesh protocol, and then adds profiles on top. With home automation being most common. Thread uses 6LoWPAN to run IPv6 on 802.15.4. Thread adds a mesh network. Matter is the home automation protocol on top of that.
- tjoff 3y agoFrom an systems perspective they are the same thing. Zigbee vs. Thread is just transport. The protocol on top of that is what matters and the sole purpose (from my narrow perspective) of Thread+Matter was that this would be a team effort to allow different vendors to talk to eachother. And with that in mind IPv6 feels like a decent choice. If vendors don't respect that foundation then the whole point of Matter+Thread is just gone.
- Tijdreiziger 3y agoEven on Zigbee, there are slight incompatibilities between vendors.
- rubatuga 3y agoYou can't add zigbee lights from IKEA to a philips hue bridge and have them show up in homekit. [0] [0]: https://www.reddit.com/r/Hue/comments/cpbu9w/ikea_tradfri_bulbs_hue_app_apple_home_kit/ https://www.reddit.com/r/Hue/comments/cpbu9w/ikea_tradfri_bu...
- tjoff 3y agoThat's an issue with the hue bridge though (and maybe homekit). There certainly are issues with the zigbee devices, but that is not it.