No, you made a change to your built in driver. Mine quit working about 1.5 years ago, yet my hashed together driver from older "community" code works fine with my locks.
HUBITAT needs to fix their built in driver.
It's not a network problem, it's not a router/repeat problem, it's a driver problem.
I am glad you found a solution to your problem. This is why the community exists, so people can come up with solutions that work for them best. The diver didn't change, or if it did, it was because Schlage released newer firmware and we had to make adjustments to match their latest firmware. Knowing that thousands of users have working Schlage locks, even though they are no longer listed on the Compatible Devices, suggests that you may want to reach out to Schlage to see if you can update the firmware on your locks, so you can use the built-in driver.
By your own company's admission, Schlage hasn't updated their firmware since before Hubitat existed, so that's not the issue, yet the locks up and decided not to work, randomly. And yes, the code was updated, there was a "fix" to the Schlage drivers in a release about 1.5 years ago. It's documented in the release notes.
Soon after that failed, Hubitat decided that Schlage wasn't compatible anymore.
This is not true.
The firmware on my locks hasn't been updated since I bought them, about 3 years ago Yet they failed about 1.5 years ago, so again, that answer is not true, that Schlage updated the firmware.
Look through the release notes for Hubitat, you will find a "fix" for Schlage locks.
I don’t really care about your locks. What I care about is the factuality of the claim that Schlage hasn’t updated their firmware since Hubitat was born.
That’s not true. They were at FW 8.4 in 2018. They’re at 12.x now. And locks with newer firmware work with built-in drivers.
I personally have 3 schlage be469's with above 7.10 firmware. Works fine. Locks to get firmware updates but they have to be done at the factory. They we're removed from the compatibility list because of firmware issues. While I'm glad you got your lock working, the drivers haven't changed in several years. The firmware for z-wave has changed a couple of times since 2020 via the sdk.
Yeah my front door lock is 10.09, I think my backdoor is 11. something and my basement lock is certainly 12.something (the latter 2 don't show firmware on the device page). All paired fine, all work fine. Now I have an older one (non plus) with 6.x firmware on it. Pairs fine on my c5 with the 500 series chip. 700 series won't even see it. Currently sitting in a box... When the c7 came out and I called Schlage for a firmware upgrade and they didn't have them available to the public, they're answer was to simply send me a new lock (z-wave plus with the 10. firmware) Been chugging along ever since
Again, let me repeat. Schlage had updated their firmware in 2019 (10.x) and 2020 (12.x). So I take issue with your claim that Schlage has not updated their firmware since Hubitat was born.
I would anticipate Hubitat engineers to update their drivers to work with updated firmware, which they apparently have. If you use a 15-year old lock with antiquated firmware, you should anticipate that it may not work with drivers designed for current firmware.
But wait. There might be a solution for that. @jdmm72 was able to make changes to the driver and confirmed the lock is working as expected. For others who may have issues with older locks, check out this post.
For now, this thread will be closed as it has overrun its usefulness.
Download the Hubitat app
