You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there currently a way for the Matter Controller Client to be able to discover all of the commissioned devices for that controller when requested? The equivalent of using ./chip-tool discover
The matter_controller_client has a DeviceCommissioner and DeviceController class but I can't find any public APIs within these for this. Only discovery of advertising commissionable devices?
My use case is basically to send my Matter Controller Client application a message via MQTT at any time which should then discover and list the currently commissioned devices for that controller.
The text was updated successfully, but these errors were encountered:
github-actionsbot
changed the title
Matter Controller discovery of commissioned devices
Matter Controller discovery of commissioned devices (CON-1484)
Dec 19, 2024
Normally the controller gets the device's node id from cloud and then establish secure session with the device use that node id.
But Matter provide APIs to browse operational nodes and a console command which uses those APIs. You can try it with the console command matter dns browse operational _I{compressed_fabric_id}. Note that the compressed fabric id is the controller's fabric ID.
Is there currently a way for the Matter Controller Client to be able to discover all of the commissioned devices for that controller when requested? The equivalent of using
./chip-tool discover
The
matter_controller_client
has aDeviceCommissioner
andDeviceController
class but I can't find any public APIs within these for this. Only discovery of advertising commissionable devices?My use case is basically to send my Matter Controller Client application a message via MQTT at any time which should then discover and list the currently commissioned devices for that controller.
The text was updated successfully, but these errors were encountered: