![schlage deadbolt locks schlage deadbolt locks](https://sc02.alicdn.com/kf/HTB1WbKIPVXXXXcIXpXXq6xXFXXXk.jpg)
So I added a user locally, manually on the lock, and saw in Device Manager the new Null username associated with a new code position. Not one user could be added to the lock using LCM! It had been easily removed and re-added to the mesh (now cleanly functioning thanks to Habitat's work over the last year or so), newly factory reset, then my personal local admin code locally replacing the lock's, all the default local users removed locally, and the lock locally set to 6 digit codes. Then finally, came a final lock which I had reset in testing while trying to unscrew the LCM mess. I then used the DM display repeatedly until the Null users and the null user code positions were erased on each recalcitrant lock. So I also deleted that user in LCM, and reran LCM to add a user to that lock. But also, if I ran Get User Codes on the Device Manager page for that lock, the missing username would show up on LCM’s display for that lock with a Null username. It even showed in the Logs page for the lock while LCM was running. I then realized the locally-entered code for that user showed as a no-username-name “?”, and that code duplication was causing LCM to fail for that user on that lock. After this LCM could add a code for that user. I then went to the Device Manager page for each lock, and began to delete the codes which showed no username. I finally realized I should delete the failed jobs in LCM, and that would then show which locks were the problem for each user. I couldn’t tell which users failed with each lock. LCM never worked cleanly, had many failed jobs. In frustration, pressed for time, especially as I added new locks as time went on, I manually entered codes for people at the lock.
![schlage deadbolt locks schlage deadbolt locks](https://s3.amazonaws.com/assets.knackhq.com/assets/54e658034b4f44e42fb18201/5c740b3308af2f2e7c5c1862/original/be468cam619ho.jpg)
It failed with some users on some locks, others on others. More storms along the way: Lock Code Manager (LCM) was a huge pill. I’m happy, though: the house covers 4,200 sf, two floors, an outbuilding, several steel-clad doors, several aluminum-clad walls. Now Hubitat has fixed the mesh issues, so maybe the repeaters weren’t all necessary. To kick the earlier problems with Hubitat's mesh, per your advice, I added 8 repeaters near the locks. The voyage begins: Adding Schlage locks to Hubitat was a massive pronlem, as your earlier readings here in many threads will attest. Wink stopped development, and could not handle new Schlage Z-Wave Plus locks. While on Wink, I chose the Schlage BE 469s. How I got here: I have lots of outside doors, we travel a lot, I needed remotely managed locks.
![schlage deadbolt locks schlage deadbolt locks](https://cdn11.bigcommerce.com/s-hn76ucwp5f/products/59181/images/130655/FC21PEN619DLT-I__91592.1705935120.386.513.jpg)
The goal of the Odyssey: Make all my locks work in the mesh and with Lock Code Manager. Range Extender 6, and 7 repeaters: 8 near the locks, using the Hubitat Generic Z-Wave Repeater driver. They are using the Hubitat Schlage BE468/BE469 Lock driver. I have used them out of the box, and never updated them. I have no clue as to their internal version numbers. Several are non Z-Wave Plus, several are Z-Wave plus. Hubitat Elevation® Platform Rev C-7 Version 2.3.0.116 Many folks here contributed tidbits of info along this long voyage. Lock Code Manager now runs cleanly with 10 users! I have nine Schlage Z-Wave locks in my home.