Repository navigation
Support multi-endpoint window covering #3191
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
Merged
Merged
Changes from all commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
fa58718
Support multi-endpoint window covering
HunsupJung 87da271
Remove unnecessary code
HunsupJung b971722
Add test units
HunsupJung 418e8f4
Fix wrong status issue and modify test units
HunsupJung c3849ad
Merge branch 'main' into feature/multi-endpoint-window-covering
HunsupJung 05fa702
Change get/set_field to get/set_field_for_endpoint
HunsupJung 75181de
Add handling for the missing child case
HunsupJung f74b93c
Merge branch 'main' into feature/multi-endpoint-window-covering
HunsupJung 11503da
resolve device before handling attributes
hcarter-775 876d3fa
correctly path all events in the child tests
hcarter-775 69613d7
add more tests for comprehensiveness
hcarter-775 98af708
clean up instances where emit_event_for_endpoint was used for child d…
ctowns 67994bd
Merge branch 'main' into feature/multi-endpoint-window-covering
HunsupJung File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Just confirming - will all the child endpoints always have the
window-coveringprofile? For example, none of them support tilt, right?In the future we might want to make this dynamic similar to how we handle child devices in the matter-switch driver, but if this is the only multi-endpoint device we know of for window coverings, we can leave it as is for now and plan to make this dynamic in a follow up.
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.
I don't know how the child lifecycle works, but from the logs it looks like
do_configuregets called for each child once it’s created as anEDGE_CHILD. So it seems we don’t need to check the feature map here.Could you take a look at how the lifecycle is currently set up and let me know what you think?
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.
Yes, child devices do get the
do_configureevent. And currently it looks like all child devices would go through the same match_profile as the parent device because of this.When I look at the testing you provided in the linked confluence page, it looks like all these child devices do have tilt support.