OTBR acting at BR for Apple Home/Homekit Network #9003
Replies: 4 comments 5 replies
-
Commissioning a Thread device involves transferring Thread credentials to the new device. Apple currently requires those Thread Credentials to be stored within iOS using the iOS ThreadNetwork APIs. |
Beta Was this translation helpful? Give feedback.
-
Hi @jwhui , |
Beta Was this translation helpful? Give feedback.
-
The entitlement developers need to use the ThreadNetwork API: com.apple.developer.networking.manage-thread-network-credentials Your app must have this entitlement to invoke the ThreadNetwork API. To get the entitlement, request permission from the ThreadNetwork Framework Entitlement Request page. |
Beta Was this translation helpful? Give feedback.
-
@jwhui Maybe we can open source an Android (and iOS) sample apps to show how the developers can integrate their OTBR-based products with mobile. It will help us make OTBR production-ready. |
Beta Was this translation helpful? Give feedback.
-
Hi team,
Just having a bit of fun with a RPi 3 I had laying around and a nRF52840 dongle I just purchased and have now spun up OTBR on it and it "seemingly" works as expected. I can log in via WebUI and provision/form a new Thread network, but that's where my success ends. My expectation was that I might be able to then use this setup as a BR for my Homekit/Apple Home network and get some of my thread-enabled devices onto a more robust network versus Bluetooth. However, my outcome is that I cannot see this BR in Eve and it doesn't seem to be connected to my Homekit architecture. Is what I am looking to do actually possible? If yes, what am I missing?
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions