Yale lock fob identification

[brktnk (AJS)]

I have installed the Yale smartlock and z-wave 2 module and all works great. However the one thing that i haven’t figured out is how to identify a fob/card so when someone enters the house with the Fob it recognises the fob and says who is entering the house (or at least provides a notification/log entry). This works fine if they use the PIN entry method.

Any insight much appreciated.

[JDRoberts]

Tagging @rboy . He has a library of sophisticated code behind a paywall which is very popular ( https://www.rboyapps.com/ ) and in the process of writing that code has become an expert on locks. So he may know.

[RBoy (www.rboyapps.com - Making SmartThings Easy!)]

If your Yale lock captures and reports that information over zwave you’ll need a special device handler which can process that information like this one

[RELEASE] Universal Enhanced Z-Wave Lock Device Handler for Schlage, Yale, Kwikset, IDLock, Popp, Danalock, August Pro, Keywe, Philia, Samsung

A “future proof” Universal Enhanced Z-Wave Lock device handler This device handler is enhanced to fix bugs in the stock ST ZWave Lock Device Handler, include patches for bugs in lock firmwares and bring out additional features for Schalge, Yale, Kwikset, IDLock, Popp, Samsung, Delaney, August Pro, Danalock, KeyWe, Philia, Vivint, Locstar etc zwave locks (see below for a full list of models and features). This works with all ZWave locks and newer ZWave Plus locks (see below for a list of locks tested). It discovers/learns the lock features and automatically configures them. If a feature is not supported by the lock it will not show up or say Unsupported. You need a SmartApp like Lock User Management (LUM), Rental Lock Automater (RLA) or SmartLocks to program user codes, create actions for…

If you want to use that information to get custom notifications or take actions then you’ll need a SmartApp which can process RFID fobs like this one:

[RELEASE] Lock User Unlock/Lock Door Notifications and Actions

User Unlock/Lock Door Notifications and Actions This is a Lock Manager for locks which cannot be programmed through SmartThings but can report events through Z-Wave/ZigBee to SmartThings. It provides functionality of managing actions and notifications when users unlock door and lock doors but with using the existing codes programmed into the lock. (i.e. no lock programming). However, while this app replicates all the functionality of the Lock User Management (LUM) app, related to taking actions and notifications for users, it does not program the lock codes but rather uses the locks existing programmed users. This is great for folks who don’t want to expose their user codes through the ST platform, don’t want/change the codes often, cannot program codes remotely (e.g. RFID cards, FOB’s, …

[brktnk (AJS)]

Thanks for the quick response. Not sure if my Yale model reports RFID and haven’t been able to find any definitive information. Model is Yale Smart Living YD-01-CON-NOMOD-CH Keyless Connected Ready Smart Door Lock

[RBoy (www.rboyapps.com - Making SmartThings Easy!)]

Key fobs are RFID. If your module supports sending that info over zwave the above should work for you just fine to capture and report that information.

[RELEASE] Lock User Management (LUM)

Not the DH however the apps (Door Lock Code User Management…) can do exactly this. You have a place where you enter the Users. So you set the number of Users to 10 and then name each slot accordingly in the SmartApp. One thing to remember is that if you only run one instance of the app then you have to make sure that all your Fobs or KeyCards are added to each lock in the same order as that is the way they are identified via the lock itself. If it is too much trouble to reorder the KeyCards etc. on each lock so they match then I cannot see why you cannot run separate instances of the app, one for each lock. I would also run with RBoys DH, I have found it much better plus you can actually configure the locks themselves via the ST app. (Audio, AutoLock On/Off, AutoLock Timeout etc.) EDIT:…