-
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
[NetworkCommissioning] Send Response Command instead of status code for network commissioning cluster #12010
[NetworkCommissioning] Send Response Command instead of status code for network commissioning cluster #12010
Conversation
…or network commissioning cluster
@vivien-apple Can you verify if CHIPTool still works fine? IIRC it just ignored the response and always call default success callback. Thanks. |
PR #12010: Size comparison from ebadd33 to 4d21e3d Increases above 0.2%:
Increases (30 builds for efr32, esp32, k32w, linux, mbed, nrfconnect, p6, qpg, telink)
Full report (38 builds for efr32, esp32, k32w, linux, mbed, nrfconnect, p6, qpg, telink)
|
I would assume that it just works fine looking at https://github.com/project-chip/connectedhomeip/blob/master/examples/chip-tool/commands/pairing/PairingCommand.cpp#L367 since the One can verify that by running |
I applied the patch locally and it just works. I also tried to uncomment https://github.com/project-chip/connectedhomeip/blob/master/examples/chip-tool/commands/pairing/PairingCommand.cpp#L367 and https://github.com/project-chip/connectedhomeip/blob/master/examples/chip-tool/commands/pairing/PairingCommand.cpp#L400 and use an very long SSID just to trigger an error and it does work too |
Problem
Network Commissioning cluster commands are sending status codes instead of cluster commands, this should be fixed
Fixes #12006
Change overview
Testing