-
Notifications
You must be signed in to change notification settings - Fork 463
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
Add Unlatch command and Unlatched status (Unbolt feature) #1756
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Hunsup Jung <[email protected]>
Duplicate profile check: Passed - no duplicate profiles detected. |
Invitation URL: |
Minimum allowed coverage is Generated by 🐒 cobertura-action against 31a85c3 |
713486b
to
e2d8f58
Compare
Signed-off-by: Hunsup Jung <[email protected]>
e2d8f58
to
17ee108
Compare
value: '{{i18n.attributes.lock.i18n.value.unlocked.label}}' | ||
- key: unlatched | ||
value: '{{i18n.attributes.lock.i18n.value.unlatched.label}}' | ||
- key: unknown |
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 think we need to include unknown
or unlocked with timeout
since these are not included in enabledValues
@@ -755,7 +758,7 @@ test.register_message_test( | |||
direction = "send", | |||
message = mock_device:generate_test_message( | |||
"main", | |||
capabilities.lock.lock.locked( | |||
capabilities.lock.lock.unlatched( |
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'm not sure we want to change the existing unit test. I suggest adding a new unit test file that sets the feature_map
to include the UBOLT
feature and then fully exercising the lock/unlock/unlatch functionality
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 got it. For that, we need to remove the tests related to unlatch from current test unit. I will move the unlatch test to new test file.
Signed-off-by: Hunsup Jung <[email protected]>
0613750
to
d5b1d44
Compare
) | ||
|
||
test.register_message_test( | ||
"Handle Lock Operation event from Matter device.", { |
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.
"Handle Lock Operation event from Matter device.", { | |
"Handle Unlatch Operation event from Matter device.", { |
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.
Couple of minor remaining comments but otherwise looks good. Thanks for adding the new unit tests.
@bflorian could you look over the embedded device configs? They look right to me but I'd appreciate a second look
Signed-off-by: Hunsup Jung <[email protected]>
Check all that apply
Type of Change
Checklist
Description of Change
To support the Unbolt feature
https://smartthings.atlassian.net/browse/CPBLTS-2481
Summary of Completed Tests