Yale YRD Deadbolt Compatibility

🛎️ Get Help
1

@mike.maxwell Since the Wiki doesn't list any Yale products, I thought you may like to know that the Generic Z-Wave Lock DH seems to work with the YALE YRD256 Deadbolt. I haven't had the nerve to test the check, delete or get get code functionality because my codes are already set, and I don't want to risk needing to reset them using the keypad, but the Lock and unlock work perfectly. Very fast response when compared to SmartThings. Current state is reported back instantly as well. Here is a copy of the fingerprint
Fingerprint%20Yale%20YRD256
image

image

I can provide you with any logs if you would like.

1 Like
2

Thanks, I’ll update the driver with the fingerprint, check and getcode won’t do any harm, they only attempt to read codes, they will either work or they wont.

3

Did this work 100%? I'm sure a bunch of people bought these since they're available at a bargain price. Would like to see them on the compatible list.

4

Where are you finding them for a low price? May buy another. The lock / unlock, and reporting work well. I have not tried most of the code setting / deleting functions. The get code and check code don't seem to do anything though.

5

This is what the driver screen looks like. I just checked the live logs and clicking the "Check Code", and "Get Codes" buttons do not generate any log entries.

image
image.png1217×739 19.7 KB

6

They have them new anywhere from $94.50 - $75. depending quantities you buy. https://www.mydigitaldiscount.com/

7

Thanks for the link! I did a search for Yale. Just be aware that the ones they have appear to be the older non-touchscreen version, and only seem to be available only in zigbee. Not that there is anything wrong with that. Just want to make sure you know.

This is the one I am using in ZWave plus
https://www.yalehome.com/en/yale/yalehome/residential/yale-real-living/assure-lock/yrl-assurelock-sl/

8

I bought some from my link and they are zigbee.
I'm not ready to move those off of Smartthings yet. I also am using the Schlage locks.

9

@mike.maxwell - just another data point - the Yale YRD226 doesn't appear to be compatible. It joins with secure pairing, but I don't get any retrieve code options (just a fragmented set of set code options - see below).

It sometimes works (inconsistently) and usually extremely slowly. I first thought it might be Z-wave inconsistency (still might be), but I've been following @bobbyD's guidelines on building a strong Z-wave mesh and I have several strong Z-wave mesh devices close by that lock.

Fingerprint data:

  • deviceType: 32770
  • inClusters: 0x5E,0x72,0x98,0x5A,0x73,0x86
  • deviceId: 1536
  • manufacturer: 297

Z-wave%20Lock1
Z-wave Lock1.png1972×674 30 KB

Z-wave%20Lock2
Z-wave Lock2.png1984×1204 124 KB

10

The event lockCodes schema was not finalized when this driver was written.
They are now complete and this driver is being updated to accommodate them, as well as a preference option to encrypt the code related data events.

Code retrieval will be included in the refresh method.

Did the device work any better when you initially paired it? (assuming it was paired near the hub)

I don't have the zwave version of this lock, so diagnosing issues will be a bit hit and miss.

11

Hi David,

Can you tell me how you associate the Generic driver with the Yale YRD256? I just got this lock, but Hubitat didn't associate it with any driver.

Does it make any difference that I have the Zigbee version rather than Z-Wave? It was impossible to buy a UK/EU Z-wave module for it as Yale refuse to release this lock in the UK. So had to order from the US and get the Zigbee version.

12

OK, figured out that I can change the "type" from Device to the Generic Zigbee Lock. It wasn't intuitive to me that that is where you changed the driver.

It seems to work fine now, in that I can lock and unlock from Hubitat. But it does put warn and error messages in the logs, like

dev:22018-10-25 00:58:03.100:errorCommandResponse skipped 0009, alarmCode:18, [raw:catchall: 0104 0009 01 01 0040 00 9E5C 01 00 0000 00 01 1800FC, profileId:0104, clusterId:0009, clusterInt:9, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:9E5C, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:01, data:[18, 00, FC]]
dev:22018-10-25 00:57:45.294:warnCommandResponse skipped clusterId:0001, descMap:[raw:catchall: C25D 0001 C4 C4 0040 00 9E5C 00 00 0000 0A 00 0700420A79616C656C6F636B76320400420534322E3035050020FF0600210100000020040100212C01020021B004030020010B00210A000C0020160F002300030000, profileId:C25D, clusterId:0001, clusterInt:1, sourceEndpoint:C4, destinationEndpoint:C4, options:0040, messageType:00, dni:9E5C, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0A, direction:00, data:[07, 00, 42, 0A, 79, 61, 6C, 65, 6C, 6F, 63, 6B, 76, 32, 04, 00, 42, 05, 34, 32, 2E, 30, 35, 05, 00, 20, FF, 06, 00, 21, 01, 00, 00, 00, 20, 04, 01, 00, 21, 2C, 01, 02, 00, 21, B0, 04, 03, 00, 20, 01, 0B, 00, 21, 0A, 00, 0C, 00, 20, 16, 0F, 00, 23, 00, 03, 00, 00]]

Not sure if that is significant.

13

The line response skipped may mean something depending on what you were doing with the lock when it logged that.
I can add the fingerprint of your model to the zigbee driver so others don't need to do the device switch.
Pm me if you have the time to help with this.

14

The error and warn were logged when I unlocked and locked the door.

How do I get the device fingerprint?

15

As I said, if you have time pm me, well go over that and also whatever functions aren't working correctly with your lock.
It's not a big secret what we'll be doing, it simply makes my life easier being able to track it that way.

16

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.