Agreed. I just built an OTBR compliant router but can’t for the life of me figure out how to join a Nanoleaf device to it. Would love to not be tied to a HomePod just to use Thread. It does have a compliant Bluetooth module, but I need information like it’s IEEE EUI-64 or that in a QR code or something to be able to get the router to scan for the device.
Echoing the above, I'm very interested in the Thread capabilities of the new Nanoleaf hardware, but wondering if it is really Thread, or they just happen to use Thread plus some magic bits specific to HomeKit / HomePod mini.
1) Is there any official word whether it will be possible to control "Thread-capable" Nanoleaf lights using something other than HomePod mini, or are they only with certain "certified" border routers? (in which case what's the point of the Thread standard…)
2) In this new world order where Nanoleaf uses Thread to communicate with (hopefully any) Thread border routers, does this mean there will be some published set of commands? I'm hoping developers can use Thread to exercise the full gamut of capabilities like the Nanoleaf API, and not some limited set (or limited throughput), or channeled exclusively through HomeKit.
3) Can a developer actually direct Thread commands to a light via the HomePod mini (configured as a Thread border router), or is that just an implementation detail between the HomePod mini and the light, but HomeKit is the only way to "speak" to the light?
+1. I don't like that I have to wait a few seconds for my phone to connect my LED strip each time I want to change something. I got a thread dongle and set up a Border Router. I was disappointed to find out that I can't add the LED strip to the thread network.