Symptom:
On Hubitat with a Schlage BE468/BE469 that joins with S2 Access Control, Lock Code Manager (LCM) (and sometimes the device page Set Code) fails to add codes (“job failed”, “job stuck”, etc.). Deleting may still work. This is especially common when trying to use 8-digit PINs (or any non-default length).
Root cause (likely):
The lock enforces the User Code length policy internally. On some setups, Hubitat/LCM can’t reliably change that policy over Z-Wave when paired with S2, so Hubitat and the lock end up out of sync. If the lock is still enforcing 4 digits, code programming can fail.
Working fix (do this first)
1) Set User Code Length on the lock keypad (this is the key step)
On the Schlage keypad:
- Press Schlage button
- Enter the 6-digit Programming Code
- Press 8
- Enter desired length (4–8)
- Re-enter the same length to confirm
- You should see/hear confirmation (typically 2 check-mark blinks + beeps)
2) Set the same Code Length in Hubitat
In Hubitat → the lock’s device page:
- Use Set Code Length and enter the same value (e.g., 8)
- Save/refresh if needed
3) Program codes normally
After both sides match:
- Use Lock Code Manager to push new codes or
- Use the device page Set Code
Code adds should now succeed reliably.
Notes / Tips
- If you previously tried changing code length only from Hubitat, and adds failed, setting the length on the lock first resolved it.
- This appears tied to how the lock enforces the PIN length policy when paired with S2, but even if the exact reason varies, the above sequence has been a consistent fix.
1 Like
I have experienced this as well. The driver for the Schlage lock has a field for lock code length but it doesn't work. I had to change lock code length via the lock keypad and programming code. Once changed in the lock I was able to load various passcodes of that length.
Just another quirk for a substandard lock that is poorly supported by Allegion, the maker of these products.
I've complained about these locks before but I'm stuck with two of them now due to my desire to key alike these locks with the rest of the locks in my home.
Changing below does not change the code length in a Schlage deadbolt. It might have something to do with clearing all codes of the prior length before changing to a new length but I just grew weary of the experimentation to sort things out since there is next to zero documentation for these locks.
It should in that it should set the codeLength attribute on the device. I don't think Z-Wave supports actually setting this wirelessly in a standard way, so it must be done on the device, and this command is just to set things on the driver side to catch it up to speed.
Looking at the Schlage locks more, I think this actually is possible on at least some of them with a (device-specific) configuration parameter. Perhaps this driver could be updated for that, though since it's not an "officially" supported device (and I don't know which do this -- parameter 16 for the one where I looked), I'm not sure I'd count on it.
But that at least explains what's going on here -- it's not supposed to do that. 
1 Like
Yes to your point FYI below. I didn't take it this far but I suspect doing a manual code length command via the device driver parameter setting should work. Unfortunately the native driver doesn't support parameter manipulation so I guess you'd have to load a tool to change the parameter and then back to the driver?
It also says changing code length automatically deletes all old codes.
This doesn't exist in the lock driver:
Not sure this is germane to the issue but one issue the Schlage locks have with hubitat's LCM is that in order to have longer code lengths you need to factory reset the lock then set the code length then delete the 2 default codes on the lock so that everything is 100% clear then you can add longer code lengths through LCM. If I remember correctly there a few threads on that.
2 Likes
That could explain some issues I had with LCM. I ended up abandoning LCM and just did my config via the device driver.
I don't change the codes often so LCM isn't a big loss for me. I imagine for VRBO type folks its quite useful. Once I got the code length sorted to seven digits (think phone numbers) I was in good shape.
I wonder if the LCM author could do another pass with the learnings from above and tidy-up a few of these gaps?
