Add support for additional Closure device types#2751
Add support for additional Closure device types#2751nickolas-deboom wants to merge 4 commits intomigrate-window-covering-driver-to-matter-switchfrom
Conversation
|
Duplicate profile check: Warning - duplicate profiles detected. |
| - id: refresh | ||
| version: 1 | ||
| categories: | ||
| - name: Door |
There was a problem hiding this comment.
A request for a new Gate category has been opened, and once that's published we can update the category here to reflect that
ce17223 to
4803fa1
Compare
|
Minimum allowed coverage is Generated by 🐒 cobertura-action against 6128583 |
This adds support for Coverings, Gate, Doors, and GarageDoors closure subtypes.
4803fa1 to
b0c7eb5
Compare
| device:emit_event_for_endpoint(ib.endpoint_id, capabilities.windowShadeLevel.shadeLevel(level)) | ||
| end | ||
|
|
||
| function ClosureAttributeHandlers.main_state_attr_handler(driver, device, ib, response) |
There was a problem hiding this comment.
Looking over this logic again, some changes are definitely needed. There is no guaranteed ordering of when these attributes will be processed and so saving the data in fields in these handlers doesn't mean that the fields would contain the latest report if a given attribute is received after another one. I'm going to try a few different ways to restructure this logic and will add some unit tests to verify
16b02c7 to
2b519fa
Compare
2b519fa to
97b819c
Compare
1fa859f to
0b53893
Compare
0b53893 to
6128583
Compare
This adds support for the Covering, Gate, Door, and GarageDoor closure subtypes.
Note that this PR depends on #2714