First, Border Router deployed
from one manufacturer, how can those credentials shared the relevant
apps like HomeKit with Thread, Matter with Thread, other Thread-based
application layers? Second, Thread mesh already exists, how can user
commission new Border Router they purchased the same mesh they
do not know the commissioner passphrase generated automatically for
them?
One method facilitate the sharing Thread Network credentials is
provided the Mobile commissioning APIs, currently available iOS
and Android. The Border Router
then informs the mesh, and any device already the mesh that range
of the device commissioned can commission directly over secure
Thread channel. These APIs have been created their respective mobile
OSes collaboration with the Thread Group; they allow Thread Group
members’ Apps add Thread credentials user’s personal keychain on
their mobile phone.
Rather than educate the user about the Thread commissioning passphrase,
they have instead opted for commissioning Thread devices directly over a
secure Bluetooth channel already-known network.g.
In the quest for smart home simplicity, this method has not yet been adopted
by consumer space deployments including HomeKit and Matter with Thread. Other Thread Group members’ apps can read those
credentials and commission their own Thread devices whatever way they
choose. Border Router Tutorial
Getting and running with your own Thread Border Router made very
straightforward using these instructions from the OpenThread project.
This poses problem for Border Routers.
8. General access these APIs mobile OSes open Thread Group
members, although specific access the APIs apps always requires user
consent.The user (or app) then indirectly tells the Border Router they want to
commission device (e. registering scanned code).
OpenThread open-source implementation the Thread networking
protocol technology developed and released Google and maintained on
