-
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
Allow and ignore '-' characters in manual pairing codes. #22238
Allow and ignore '-' characters in manual pairing codes. #22238
Conversation
The spec does not mention these, but the brand guidelines apparently talk about using them. While ideally all SDK consumers would do the right thing and strip them out on input, we should probably also try for maximal interop and do the same stripping in the SDK itself.
@bzbarsky-apple if not in the spec, should we do this at all at this stage for 1.0? |
PR #22238: Size comparison from 50f9835 to e1991ed Increases (8 builds for cc13x2_26x2, cyw30739, linux, psoc6, telink)
Decreases (4 builds for cc13x2_26x2, esp32, psoc6)
Full report (43 builds for bl602, cc13x2_26x2, cyw30739, efr32, esp32, k32w, linux, mbed, nrfconnect, psoc6, telink)
|
@andy31415 That is a good question. If we don't, all SDK consumers probably need to. Doable, of course, but might not be as good for interop.... |
PR #22238: Size comparison from 50f9835 to 57b77f4 Increases (3 builds for mbed, nrfconnect)
Full report (3 builds for mbed, nrfconnect)
|
Postponed: it seems like applications can ignore - in manual pairing codes, there is no strict need for SDK to check and/or allow it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Marking changes requested to wait until after 1.0 branch
This seems like we should support this for 1.0, given if we don't fix all clients need to adopt this work. |
@andy31415 Please reconsider as this is actually in the spec
This is in the Setup Code specifications, which is outside the "core spec" and under different review process, but still part of what must be met for certification of matter devices. Please consult source of truth in Causeway: https://groups.csa-iot.org/wg/matter-wg/document/27120 |
Dismiss for 1.0 acceptance: it seems SVE participants are hitting this, may as well fix it then.
…p#22238) * Allow and ignore '-' characters in manual pairing codes. The spec does not mention these, but the brand guidelines apparently talk about using them. While ideally all SDK consumers would do the right thing and strip them out on input, we should probably also try for maximal interop and do the same stripping in the SDK itself. * Add test per review comment.
The spec does not mention these, but the brand guidelines apparently talk about
using them. While ideally all SDK consumers would do the right thing and strip
them out on input, we should probably also try for maximal interop and do the
same stripping in the SDK itself.
Problem
Using something with dashes in it as a manual pairing code does not work.
Change overview
Strip out '-' when initializing the manual code parser.
Testing
Tried doing
chip-tool pairing code
with a code with severa dashes inserted and made sure it worked.