Schlage BE469 Unable to access settings in ST app Unable to manage codes after the code migration

I’m so frustrated with ST now after the new app update and lock code managment change.

I can’t access settings for any of my Schlage BE469 locks or ZOOM sensors in the ST app, you click on the device it makes the pressed animation but nothing happens.

I was also stupid enough to let ST migrate my lock code management and now I can’t add or remove codes in the app. Settings are available in the web app only. The locks also force me now to use 6 digit codes minimum instead of 4 digits. (tried changing that in the web interface but it made no difference)

Can someone PLEASE save my sanity and tell me what to do?

I tried to remove the lock and add it again tried different drivers, but no joy. By default the driver installed is Z-WAVE Lock PH (can open the settings but it will not change any of them and no code management available. If I change the driver to Z-WAVE Lock I can no longer access the settings all together in the app. Switching back to the previous PH driver will no longer allow me to access the settings in the app. (only removing the lock from the network and adding it again will fix that)

If you are willing to exclude and re-add your lock, the cloud state for your lock will be deleted and you can revert to either Z-Wave Lock PH or to my updated version of that driver that you can find in this topic [ST Edge] Z-Wave Lock BP Beta — Schlage BE468 / BE469. Be aware that excluding and re-adding your lock will loose the names associated with your codes but will not affect the actual PIN codes on your lock.

If you don’t want to do that, you can try installing my experimental version of that driver found in the same channel. For that version, there is a “BP Migration test” button that can be toggled on/off. On driver load, it should read the cloud state and set it to “On”. Once the driver has completed loading and shows the Status as “Ready”, you can turn off the Migration button which should revert the state on both the hub and cloud. Once that happens, you should be able to go back to using SLGA and still able to change Schlage specific features. Nice thing is my driver will preserve code names across driver loads. If you successfully revert the migration, I suggest loading the Beta version of my driver which removes the Migration button.

At this point in time, I do not suggest doing the SLGA->Manager users experience. Only the stock driver allows access to the Manage users dialog and doesn’t support any of the Schlage features nor any advanced automation triggers like my driver does. My driver has all the functional abilities of Z-Wave Lock PH plus a bunch of enhancements. Until ST allows community drivers to trigger the migration and/or support the Manage users dialog, you’ll loose functionality regardless of using the stock driver or community driver.

There are some other design flaws that I reported to ST that they really need to fix before allowing even stock drivers to do the migration. You can read about those in this topic Update for the New Smart Lock Code Management Experience and Beta Opportunity - #16 by h0ckeysk8er

If you decide to use my migration test driver and have any issue, DM me.

Thank you so much for your reply!

I did exclude and re-add the locks many times and about an hour ago I actually seen your thread and tried your driver as well, everything looked great but the second I left the settings page for the lock in the ST app it won’t let me go to settings again. The device button when presses makes the animation but nothing happens it will not go to the device page.

It is unbelievable ST will offer people to migrate without warning if it does not work as it should :frowning:

UPDATE

I deleted the PH driver from my drivers and now when I exclude and re-add the lock it will default to your driver and ( NOT ANYMORE looks like I can still access the device even if I leave the page and go back! :thinking: ) It also reverted the code setting so that is great as well!

THANK YOU SO MUCH!

Spoke too soon, 30min later and I can’t no longer open the device page for both locks in the ST app (tried to uses several phones, all the same problem). Very strange, exactly same problem as my ZOOZ sensors. other devices work fine.

This solved the problem not accessing the lock preferences page ( Rename the lock, force closel the ST app wait a minute and reopen the app)

The rename-and-restart step is the part I would not have thought to try, since giving a device the same profile name sounds like a no-op. What worries me is whether that fix sticks after the hub reboots or the driver gets updated again, or if you end up repeating it every few weeks. I only have one Schlage lock on my garage entry, so I would rather wait and see how stable it is before migrating. For anyone shopping around first, I came across Best Smart Locks of 2026 while reading up on model differences. Has anyone confirmed whether the rename trick holds long term?

I would not do the migration at this point. There have been too many people reporting issues and I’ve identified at least two real defects that I’ve reported to ST that need to be fixed for the migration to be usable.