Zwave Lock: Remove Migration on Added - #3127
Merged
Merged
Conversation
|
Channel deleted. |
hcarter-775
force-pushed
the
remove/zwave-migration-on-added
branch
from
July 16, 2026 23:25
37b6715 to
a8397de
Compare
hcarter-775
commented
Jul 16, 2026
hcarter-775
force-pushed
the
remove/zwave-migration-on-added
branch
from
July 16, 2026 23:28
a8397de to
9d3e899
Compare
varzac
approved these changes
Jul 17, 2026
NoahCornell
approved these changes
Jul 17, 2026
cjswedes
reviewed
Jul 17, 2026
cjswedes
approved these changes
Jul 17, 2026
ctowns
approved these changes
Jul 17, 2026
ctowns
added a commit
that referenced
this pull request
Jul 17, 2026
Zwave Lock: Remove Migration on Added (#3127)
ctowns
added a commit
that referenced
this pull request
Jul 17, 2026
Zwave Lock: Remove Migration on Added (#3127)
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
Tested on-device.
After onboarding, device functions with lockCodes capability as expected.
Migration functions as expected.
After migration, new capabilities function as expected