-
Notifications
You must be signed in to change notification settings - Fork 166
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
Matter device discovery issue (CON-1464) #1201
Comments
I'd suggest you to please take a look at this simplified blog post which talks about Matter multi admin feature https://developer.espressif.com/blog/matter-multi-admin-identifiers-and-fabrics/ Also, please check this small video about how multi admin feature works - https://youtu.be/-NGXwGz8EnQ
I'd suggest you start with chip-tool first and then add the device to chip-tool as described in the Commissioning and Control section. Then open the commissioning window using below command
Then in the chip-tool logs you will see a either QR Code text or manual pairing code, then use that with the ESP-RainMaker application to add that device to RainMaker ecosystem. NOTE: While attaching logs, please paste the logs to the file and attach that file. Its very inconvenient to scrub through the such picturesque logs. |
@tien1608 more detailed chip-tool guide can be found here: https://github.com/project-chip/connectedhomeip/blob/master/docs/development_controllers/chip-tool/chip_tool_guide.md Please check the multi admin scenario section: https://github.com/project-chip/connectedhomeip/blob/master/docs/development_controllers/chip-tool/chip_tool_guide.md#multi-admin-scenario |
@tien1608 Is this still a problem, else can you please close this issue. |
Thank you @shubhamdp , I did it your way and the problem is solved. |
I encountered a problem in Light example. When I connect the device to Esp Rainmaker, I can't connect it to chip-tool at the same time. Even though I enabled advertising BLE on the device, chip-tool still can't detect it. The device I used is esp32c6.
The text was updated successfully, but these errors were encountered: