Post

Replies

Boosts

Views

Activity

Reply to Thread topology data: no API path for parent-child relationships
Filed as FB23817144. Kevin, thanks for the pointer on matterNodeID and the ecosystem pairing flow. We decided to pivot for a bit since the path wasn't clear in February and have launched the app (https://homemapper.app). The next version v26.3.0 (currently in TestFlight review) does have Thread diagnostics and topology relationship for Matter-over-Thread (reading cluster 0x0035 through the shared controller works), but the hole is Apple Home-provisioned Thread devices. Those Thread device roles, RLOC16, and neighbor data are not reachable from any HomeKit API. So still chasing this. A read-only diagnostics read on HMAccessory or HMHome would probably solve the issue. And yes, definitely taking feature requests.
2w
Reply to Thread topology data: no API path for parent-child relationships
Filed as FB23817144. Kevin, thanks for the pointer on matterNodeID and the ecosystem pairing flow. We decided to pivot for a bit since the path wasn't clear in February and have launched the app (https://homemapper.app). The next version v26.3.0 (currently in TestFlight review) does have Thread diagnostics and topology relationship for Matter-over-Thread (reading cluster 0x0035 through the shared controller works), but the hole is Apple Home-provisioned Thread devices. Those Thread device roles, RLOC16, and neighbor data are not reachable from any HomeKit API. So still chasing this. A read-only diagnostics read on HMAccessory or HMHome would probably solve the issue. And yes, definitely taking feature requests.
Replies
Boosts
Views
Activity
2w