-
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
[TC-DL-1.1] FeatureMap and Attribute/Command Lists mismatch #18407
Comments
@yinyihu-silabs Is this using all-clusters-app or lock-app as the server? |
lock-app |
Cert Blocker Review: @franck-apple to find an assignee (maybe @Morozov-5F ) |
I can just enable those commands and attributes in the lock-app but they won't be actually implemented. SDK part of the door lock currently supports only a limited subset of all the commands. |
I think the important part is that anything claimed to be supported by the feature map needs to actually be supported. |
I believe we should enable all features and implement at least stubs for any features we expect V1 production devices to want certifiable. Either path of "remove feature flags" or "implement stubs" works, but they affect what certification will certify. |
Cert Blocker Review: Tagging @cjandhyala to set up an evaluation of this test plan as well. |
@cjandhyala @woody-apple Initially DL had all the requirements as in AppCluster test plan . But as part of PR reviews we had request from reviewers to remove non matter specific requirements. Now in test plan we deleted non matter specific requirements and got the PR approval |
* [#18407] Update attributes and feature map for lock-app * Update auto-generated files
Problem
FeatureMap from chip-tool does not match the outputs from AttributeList and AcceptedCommandList
Given a FeatureMap below, the follow features are enabled: PIN, RID, SCH, NOT
However, AttributeList and AcceptedCommandList return:
As results, many DoorLock test are not testable when required attributes/commands are not supported.
The text was updated successfully, but these errors were encountered: