Exploring Schlage Z-Wave Lock Control Challenges

As a homeowner who recently upgraded to a Schlage Z-Wave smart lock, I’ve encountered some intriguing challenges that I’d love to discuss with the community. The inability to set, clear, or retrieve user codes from the UI has been puzzling. While I’ve managed to set codes using hexadecimal strings like \x31\x32\x33\x34, the system refreshes, and the codes don’t persist. Deleting a code slot also doesn’t work, leaving old codes active even after attempts to clear them.

I’ve noticed that when using \x31\x32\x33\x34, the lock displays the correct code and unlocks, but upon refresh, it reverts. The logs show successful transactions, yet the state doesn’t update. Similarly, setting the code to \x30\x30\x30\x30 or \x00\x00\x00\x00 doesn’t delete the slot; the old code remains active.

This has been a fascinating journey. I’m curious if others have faced similar issues or found workarounds. Perhaps there’s a configuration or a setting I’m missing. I’m also wondering if this is a known limitation of OpenZWave or if there’s an upcoming fix from the developers.

In the meantime, I’m exploring alternative methods to manage codes, such as using the mobile app or third-party integrations. It’s a bit frustrating, but it’s also a great learning opportunity about Z-Wave protocols and lock mechanisms.

I’d love to hear your experiences, insights, or any tricks you’ve discovered while working with Schlage Z-Wave locks. Let’s brainstorm together and see if we can crack this puzzle!