For a while now I've been using the built in Lock Code Manager, the Generic Z-Wave Lock driver/device, and some rules to run certain routines when specific people (codes) open the door.
I noticed two days ago that this is no longer working. When I look at the logs for the device I notice that unlocking the door no longer results in an unlock event. Other events fire (lock, polling, etc) - but no unlock events, not for a couple days.
This doesn't appear to be concurrent with firmware updates, and I did a rollback to .118 just in case, to no avail (now back on .123).
Any ideas on why this event stopped firing from the lock?
Solution: There seem to be rather large caps in here (relative to the idle drain), so if doing a batt pull, hit buttons, wait a good ten sec, etc. The first batt pull did nothing, but properly draining it allowed for a proper reboot...and now the events appear again.
Does the lock work fine otherwise? You can lock and unlock the lock from the device settings page? What do Events show from the settings page? Similarly, if you turn on logging, what do the logs show?
The lock indeed works fine otherwise. It can be locked and unlocked via the hub, etc. It doesn't show lock/unlock status...which it always did until this happened.
In the logs I see no errors, but also, no unlock activity...only lock activity. Same with events. What is shown below is the first activity in about 15 mins...which started when we arrived and UNlocked the door. None of that is logged in any way, just goes right to after we entered, when the door re-locked.
The hardware itself is a Kwikset Home Connect 620. Nothing about the hardware or my setup was changed in this time (not by me - no idea what can be pushed to the hub). I did a battery pull on the lock, just in case it was going wonky, but no dice there.
Past threads indicate others use the same lock with the generic driver.
The first thing that stands out to me is the 38% battery level. I would start with some fresh batteries and see what happens. You might not have enough power to transmit and unlock the lock with batteries that low.
What does your lock look like in Z-wave details? Does it have a good signal strength, and very few route changes? Screenshot of this might help here.
I also would check your Z-wave details page, and see if there are any devices that don't have routes. Maybe you lost a repeating device and the lock can't communicate well?
Solution: There seem to be rather large caps in here (relative to the idle drain), so if doing a batt pull, hit buttons, wait a good ten sec, etc. The first batt pull did nothing, but properly draining it allowed for a proper reboot...and now the events appear again.
