Skip to content

zwave-lock: Schlage sub-driver drops the UserCode Report that confirms addCredential (no commandResult, slot reused) #3365

Closed

Description

@kainpets

Summary

On SLGA-migrated Schlage locks (seen on BE469ZP 003B-0001-0469, and on the 003B-6341-5044, 003B-6349-5044 and 003B-634B-504C models), addCredential emits no commandResult at all. SmartThings accepts the command and lock/keypad events keep arriving, but the driver never confirms or rejects the add.

Cause

After a UserCode:Set, these locks confirm with an occupied UserCode Report whose code is masked (**********) or blank. In schlage-lock/init.lua, is_user_code_report_mfr_specific classifies that report as manufacturer-specific, and user_code_report_handler consumes it, only acting on index 0. The generic handler never sees it, so:

  • set_credential_report_helper isn't called. There's no success and no credential entry, and the busy state lapses after 10 s without a result.
  • tables.next_index keeps returning the same slot, so the next addCredential writes to that same slot. If the PIN landed, it is overwritten.

#3232 / #3318 fixed this only for CODES_FROM_LOCK. #3364 handles the refused (0xFE) case. Nothing yet covers the success case for an add or update.

The pre-migration handlers treated the same report as "code set": the legacy Edge Schlage handler (code_set_event), and the Groovy DTH (zwave-lock.groovy: "Schlage locks sends a blank/empty code during code creation… Some Schlage locks send '**********' during code creation also").

Evidence

Across about 200 migrated, online Schlage locks we integrate with, 22 of the 23 locks that went silent on addCredential in one day were Schlage. On affected locks, keypad unlocks keep arriving with userIndex set to slot numbers that aren't in the driver's credentials table, so PINs are on the lock that the driver never recorded. The hubs report driver build 2026-09-02. main has the same add-path logic.

Suggested fix

Alongside #3364's is_set_rejected:

-- in user_code_report_handler, after the CODES_FROM_LOCK branch
local in_progress = device:get_field(consts.DRIVER_STATE.COMMAND_IN_PROGRESS)
if (in_progress == consts.LOCK_CREDENTIALS.ADD or in_progress == consts.LOCK_CREDENTIALS.UPDATE)
    and cmd.args.user_id_status == user_id_status.ENABLED_GRANT_ACCESS then
  local args = device:get_field(consts.DRIVER_STATE.CREDENTIAL_ARGS_IN_USE) or {}
  if cmd.args.user_identifier == args.credentialIndex then
    zwave_handlers.user_code_report(self, device, cmd)
    return
  end
end

A test mirroring test_schlage_lock.lua would queue a masked occupied report for the pending slot and expect addCredential success.

Questions

  1. When will a driver build that includes Schlage masked User Code reports stop migrated credential synchronization #3232 reach production hubs? Affected hubs still run 2026-09-02.
  2. Is there a way to re-run the one-time code sync on an already-migrated lock?

We have a Schlage BE469 in our lab and are happy to test a beta driver build or share more detail.

Activity

  1. added 7 commits that reference this issue on Nov 19, 2026
    dc1181e
    0456628
    993dd09
    084d0aa
    dfab261
    15ca0b1
    090b1e3
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions