Skip to content
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

Closed
tien1608 opened this issue Dec 10, 2024 · 4 comments
Closed

Matter device discovery issue (CON-1464) #1201

tien1608 opened this issue Dec 10, 2024 · 4 comments

Comments

@tien1608
Copy link

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.
IMG20241211054936
IMG20241211054905

Screenshot_2024-12-11-05-50-53-49

@github-actions github-actions bot changed the title Matter device discovery issue Matter device discovery issue (CON-1464) Dec 10, 2024
@shubhamdp
Copy link
Contributor

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

matter ble adv start won't move the device into commissioning state. Assuming you have added a device to first ecosystem, you have to open the commissioning window using the first ecosystem and then you can add the device to another ecosystem. For the second time, device will not advertise using BLE but the mdns.

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

chip-tool pairing open-commissioning-window 0x7283 1 180 1000 3840

# please check the command help for what value is what
chip-tool pairing open-commissioning-window node-id option window-timeout iteration discriminator

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.

@shubhamdp
Copy link
Contributor

@shubhamdp
Copy link
Contributor

@tien1608 Is this still a problem, else can you please close this issue.

@tien1608
Copy link
Author

@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.

@tien1608 tien1608 reopened this Dec 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants