I have two of these locks that were working fine with Hubitat before.
I was able to add them to Home Assistant. I can lock and unlock them and see their status without any issues.
The problem is that I can’t edit the user codes. When adding a lock, the “user code” value is missing / not available.
I found a few older posts about this issue, but the suggested steps there didn’t resolve it.
Has anyone had more recent experience with these locks or found a solution?
Assuming you’re using the Schlage integration then this feature is coming: https://github.com/home-assistant/core/pull/151014 unfortunately just not in the coming version of Home Assistant as I didn’t get it merged before they cut the latest beta.
After that lands and is in a released version of Home Assistant I will also be working on getting it added a supported lock type in Keymaster and probably Lock Control Manager as well.
Sorry I’m still very new to HA
These locks been around for many years and I saw a few posts of people able to work with them (manage codes) in HA
How was it possible if its only in development ?
I suppose I should correct myself here. I haven’t looked up the management protocol on that specific lock. If it’s a ZWave lock, then you can use Keymaster right away with it to manage the codes. If it’s a WiFi lock, then then change I’m working on getting landed will be needed.
I really should have definitely looked at how that lock is managed. Go install Keymaster. It will let you manage the codes as it’s a ZWave lock.
Its not that simple
Its not because of Keymaster or any other variant of code manager
HA doesn’t believe the lock has any code slots to manage.
As far as I understand this is because the initial “Interview” (the handshake where the lock tells Home Assistant its capabilities) was interrupted or timed out before the lock shared its User Code Command Class. Schlage locks are notorious for being “sleepy” and aggressive about saving battery during this process.
Ah… yes, if the interview didn’t properly complete then you’re going to have that problem. Some Kwikset locks had this problem too. They like to whisper. While it’s a hassle, you might consider excluding the lock from your ZWave mesh, pulling it off the door and bringing it as close as possible to your ZWave controller and then re-including it. I had to do that with a couple of my Kwikset locks in the early days. Though that problem was primarily resolved by just getting a better controller. I find that the ZWA-2 is an excellent ZWave controller and has zero problems talking even to my quietest of devices at the edge of mesh.
The user has BE469ZP models, these are not the same as the old BE469 models (which I have several) that use whisper-mode for inclusion. There’s no need to pull them off the door. BE469ZP is a Z-wave Plus model.
The lock did not interview completely due to the extend time period needed for lock interviews. If you are using ZwaveJS UI then you can change the interview process length by temporarily enabling the following feature:
Once the lock successfully interviews then disable the above feature.
Changing timeout didn’t help
However, I was able to fix it by doing Re-interview and pressing the Schlage lock button every second or two to keep the lock awake.
As long as the end result is good, glad you got it working 
