This happened to me with the past two firmware updates for Hubitat after a year of smooth operations.
Hereās what fixed it for me:
- on my phone go to the logs for Hubitat so those are open
- on the lock, disconnect the battery for 30 seconds, reconnect the battery, and then lock/unlock the lock manually with the thumb turn.
- verify that the lock shows the activity in the logs
- with the logs still open, open a new tab and go to the device page for the lock
- change the driver to the Generic Z-Wave Lock driver
- save the device. Then hit āconfigureā. In your logs you should see the lock going through the process of fetching 30 codes (even if you donāt have 30 codes) Sometimes it takes 1-2 minutes before the hub will start to fetch the codes from the lock. Be patient here.
- once the 30 codes are fetched, change the driver back to the Schlage Lock driver. Save the device. And again hit configure while watching your logs to ensure the lock is transmitting all of the codes properly.
If you were able to get through all the steps above, you should be good to go.
If any of the steps fail, start back at step 1. Sometimes I had to do this 3-4 times. Other times only once was enough.
Both of the past firmware updates have caused me to have to do this dance, and then things work properly again.
The Schlage locks arenāt officially supported anymore so Iām not anticipating any more effort on these issues from @bobbyD or @mike.maxwell but I do know that they still want to keep us happy. The issue with the locks are entirely on Schlageās end as far as I, and others, can tell.
EDIT: I have 2 HE C5 hubs on 2.2.3.142. I have 3 Aeotec v6 extenders and 2 locks on one C5 and 2 Aeotec v6 extenders and 1 lock on the other C5. This happens on both my hubs after updating recently. On my hub with the 1 lock there are only 5 total devices attached to it. The lock, the 2 extenders, and 2 GoControl z-wave lights. I isolated the lock with those devices and hub in my garage last year to make that lock work properly.
