3 ms·
The protocol and network are open, but it’s encrypted and as far as I can tell none of the major vendors allow you to export or import the keys you would need t
by alphabettsy 3y ago
The protocol and network are open, but it’s encrypted and as far as I can tell none of the major vendors allow you to export or import the keys you would need to add a bridge from a competing platform.
- toomuchtodo 3y agoSounds like an FTC complaint around interoperability and anticompetitive behavior.
- tjoff 3y agoIsn't that what the Matter QR codes are for? Which I thought were mandatory for all Matter products? I guess a loophole might be to make the border router matter compatible but none of the actual devices. At which point you really shouldn't be buying them anyway.
- alphabettsy 3y agoNo. Thread and Matter are not the same thing. Matter is an interoperability standard so that devices expose a common API. It works over WiFi, Bluetooth or Thread currently. Thread is a network protocol like WiFi or Bluetooth. The QR codes are used for pairing devices to a Matter controller.
- tjoff 3y agoPairing it to the controller, yes. Not the border router. The controller could talk to the border router if needed but that should be it.
- tjoff 3y agoThat was a bit unclear by me. Zigbee relies solely on noone being able to MITM the pairing process, where the security lies in the short window of opportunity and short range. But Matter (and thus the Thread devices we talk about here) has an out of band mechanism for sending keys, since it requires QR + BLE. I guess your point is that you typically can't form a Thread mesh between different border routers of different vendors. Which is unfortunate, but solvable. Don't buy/use border routers from such vendors. Because that problem is not the same as not being able to use a device from vendor X on a non-X border router.