Hi, i hope you are doing good.
I have two Yale locks. Model Assure 2 with Fingerprint. I noticed that when I open the door using a code, the lock returns an open status to HE, which is ok.
However, when I open it using fingerprint, the lock remains with lock status in HE. I need to manually close it.
Wondering if there is an updated driver to support this lock. I found nothing about it. By now, I'm trying to workaround this issue via a custom app. No success at all.
The workaround works. For those who are facing this issue, a simple rule fix it. You can create a rule that triggers when the door contact opens and an action that refreshes the status of the door.
What driver are you using for this device? And if you enable debug logging, what do you see come in to Logs when you open the door with fingerprint but the "lock" value doesn't change?
Some other information that you should share:
What hub model are you using? (Check Settings > Hub Details for "Hub hardware version.")
Under Settings > Z-Wave Details, do you have a button at the top that says Switch to legacy Z-Wave? (Don't click anything; this is just to see if you are using Z-Wave JS or legacy Z-Wave.)
This would help figure out whether there is something that can be done in the driver to parse this data, assuming it's there in the first place.
Z-Wave JS is the default for new installs and supported on C-8 Pro only. Legacy is Z/IP Gateway, which the vendor (Silicon Labs) abandoned, forcing Hubitat to find another option moving forward -- and that was Z-Wave JS. Existing compatible hubs can be switched as described above, but Legacy should continue to work indefinitely, so there is no reason to (and a few things to pay attention to if you do).
From a driver perspective, they should behave identically when using the hub's standard parsing and commands, but with JS being a fairly new option, sometimes things come up, which is why I asked the OP.