Support Closure device type#2875
Conversation
|
Duplicate profile check: Warning - duplicate profiles detected. |
|
Invitation URL: |
Test Results 72 files 507 suites 0s ⏱️ Results for commit f33d782. ♻️ This comment has been updated with latest results. |
|
Minimum allowed coverage is Generated by 🐒 cobertura-action against f33d782 |
611fc50 to
7a0bf8b
Compare
b497ce6 to
3e00e9d
Compare
542367b to
44c80b1
Compare
|
@nickolas-deboom would it make more sense to implement this closure logic as a subdriver? That way, we would overwrite the capability handlers rather than add a bunch of else's to the handlers |
44c80b1 to
50c21ea
Compare
I think that might be a good idea |
61129a1 to
494dd19
Compare
494dd19 to
f33d782
Compare
Check all that apply
Type of Change
Checklist
Description of Change
Add support for the Closure device type.
Note that these changes were originally in #2751, but that PR was based on a branch that would migrate the matter-window-covering driver to matter-switch, which might be done at some point but is a much larger scope. In the interest of supporting this device type sooner, this PR implements this code in matter-window-covering.
Summary of Completed Tests
Tested with VDA Closure and CHIP example app.