#Z-Wave Yale Assure Lock 2 Fingerprint - How to ID the user associated with the fingerprint used?

1 messages · Page 1 of 1 (latest)

woeful trellis
#

I have it integrated using Z-Wave JS UI and keymaster.

When someone uses their fingerprint to unlock, it just says the following in the logbook;

Front Door Lock was unlocked

Any help?

torn shore
#

i don't think you're getting anything better than that

#

Biometric authentication is not part of the zwave spec, yale is doing their own stack on top. so anything related to the fingerprint sensor is not being passed along through z-wave other than the lock opening

woeful trellis
#

I kinda figured that was the deal. It'll send when it's locked manually, so I was hopeful that maybe I missed something... 😦

violet goblet
#

Look at the z-wave js driver debug logs when unlocked and see if any notification is logged

woeful trellis
#

2025-01-07 15:41:26.905 INFO Z-WAVE: [Node 003] CC Notification notification {
type: 6,
event: 6,
label: 'Access Control',
eventLabel: 'Keypad unlock operation',
parameters: { userId: 1 }
}

#

So can I modify that default notification with this info?

#

I am very green with HAOS and Z-Wave.

violet goblet
#

presumably the userId matches a fingerprint, but you'd have to check

woeful trellis
#

I used the wrong terminology. I'd like the logbook to contain the info.

violet goblet
#

You could add your own logbook messages.

woeful trellis
#

I checked, and the userid is as it was setup when I programmed the fingerprints via BT.

#

I have yet to fully complete the keymaster setup. I still need to setup the Lovelace card. Perhaps there are more controls logging in there.

violet goblet
#

I actually see notification cc logs in my logbook

woeful trellis
#

Perhaps I was filtering incorrectly

violet goblet
#

Not sure it would show event data though.

image.png
#

Apparently you can't filter on them.

woeful trellis
#

This is what is in logbook:

Front Door Lock fired Notification CC 'notification' event 'Access Control': 'Keypad unlock operation'

violet goblet
#

Ok, no parameter info then. So you can write an automation to trigger on the notification and use a template to create your own logbook message. You can also associate the logbook with your lock entity if you want to be able to filter.

woeful trellis
#

Thanks for all of your help. I'll see what I can do now.

violet goblet