zwaveSecurePairingComplete: true
You need to see that in the Data row of the table at the bottom of the device page.
I don't see YRL-220 in any search results here.. so maybe you're the pioneer 
Oh, and @SmartHomePrimer question is important: ZWave or Zigbee.. because I just gave you a ZWave answer. 
Sorry. I misinterpreted your saying it doesn't work with Lock Code Manager. If it's joining securely (pairing is a Zigbee term), then you'll see 0x98 in the InClusters under the DATA field of the driver. I see this with my YRD256.
Thanks, no worries at all.
My unit is Z-Wave, i can buy a ZigBee module for the unit, i wonder if their Zwave module doesnt support the secure feature.
I think people are having more issues with the Zigbee module. I'm not certain, but I think your lock and mine probably use the same Z-Wave module. Mine is working great. Maybe your lock has an older version of the module? Is it Z-Wave Plus?
The ZWave spec is pretty specific about Barrier Devices. Garage Door Openers and Locks are common examples of Barrier Devices.
The spec says, (paraphrased) if they don't join securely 
they must not do anything. And that's certainly the most common comment I've been seeing over the past few months, related to Locks. "My lock paired just fine, but it won't respond to anything." Yep. That's what Barrier Devices are expected to do when not securely joined.
Therefore, I would begin with... the manufacturer (Yale) knows the spec and has a secure ZWave module in your lock.
my thoughts as well, I have a support ticket into them to verify that it joins securely.
It will join my SmartThings hub immediately,
Garage Door opener is on your list, but you don't mention brand, etc. However, it's the same type of device, probably, A Barrier Device and must securely join.
There are two elements to secure pairing: 1) whisper 2) beaming.
Once upon a time, to prevent Man-in-the-middle problems, they lowered the radio transmit power such that the hub to device distance was inches. The idea was, some bad character out on the street, couldn't sniff the secure key, when the power was so low, during the join.
Obviously that has practical problems since the Assembly Instructions for most Locks begin with "Mount this on your door" -- forcing you to find a 100' Ethernet cable to get the hub close enough.
Beaming was created for battery powered devices, you can't have a battery powered device with the radio on most of the time. You won't have any battery life that way.
"Z wave introduced beaming to address this. A nearby mains-powered device, typically a wired wall switch or plug-in pocket socket, will keep repeating the same message to the lock until it is received. So it is the wired device that is using power. This ensures that as soon as the lock wakes up to check, The message will be available. "
BTW, you can do all this with LCM. You just need to get the lock working. Here's the module for my lock and the module for your lock. They say they're not interchangeable in the Amazon description (if correct). Yours appears to not be Z-Wave Plus.
Maybe their's a firmware update from Yale? Can it be sent to the lock via SmartThings if there is one?
I did my Harmony remotes this last week and it's way more awesome in HE than ST!
How do you setup LCM to enable a code for specific repeating days (like every two weeks on Wednesday) and time (morning hours only)?
Oh sorry, you're right. The repeating schedule is not yet available. @mike.maxwell did say this in another post. I should have looked at LCM first.
Oh no worries, I just got excited for a sec and tried to figure it out and couldnt which is why I had to ask...looking forward to that feature because I think thats a critical component to making sure transient lock users are properly contained.
It's back on... Testing my Samsung button on ST as that's what it was made for...
Trying to prove if it's something with Hubitat...
Maybe range... That'd be pretty sad if so... It's so close....
My ST hub went in the mail to a new owner Wednesday. Bye Felicia!
I tried pairing my Schlage BE469 and BE468 Zwave locks the other day with similar results. I reached out to @bobbyD in support and he is working with engineering to see what can be done.
My ST is totally shut down now too. Keeping it around for firmware updates to some devices since I'm not sure that HE supports that yet.
Not a bad idea. HE doesn’t support device firmware updates.
My ST v2 Hub has been unplugged for about 5 days now. I needed to reorganize some wiring and needed the Cat5 cable it was using for another device. I haven’t missed it at all.
I’ll keep it around as I still support ST_Anything for ST users.
I wasn't using ST with much in the way of custom code, other than a specific device handler for motion dimmers. As soon as I migrated all my z-wave and zigbee devices over I yanked the cord on ST hub and haven't looked back.
Already I am doing things with HE that I never even though to do with ST. Also, wanting functionality is making me learn Groovy which reminds me how satisfying it is to get code to function correctly.
I have new doors with dead bolts being installed in the next week or so, I may go to (i know!) nest's yale lock instead, I use all the cameras and thermostats and nest protects so it would all be in one place.
Download the Hubitat app
