Yale YRD220 Zigbee touch screen lock

Tyler · December 4, 2015, 1:01am

Yup! Official support is live!

SmartThingsCommunity/SmartThingsPublic/blob/master/devicetypes/smartthings/zigbee-lock.src/zigbee-lock.groovy

/**
 *  ZigBee Lock
 *
 *  Copyright 2015 SmartThings
 *
 *  Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except
 *  in compliance with the License. You may obtain a copy of the License at:
 *
 *      http://www.apache.org/licenses/LICENSE-2.0
 *
 *  Unless required by applicable law or agreed to in writing, software distributed under the License is distributed
 *  on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License
 *  for the specific language governing permissions and limitations under the License.
 *
 */
import physicalgraph.zigbee.zcl.DataType

metadata {
	definition (name: "ZigBee Lock", namespace: "smartthings", author: "SmartThings") {
		capability "Actuator"

This file has been truncated. show original

There you’ll see the compatible fingerprints for the Yale models.

manufacturer: "Yale", model: "YRL220 TS LL", deviceJoinName: "Yale Touch Screen Lever Lock" fingerprint profileId: "0104", inClusters: "0000,0001,0003,0009,000A,0101,0020", outClusters: "000A,0019", manufacturer: "Yale", model: "YRD210 PB DB", deviceJoinName: "Yale Push Button Deadbolt Lock" fingerprint profileId: "0104", inClusters: "0000,0001,0003,0009,000A,0101,0020", outClusters: "000A,0019", manufacturer: "Yale", model: "YRD220/240 TSDB", deviceJoinName: "Yale Touch Screen Deadbolt Lock" fingerprint profileId: "0104", inClusters: "0000,0001,0003,0009,000A,0101,0020", outClusters: "000A,0019", manufacturer: "Yale", model: "YRL210 PB LL", deviceJoinName: "Yale Push Button Lever Lock"

We’re waiting on a content update before listing it on the site and in the app, but you can click “Connect New Device” in the app right now and pair these devices.

Ronin · December 8, 2015, 3:10am

I am having trouble getting it to pair up properly, it shows up as a thing and then i change the device type in the ide and it doesn’t lock or unlock… Any suggestions? I have 2 of them so i doubt that it is the lock itself.

mythic_glyph · December 17, 2015, 12:12am

Same here. The Zigbee version of the Yale lock does not yet appear in the product list, so I simply chose “Connect new device.” The app will recognize my Yale 210 as a lock. Sometimes, the lock buttons fail to unlock or lock the lock.

Yesterday, the Hub would not even recognize the lock. Here’s how I corrected that problem today:

From within the app, remove the lock from the list of connected devices.
From within the app, remove any other “things” from the list of connected devices.
Manually command the lock to leave the network, according to the user’s guide: PIN#, 7#, 3#
Relocate hub beside the lock.
From within the app, choose “Connect New Device”
Manually command the lock to join the network, according to the user’s guide: PIN#, 7#, 1#
When the app claims it found the lock, try the unlock / lock buttons.

Tab13tab13 · December 23, 2015, 5:29am

@Tyler + @mythic_glyph + @Ronin: Received my new Hub today!

My attempts:
Placed hub inches away from Yale ZigBee (YRD220) lock, and went into add new device mode.
Manually connected to the Yale ZigBee (YRD220) lock:

PIN #, 7#, 1#

Results:
The lock has audible announcement that it is connected to ST hub.
The ST app continues to show “Identifying a Device…” message incessantly.
The https://graph.api.smartthings.com/device/list shows “Thing”, not Yale lock, and Status as “Active”.

At https://graph.api.smartthings.com/device/list, I can update from “Thing” to “ZigBee Lock” even though ST app continues to show “Identifying a Device…” message incessantly. When I back out of the ST app screen that shows “Identifying a Device” I cannot control the Lock/Unlock from the app.

Because of the “new” nature of my hub should I just wait until tomorrow hoping that all firmware and other updates catch up and try again?

I have Live Logging turned on in my browser in case you have questions. Tired. Must sleep. Will resume tomorrow.

Tab13tab13 · December 23, 2015, 3:10pm

I’ve now done this so many times I can do it with my eyes blindfolded…no luck!

Tyler · December 23, 2015, 6:15pm

Please share the live logs when it pairs as well as a screenshot of full device page after clicking on it here.

It sounds like the device isn’t exposing an expected fingerprint to us during the pairing process.

Thanks!

Tab13tab13 · December 23, 2015, 6:33pm

I just re-paired the device using the app:

Here is the device event:

No log errors yet! Then I switch it to a Zigbee lock:

Below are logs the last time I paired…

0e9d6a02-f8d9-4687-b499-ba39de3171bc 10:55:51 AM: debug parse() — Parse returned [:]
0e9d6a02-f8d9-4687-b499-ba39de3171bc 10:55:51 AM: trace parse() — description: catchall: C25D 0001 C4 C4 0440 00 9C9A 00 00 0000 0A 00 0700420879616C656C6F636B0400420533332E3237050020FF0600210100000020040100212C01020021B004030020010B00210A000C0020180F002300030000
0e9d6a02-f8d9-4687-b499-ba39de3171bc 10:52:57 AM: debug parse() — Parse returned [:]
0e9d6a02-f8d9-4687-b499-ba39de3171bc 10:52:57 AM: trace parse() — description: catchall: C25D 0001 C4 C4 0440 00 9C9A 00 00 0000 0A 00 0700420879616C656C6F636B0400420533332E3237050020FF0600210100000020040100212C01020021B004030020010B00210A000C0020180F002300030000
0e9d6a02-f8d9-4687-b499-ba39de3171bc 10:51:20 AM: debug parse() — Parse returned [:]
0e9d6a02-f8d9-4687-b499-ba39de3171bc 10:51:20 AM: trace parse() — description: catchall: C25D 0001 C4 C4 0440 00 9C9A 00 00 0000 0A 00 0700420879616C656C6F636B0400420533332E3237050020FF0600210100000020040100212C01020021B004030020010B00210A000C0020180F002300030000
0e9d6a02-f8d9-4687-b499-ba39de3171bc 10:45:59 AM: debug parse() — Parse returned [:]
0e9d6a02-f8d9-4687-b499-ba39de3171bc 10:45:59 AM: trace parse() — description: catchall: C25D 0001 C4 C4 0440 00 9C9A 00 00 0000 0A 00 0700420879616C656C6F636B0400420533332E3237050020FF0600210100000020040100212C01020021B004030020010B00210A000C0020180F002300030000
0e9d6a02-f8d9-4687-b499-ba39de3171bc 10:45:49 AM: debug parse() — Parse returned [:]
0e9d6a02-f8d9-4687-b499-ba39de3171bc 10:45:49 AM: trace parse() — description: catchall: C25D 0001 C4 C4 0440 00 9C9A 00 00 0000 0A 00 0700420879616C656C6F636B0400420533332E3237050020FF0600210100000020040100212C01020021B004030020010B00210A000C0020180F002300030000
0e9d6a02-f8d9-4687-b499-ba39de3171bc 10:42:21 AM: debug parse() — Parse returned [:]
0e9d6a02-f8d9-4687-b499-ba39de3171bc 10:42:21 AM: trace parse() — description: catchall: C25D 0001 C4 C4 0440 00 9C9A 00 00 0000 0A 00 0700420879616C656C6F636B0400420533332E3237050020FF0600210100000020040100212C01020021B004030020010B00210A000C0020180F002300030000
0e9d6a02-f8d9-4687-b499-ba39de3171bc 10:39:24 AM: debug parse() — Parse returned [:]
0e9d6a02-f8d9-4687-b499-ba39de3171bc 10:39:24 AM: trace parse() — description: catchall: C25D 0001 C4 C4 0440 00 9C9A 00 00 0000 0A 00 0700420879616C656C6F636B0400420533332E3237050020FF0600210100000020040100212C01020021B004030020010B00210A000C0020180F002300030000
0e9d6a02-f8d9-4687-b499-ba39de3171bc 10:37:39 AM: debug parse() — Parse returned [:]
0e9d6a02-f8d9-4687-b499-ba39de3171bc 10:37:39 AM: trace parse() — description: catchall: C25D 0001 C4 C4 0440 00 9C9A 00 00 0000 0A 00 0700420879616C656C6F636B0400420533332E3237050020FF0600210100000020040100212C01020021B004030020010B00210A000C0020180F002300030000
0e9d6a02-f8d9-4687-b499-ba39de3171bc 10:34:30 AM: debug parse() — Parse returned [:]
0e9d6a02-f8d9-4687-b499-ba39de3171bc 10:34:30 AM: trace parse() — description: catchall: C25D 0001 C4 C4 0440 00 9C9A 00 00 0000 0A 00 0700420879616C656C6F636B0400420533332E3237050020FF0600210100000020040100212C01020021B004030020010B00210A000C0020180F002300030000
0e9d6a02-f8d9-4687-b499-ba39de3171bc 10:30:42 AM: debug parse() — Parse returned [:]
0e9d6a02-f8d9-4687-b499-ba39de3171bc 10:30:42 AM: trace parse() — description: catchall: C25D 0001 C4 C4 0440 00 9C9A 00 00 0000 0A 00 0700420879616C656C6F636B0400420533332E3237050020FF0600210100000020040100212C01020021B004030020010B00210A000C0020180F002300030000

Tab13tab13 · December 30, 2015, 12:47pm

I am making my last comment on this thread because my hub and lock can now communicate with each other.
Firstly, thanks to @Tyler for helping me determine the Zigbee module in my lock was incompatible. It was a Control4 module.
Secondly, I was able to replace the Zigbee module with a Z-wave module from GoKeyless.com.
Lastly, with the new module the lock paired almost instantaneously with the hub and I can use ‘User Lock Manager’ with it now (what a great app!)

Topic		Replies	Views
Yale YRL256-ZW2-619 Assure lock problem with Smartthings app Devices & Integrations yale	6	2691	August 31, 2020
Yale YRD220 Connected to SmartThings but NOT responding to Lock/Unlock Commands Devices & Integrations yale	11	2698	August 16, 2019
How to reset Yale LOCK With Z-Wave from ATT Digital Life? Connected Things	46	47693	August 27, 2023
Yale Touchscreen Deadbolt with ZigBee Devices & Integrations	2	1828	March 2, 2017
Can't connect Yale Smartlock Devices & Integrations	9	1609	December 7, 2016

Yale YRD220 Zigbee touch screen lock

Related topics