-
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
Support FeatureMap in Network Commissioning cluster #12184
Support FeatureMap in Network Commissioning cluster #12184
Conversation
PR #12184: Size comparison from 6eba258 to 2f10710 Increases (26 builds for efr32, k32w, linux, mbed, nrfconnect, p6, qpg, telink)
Decreases (3 builds for mbed, p6)
Full report (38 builds for efr32, esp32, k32w, linux, mbed, nrfconnect, p6, qpg, telink)
|
Fast track: data definition change only (generally trivial). @yufengwangca - I assume we will have a followup to have platforms reply correctly with functionality here (i.e. all-clusters should say wifi on esp32 and thread one efr/nrf and such)? |
No, the featuremap is used to discover what attributes/commands are implemented and those attributes/commands are selected by the user from ZAP UI, not decided by the platform. The next step is we need to update ZAP UI to add features checkbox, so that the user can enable/disable the features from the UI. |
Problem
What is being fixed? Examples:
Change overview
Support FeatureMap in Network Commissioning cluster
Testing
How was this tested? (at least one bullet point required)