I'm using Lock Code Manager to deal with some codes on a Schlage BE486/BE489 lock. I had it for quite a few years and it's been working great. I haven't added a new code to it for about a year now and I was trying to add one yesterday. Every attempt failed. I was able to delete codes, just not add new one.
I have gone through all the help steps I can think of with the exception of removing and repairing the lock.
There are the logs I've pulled with debug on.
Lock:
Lock Code Manager:
ANy ideas?
Are you able to add a new lock code directly from the driver details page?
No, it shows up in the state variables but seems to be stuck there. Same when I do it via Lock Code Manager.
I did try to enter a code from the details page that was a new position and name, but the same as another code and it gave me a warning that it was already in use.
The setCode command shows up on the DEBUG log, but otherwise just remains in state variables.
Note that I also changed the batteries to fresh just to make sure it wasn't a battery issue even though it was showing up at 99%.
But otherwise it seems to be stuck.
I thought this lock supported like over 200 codes? I didn't see fetch code return that many. Wondering if this is a routing issue, maybe they ZWave repair on that node?
30 codes, I believe. I can certainly try the repair. Good idea.
It seems to be working for everything else, which is partly why I thought maybe it was related to the Zwave-JS upgrade.
My locks have 3 codes each a mixture of Kwikset zigbee and Yale zwave...I also havent touched this app in a very long time (3yrs), my Yale lock recently showed last status was deleted naturally it was my code somehow was deleted I did recent convert to zwavejs??. I am unable to add or delete codes to anything it fails to add new user with the error below. Adding locks back to existing users also fails the job fails. Isn't LCM a hubitat app?
Lock Code Manager
Error: Cannot get property 'user' on null object
It's working cleanly for me now. But as I noted I had to re-pair the Schlage lock as there was seemingly some issue with the codes getting to it--I assume encryption issues.
So nothing was working here as far as setting codes, I got pissed and decided to rewrite the drivers which ultimately fixed it. I also crafted an app for lock codes with some additional features and functionality. I got some more testing to do this week but I think I am on a good path
Some of us (me) would be interested in seeing your work.
Hubitat's LCM is due for a complete re-write, I'm open to including additional features, if you're willing to share.
I would enjoy the opportunity to be part of that process.
One other note about my resolution of this: I did change my Schlage lock from the Schlage driver to Generic Z-Wave Lock. This did not resolve the issue initially, but was in place when I redid the pairing. I still think the ultimate issue was the Zwave-JS and something with the encryption.
Yeah, that bit and this lock aren't having exactly having a love affair...
I actually have a Yale replacement for it that I have not installed. Maybe now is the time...
I also agree all my lock issues started when I switched to Zwave-JS....it sounds insane but my code was deleted from the locks. I haven't added or changed codes in years. The app I wrote was working somewhat...but the debugs pointed to the device drivers. Once I got them rewritten codes began to push and program correctly in the locks. Both my locks use the Generic drivers zigbee and zwave.
I need to do more testing but I am more than happy to share the drivers and app, once I know I will not cause mayhem for others 
