Just a heads up if someones tries to use the Nest Hub / any Thread capable Google Border Router Device.
If you just want to connect your dev device to the Nesthubs Thread Network, you need to get the networkkey from Play Services via the ThreadNetworkClient as described here: https://developers.home.google.com/reference/com/google/android/gms/threadnetwork/ThreadNetworkClien... via the getPreferredCredentials() API.. This will give you the PAN EXPAN and Networkkey, just log it to the console..
On your device via Open Thread CLI do the following (obviously with your panid and network key):
dataset networkkey _YOUR_NETWORK_KEY_IN_HEX_
dataset panid 0x1234
dataset commit active
ifconfig up
thread start
wait a little for the device to join the network, you can check the current state by entering
state
b.t.w. you can search for network by entering
scan
after your device joined the network you should be able to see it´s ips via
ipaddr
and you should be able to ping it from the network where the nest hub is connected 🙂
spacy@egal-12:~$ ping fda0:92ab:bd51:1:615d:74f3:3e42:c238
PING fda0:92ab:bd51:1:615d:74f3:3e42:c238(fda0:92ab:bd51:1:615d:74f3:3e42:c238) 56 data bytes
64 bytes from fda0:92ab:bd51:1:615d:74f3:3e42:c238: icmp_seq=1 ttl=254 time=118 ms
64 bytes from fda0:92ab:bd51:1:615d:74f3:3e42:c238: icmp_seq=2 ttl=254 time=35.4 ms
64 bytes from fda0:92ab:bd51:1:615d:74f3:3e42:c238: icmp_seq=3 ttl=254 time=34.4 ms
64 bytes from fda0:92ab:bd51:1:615d:74f3:3e42:c238: icmp_seq=4 ttl=254 time=58.8 ms
yeay IP via Thread via a Nest Device acting as Border Router :). Main takeaway is that you can get the network key from the Play Services on your android device connected to the same WiFi and being logged into the same Google Account as your Nest Device!
