-
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
Adding Dryer device type #30584
Adding Dryer device type #30584
Conversation
PR #30584: Size comparison from 2899e70 to 55f0f79 Full report (73 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, efr32, esp32, k32w, linux, mbed, nrfconnect, psoc6, qpg, telink)
|
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.
Q: how did you test this?
Just checking the setup here - it looks like serverLocked corresponds to optional/mandatory (ie, does this control if the GUI is changeable?) Are server and client the defaults for zap? What does lockOthers control?
If my description above is accurate, this looks correct, I just want to confirm before checkmarking.
This is based on the device definition for the MA-laundry-washer which is part of the previous spec. The two devices are basically the same, just differing by a slight rename of 2 of the clusters. |
<include cluster="Identify" client="false" server="false" clientLocked="true" serverLocked="false"></include> | ||
<include cluster="Descriptor" client="false" server="true" clientLocked="true" serverLocked="true"></include> | ||
<include cluster="On/Off" client="false" server="false" clientLocked="true" serverLocked="false"></include> | ||
<include cluster="Laundry Mode" client="false" server="false" clientLocked="true" serverLocked="false"></include> |
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.
But ... there is no "Laundry Mode" cluster in Matter XML, and this does not match the current spec either. @eahove
This PR adds only the device type to the SDK.