-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
ESP32 examples Readme.md update with chip-tool instructions #13264
Conversation
2564e0d
to
dca28ab
Compare
a7631e9
to
3f379c7
Compare
3f379c7
to
e57cd48
Compare
PR #13264: Size comparison from 99c1985 to e57cd48 Full report (31 builds for efr32, esp32, k32w, linux, mbed, nrfconnect, p6, qpg, telink)
|
92174b4
to
c56532b
Compare
PR #13264: Size comparison from 99c1985 to c56532b Full report (31 builds for efr32, esp32, k32w, linux, mbed, nrfconnect, p6, qpg, telink)
|
c56532b
to
03cffff
Compare
What about old example with python controller? It is not valid anymore? What about commissioning the wifi credentials and resolving the IPV6 with chip-tool? How is that done? |
@SgtPepperFTW Python controller should work as well. But, as the default testing tool now for certification is chip-tool, we've moved the documentation to mention chip-tool. The single command |
@dhrishi I had problem with Python controller, cause I didn't manage to resolve the NodeID with it. Not only it finished with "Couldn't resolve...", but it also crashed with "memory access violation" My other question is, does each "virtual" Light get a dedicated unicast IPv6 address? My understanding is each "end-device" in Matter network is supposed to have unique IPv6 device. Or does it go only for real Wifi and Thread devices? To the chip tool: Can I retrieve a list of all bridge-app ESP32 that were commissioned on the network? Also, can I get a list of all end-point NodeId with description of their clusters assigned to such ESP32s? |
|
Only real Wifi and Thread devices will have unique IPv6 address |
You can get list of device types, endpoints and clusters using Descriptor cluster |
@PSONALl it was commit 99c1985 I figured out that I can use Descriptor cluster, but I wasn't able to retrieve all the information I wanted. The example main.cpp contains But descriptor doesn't return, for example, "Office" or "Light 1", when I am commanding ./chip-tool descriptor read device-list 12344321 2. Also it returns Type 256 for Lights and Type 14 on Node-Id 0. I understand 256 probably means OnOff type and Type 14 means "Bridge App", but I can't find in source code, where does it come from and what other types there exist. |
Problem
What is being fixed? Examples:
Change overview
changed ESP32 examples Readme with chip-tool instructions
Testing
How was this tested? (at least one bullet point required)