Skip to content

Z-Wave Lock: Restore Migration on Device Added - #3323

Merged
ctowns merged 1 commit into
mainfrom
restore-zwave-migration-on-add
Nov 4, 2026
Merged

ctowns merged 1 commit into
mainfrom
restore-zwave-migration-on-add

Conversation

@ctowns

@ctowns ctowns commented Nov 3, 2026 •

Copy link
Copy Markdown
Contributor

This reverts commit b6e09b3. Only conflicts were in test_schlage_lock.lua, which have been resolved.

Check all that apply

Type of Change

  • WWST Certification Request
    • If this is your first time contributing code:
      • I have reviewed the README.md file
      • I have reviewed the CODE_OF_CONDUCT.md file
      • I have signed the CLA
    • I plan on entering a WWST Certification Request or have entered a request through the WWST Certification console at developer.smartthings.com
  • Bug fix
  • New feature
  • Refactor

Checklist

  • I have performed a self-review of my code
  • I have commented my code in hard-to-understand areas
  • I have verified my changes by testing with a device or have communicated a plan for testing
  • I am adding new behavior, such as adding a sub-driver, and have added and run new unit tests to cover the new behavior

Description of Change

This is a restoration of the same auto-migration functionality that used to be included in this driver, but was removed to address issues and coordinate with partners. It is now being added back in anticipation of the forced migration to sunset SLGA.

Auto migration on add is already included in Zigbee and Matter lock drivers, so this will bring Z-Wave up to parity.

Summary of Completed Tests

Tested on a Yale lock, and includes unit tests.

Further testing will be done in beta alongside some of the master/admin code changes we are working on.

This reverts commit b6e09b3.
Only conflicts were in test_schlage_lock.lua, which have
been resolved.
@github-actions

github-actions Bot commented Nov 3, 2026 •

Copy link
Copy Markdown

Channel deleted.

@github-actions

github-actions Bot commented Nov 3, 2026

Copy link
Copy Markdown

zwave-lock_coverage.xml

File Coverage
All files 89% ❌
/home/runner/work/SmartThingsEdgeDrivers/SmartThingsEdgeDrivers/drivers/SmartThings/zwave-lock/src/zwave-alarm-v1-lock/init.lua 24% ❌
/home/runner/work/SmartThingsEdgeDrivers/SmartThingsEdgeDrivers/drivers/SmartThings/zwave-lock/src/legacy-handlers/schlage-lock/init.lua 95% ✅
/home/runner/work/SmartThingsEdgeDrivers/SmartThingsEdgeDrivers/drivers/SmartThings/zwave-lock/src/legacy-handlers/samsung-lock/init.lua 94% ✅
/home/runner/work/SmartThingsEdgeDrivers/SmartThingsEdgeDrivers/drivers/SmartThings/zwave-lock/src/lock_utils/utils.lua 88% ❌
/home/runner/work/SmartThingsEdgeDrivers/SmartThingsEdgeDrivers/drivers/SmartThings/zwave-lock/src/lock_utils/tables.lua 98% ✅
/home/runner/work/SmartThingsEdgeDrivers/SmartThingsEdgeDrivers/drivers/SmartThings/zwave-lock/src/samsung-lock/init.lua 87% ❌
/home/runner/work/SmartThingsEdgeDrivers/SmartThingsEdgeDrivers/drivers/SmartThings/zwave-lock/src/legacy-handlers/zwave-alarm-v1-lock/init.lua 89% ❌
/home/runner/work/SmartThingsEdgeDrivers/SmartThingsEdgeDrivers/drivers/SmartThings/zwave-lock/src/lazy_load_subdriver.lua 57% ❌
/home/runner/work/SmartThingsEdgeDrivers/SmartThingsEdgeDrivers/drivers/SmartThings/zwave-lock/src/init.lua 97% ✅
/home/runner/work/SmartThingsEdgeDrivers/SmartThingsEdgeDrivers/drivers/SmartThings/zwave-lock/src/lock_handlers/zwave_responses.lua 85% ❌
/home/runner/work/SmartThingsEdgeDrivers/SmartThingsEdgeDrivers/drivers/SmartThings/zwave-lock/src/lock_handlers/capabilities.lua 94% ✅
/home/runner/work/SmartThingsEdgeDrivers/SmartThingsEdgeDrivers/drivers/SmartThings/zwave-lock/src/schlage-lock/init.lua 98% ✅
/home/runner/work/SmartThingsEdgeDrivers/SmartThingsEdgeDrivers/drivers/SmartThings/zwave-lock/src/legacy-handlers/keywe-lock/init.lua 77% ❌

Minimum allowed coverage is 90%

Generated by 🐒 cobertura-action against 57a2ca6

@github-actions

github-actions Bot commented Nov 3, 2026

Copy link
Copy Markdown

Test Results

   73 files    548 suites   0s ⏱️
3 326 tests 3 326 ✅ 0 💤 0 ❌
5 336 runs  5 336 ✅ 0 💤 0 ❌

Results for commit 57a2ca6.

@ctowns
ctowns merged commit 91a7498 into main Nov 4, 2026
16 of 22 checks passed
@ctowns
ctowns deleted the restore-zwave-migration-on-add branch November 4, 2026 17:34
ctowns added a commit that referenced this pull request Nov 4, 2026
This reverts commit b6e09b3.
Only conflicts were in test_schlage_lock.lua, which have
been resolved.
hcarter-775 added a commit that referenced this pull request Nov 13, 2026
This reverts commit 91a7498.

Conflicts with later changes (#3337, #3339, #3346) in the zwave-lock
tests were resolved by dropping the tests added by #3323 and keeping
the lock_utils require and Schlage mock device that remaining code
and tests still use.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
hcarter-775 added a commit that referenced this pull request Nov 13, 2026
…add-migration

Revert "Z-Wave Lock: Restore Migration on Device Added (#3323)"
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants