-
Notifications
You must be signed in to change notification settings - Fork 176
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to detect online Thread end devices from a Matter controller application (CON-1572) #1300
Comments
Use MDNS to look for their entries. You need to know their compressed fabric ID and node ID. You can do this same browse from the ESP MDNS API.
|
@jonsmirl Thanks for your reply. The end devices are commissioned and communicate via Thread though. Only the Thread border Router gets assigned an IP address and mDNS entry. Is that still possible in this case? I would need to detect online Thread devices from the Matter controller application. |
Try the Linux avahi-browse command and you should see them. You can also get MDNS free browser apps for your phone which can see them |
@jonsmirl Ah yes. Indeed I can see the devices using I am trying to figure how to use the the ESP mDNS Service to lookup the Matter Node IDs from within my Matter controller application. |
use mdns_query_ptr() |
I have a Matter controller application based on the provided Matter controller example application running on an ESP Thread Border Router device.
Thread end devices get commissioned via this application via the Thread Border Router and matter commands can be sent successfully.
However, how can I detect which end devices are actually powered on / online? Is there a simple way to ping the devices via some API. I can't seem to find this solution. Thanks.
The text was updated successfully, but these errors were encountered: