It will be interesting to see what you end up in terms of your customized driver. I'm sure some Schlage users may be interested in an alternative driver to try out.
I have an older Schlage BE469NX plain Z-Wave lock that I have used on ST (three years) and on HE (three years) w/out any incidents. I'm using the built-in driver on HE. I mean literally zero incidents on HE (or ST for that matter). Joined the hub fine, works 100% of the time, never burns batteries, etc. So the built-in driver isn't "borked" from my perspective, far from it. No idea of course why you're having issues.
Which model lock(s) do you have?
I don't understand why you think Hubitat is "copping out." They decided that they didn't want to support Schlage locks, have communicated that decision to the community, and removed them from their supported device list. That means if we still decide to use a Schlage lock on their hub, what happens is on us.
As long as you don't exclude the locks, you will be fine, but if you exclude and include, they will start to fail. Mine are also BE469NX. They all worked until I excluded and included them. Now 3 of the 5 don't work, the other 2 hum along nicely. I put all of these locks in place in 2019, and didn't start having issues until this past year.
The cop out is the standard answer of "It's a Mesh problem," when 100% it's not a mesh problem, it's a driver problem, as I think I've illustrated. It's not a device problem, it's not a network problem, it's not an interference/SNR/RSSI problem, it's a DRIVER problem. Adding repeaters, moving the hub, etc, etc, etc, isn't going to fix it, code is.
And my experience and previous job was in their field, I worked as a solutions architect for an IIOT (Industrial Internet of Things) company called Trilliant Networks. I currently am a solution design lead and senior engineering manager for a top 8 Fortune 500 company. My college focus as a CpE (Computer Engineering) graduate was automation, robotics and wireless communications (specifically focusing on Zigbee before it was common, think stupid little Xbee modules.) I'm pretty technical.
My biggest complaint right now is that the driver code for this device is locked away, and they have pretty much indicated that it's abandonware. Open source it and release it, I'll fix it.
My Schlage lock also just randomly stops working as well. Same symptoms as OP. This last month, the lock would update it's lock/unlock status on our dashboard just fine, but I couldn't control it.
I just installed the drive he posted in this chat and presto chango! The lock instantly started working again. Didn't reboot, didn't z-wave repair, and didn't exclude and include.
The driver was the first and only thing I did, and it worked immediately afterwards. Interestingly enough, the lock now starts to beep 3 times before it unlocks/locks, which it has never done in the past....so that's pretty cool.
@bravenel does any Hubitat staff want to comment on this?
This driver will do the basic lock/unlock and configure. I'm still having a time with lock code management, but again, the basic lock/unlock functionality is here.
My front door lock has stayed active and working since December 5, so it's definitely an improvement over the built in Hubitat driver. It has endured MANY reboots since then, due to Hubitat version updates, which was the problem since I started having it.
I got everything working last night. It's all spaghetti code at this point, so I'll clean it up and commit it to my GitHub account tomorrow.
Integration with Lock Code Manager works, alarm and beeper modes work, lock and unlock work, encryption works, and best of all, the locks survive a hub reboot.
Very much looking forward to your update. I have 3 Schlage locks on a shelf that worked perfectly with SmartThings but never worked right on Hubitat. I had to replace them with Schlage zigbee versions of the same locks.
Anyway, I will pull one of them down and test your updated driver. I doubt if I replace the locks in the doors. but I was planning on setting up so rules to unlock, lock, etc several times a day and even manually use the keypads. I also want to move them around to different locations around the house to see how the z-wave signal responds.
Good job on this. My fingers are crossed all goes well so I will then know I have backup locks.
I have updated it. The code is still very cludgy and hacked together, but it is solid and works. As I get more time, I will clean the code up, but for now, it's a working driver. I hope this helps out with others.
Unfortunately, this did not work for me. My Schlage locks are the BE469ZP models, and this driver does not work on my locks. I am saddened by this but do hope those with the NX models will have success.
I have weizer smartcode 5 z-wave lever locks. They were using the Schlage driver and all of my locks have stopped working in the last couple of months. They worked for a year without any issues.
I tried excluding them, resetting them, everything. I just gave up and flipped the auto lock dip switch inside and removed them from our hub. Seems I may not be alone here.
I'd love to try but they won't even pair now, they just sit on initializing. I added a different device to confirm it's not the hub and it paired right away.
Hmm... You're stuff looks a bit spread out. You might want to add some beaming repeaters to your mesh. Can you pair the lock within 2 feet of the hub? (before you do, shutdown the hub from the settings menu, unplug for 2 mins and power back up. This will clear the radio)
