Yale - YRD220-ZW Lock - Added as device but wont lock/unlock

Posted on
Fri Dec 09, 2016 6:24 pm
mpoulson offline
Posts: 79
Joined: Jan 02, 2011

Yale - YRD220-ZW Lock - Added as device but wont lock/unlock

I was able to add the device (log below) but when I press lock/unlock nothing happens on the lock.

Any ideas what I am missing?

Dec 9, 2016, 4:13:57 PM
Z-Wave Debug intiatingSyncUI (timeout in 1500 seconds)

Dec 9, 2016, 4:14:14 PM
Z-Wave Syncing - started for "008 - Keypad Door Lock"
Z-Wave Debug SENT getNodeNeighbors: 01 06 00 80 08 01 01 71
Z-Wave Debug RCVD getNodeNeighbors: 01 20 01 80 60 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 3E
Z-Wave Debug . . getNodeNeighbors: nodeId 008, neighbors: 6, 7
Z-Wave Syncing - retrieved module neighbors list: 6, 7
Z-Wave Syncing - assigning return route to "008 - Keypad Door Lock"
Z-Wave Debug SENT assignReturnRoute: 01 05 00 46 08 01 B5
Z-Wave Debug RCVD assignReturnRoute: 01 04 01 46 01 BD
Z-Wave Debug RCVD assignReturnRoute: 01 05 00 46 01 00 BD
Z-Wave Debug . . assignReturnRoute: node 008, success 1
Z-Wave Syncing - assigned return route
Z-Wave Debug SENT requestNodeInfo: 01 06 00 60 08 24 52 E7
Z-Wave Debug RCVD nodeInfoFrame: 01 0C 00 49 84 08 06 04 40 03 72 86 98 1B
Z-Wave Debug . . nodeInfoFrame: node 008, combined class list: 20v1 62v1 63v1 86v1 98v1 72v1
Z-Wave Debug SENT requestManufactureInfo: 01 09 00 13 08 02 72 04 25 53 EF
Z-Wave Debug RCVD requestManufactureInfo: 01 0E 00 04 00 08 08 72 05 01 29 00 02 00 00 A8
Z-Wave Debug . . requestManufactureInfo: node 008, manufacturerId 0129, productId 00020000
Z-Wave Debug . . requestManufactureInfo: Yale, Keypad Deadbolt (YRD210/220/240)
Z-Wave Syncing - retrieved manufacture and model names: Yale - 0129, Keypad Deadbolt (YRD210/220/240) - 00020000
Z-Wave Debug SENT requestVersInfoGen: 01 09 00 13 08 02 86 11 25 54 09
Z-Wave Debug RCVD requestVersInfoGen: 01 0D 00 04 00 08 07 86 12 03 03 22 21 20 4E
Z-Wave Debug . . requestVersInfoGen: node 008, protoVers 3.34, appVers 33.32
Z-Wave Syncing - retrieved protocol version 3.34, app version 33.32
Z-Wave Syncing - retrieved class hierarchy: Routing Slave : Entry Control : Keypad Door Lock (04 : 40 : 03, base 62)
Z-Wave Syncing - retrieved command classes: 20v1 62v1 63v1 86v1 98v1 72v1
Z-Wave Syncing - retrieved encrypt commands: - none -
Z-Wave Syncing - retrieved capabilities: routing, beaming, security, frequentWaking
Z-Wave Syncing - created device "008 - Keypad Deadbolt (YRD210/220/240)"
Z-Wave Syncing - complete
Z-Wave Debug SENT requestLockStatus1: 01 09 00 13 08 02 62 02 25 55 FF
Z-Wave Debug terminatingSyncUI
Z-Wave sent "008 - Keypad Deadbolt (YRD210/220/240)" status request

Dec 9, 2016, 4:14:50 PM
Z-Wave Debug intiatingSyncUI (timeout in 1500 seconds)
Z-Wave Debug SENT enterInclusionMode: 01 04 00 4A C1 70
Z-Wave Debug RCVD enterInclusionMode: 06 (ACK)
Z-Wave started controller inclusion mode with encryption
Z-Wave Debug RCVD inclusionMode ready: 01 07 00 4A 02 01 00 00 B1
Z-Wave Debug SENT exitInclusionMode: 01 04 00 4A 05 B4
Z-Wave Debug RCVD exitInclusionMode: 06 (ACK)
Z-Wave stopping controller inclusion mode
Z-Wave Debug RCVD inclusionMode finished: 01 07 00 4A 02 06 08 00 BE
Z-Wave stopped controller inclusion mode
Z-Wave Syncing - started for "008 - Keypad Door Lock"
Z-Wave Debug SENT getNodeNeighbors: 01 06 00 80 08 01 01 71
Z-Wave Debug RCVD getNodeNeighbors: 01 20 01 80 60 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 3E
Z-Wave Debug . . getNodeNeighbors: nodeId 008, neighbors: 6, 7
Z-Wave Syncing - retrieved module neighbors list: 6, 7
Z-Wave Syncing - assigning return route to "008 - Keypad Door Lock"
Z-Wave Debug SENT assignReturnRoute: 01 05 00 46 08 01 B5
Z-Wave Debug RCVD assignReturnRoute: 01 04 01 46 01 BD
Z-Wave Debug RCVD assignReturnRoute: 01 05 00 46 01 00 BD
Z-Wave Debug . . assignReturnRoute: node 008, success 1
Z-Wave Syncing - assigned return route
Z-Wave Debug SENT requestNodeInfo: 01 06 00 60 08 24 56 E3
Z-Wave Debug RCVD nodeInfoFrame: 01 0C 00 49 84 08 06 04 40 03 72 86 98 1B
Z-Wave Debug . . nodeInfoFrame: node 008, combined class list: 20v1 62v1 63v1 86v1 98v1 72v1
Z-Wave Debug SENT requestManufactureInfo: 01 09 00 13 08 02 72 04 25 57 EB
Z-Wave Debug RCVD requestManufactureInfo: 01 0E 00 04 00 08 08 72 05 01 29 00 02 00 00 A8
Z-Wave Debug . . requestManufactureInfo: node 008, manufacturerId 0129, productId 00020000
Z-Wave Debug . . requestManufactureInfo: Yale, Keypad Deadbolt (YRD210/220/240)
Z-Wave Syncing - retrieved manufacture and model names: Yale - 0129, Keypad Deadbolt (YRD210/220/240) - 00020000
Z-Wave Debug SENT requestVersInfoGen: 01 09 00 13 08 02 86 11 25 58 05
Z-Wave Debug RCVD requestVersInfoGen: 01 0D 00 04 00 08 07 86 12 03 03 22 21 20 4E
Z-Wave Debug . . requestVersInfoGen: node 008, protoVers 3.34, appVers 33.32
Z-Wave Syncing - retrieved protocol version 3.34, app version 33.32
Z-Wave Syncing - retrieved class hierarchy: Routing Slave : Entry Control : Keypad Door Lock (04 : 40 : 03, base 62)
Z-Wave Syncing - retrieved command classes: 20v1 62v1 63v1 86v1 98v1 72v1
Z-Wave Syncing - retrieved encrypt commands: - none -
Z-Wave Syncing - retrieved capabilities: routing, beaming, security, frequentWaking
Z-Wave Syncing - created device "008 - Keypad Deadbolt (YRD210/220/240)"
Z-Wave Syncing - complete
Z-Wave Debug SENT requestLockStatus1: 01 09 00 13 08 02 62 02 25 59 F3
Z-Wave sent "008 - Keypad Deadbolt (YRD210/220/240)" status request
Z-Wave Debug terminatingSyncUI

Posted on
Fri Dec 09, 2016 8:20 pm
FlyingDiver offline
User avatar
Posts: 7189
Joined: Jun 07, 2014
Location: Southwest Florida, USA

Re: Yale - YRD220-ZW Lock - Added as device but wont lock/un

Looks like it was already included on the controller before you tried the inclusion with encryption. Exclude it, then start over again. With encryption.

joe (aka FlyingDiver)
my plugins: http://forums.indigodomo.com/viewforum.php?f=177

Posted on
Sat Dec 10, 2016 4:19 pm
mpoulson offline
Posts: 79
Joined: Jan 02, 2011

Re: Yale - YRD220-ZW Lock - Added as device but wont lock/un

That did not seem to work.

What I have tried.

[*]Removed lock device from Indigo
[*]Excluded the device from Zwave network
[*]Put zwave controller in include mode with encryption
[*]Went to lock and "joined network" with my Zstick Gen5
[*]Attempted to add new device with "encryption mode enabled on new device UI"
[*]-While adding it timed out many time and I tried to keep the lock alive during the addition
[*]After many time I could finally get it added (normally after moving controller out of Inclusion mode with Encryption)

Posted on
Sat Dec 10, 2016 4:29 pm
howartp offline
Posts: 4559
Joined: Jan 09, 2014
Location: West Yorkshire, UK

Re: Yale - YRD220-ZW Lock - Added as device but wont lock/un

mpoulson wrote:
[*]Went to lock and "joined network" with my Zstick Gen5

Do you mean you took the zstick to the lock?

If so, that's the problem - you can't include with encryption unless the zstick is in the Mac.

Try again but leave the stick in the Mac. (It will work via network wide inclusion)


Sent from my iPhone using Tapatalk

Posted on
Sun Dec 11, 2016 12:16 am
srkinard offline
Posts: 320
Joined: Apr 10, 2016
Location: Austin, Texas

Re: Yale - YRD220-ZW Lock - Added as device but wont lock/un

I had the same issues with my Yale lock, so I plugged my Z-stick Gen5 into a 12-foot USB extension cable and moved it closer to the lock...then the Include with encryption was successful. Basically I removed the wall separating the Indigo server from the hallway with the lock so it became line of sight.

Once I did that, the inclusion worked fine and the lock responds perfectly. I use the Z-Wave Lock Manager plugin that Peter (howartp) wrote and it makes managing it super easy.

Ross

Posted on
Wed Dec 14, 2016 9:25 pm
mpoulson offline
Posts: 79
Joined: Jan 02, 2011

Re: Yale - YRD220-ZW Lock - Added as device but wont lock/un

Howartp - thanks for the pointers! Worked like a charm.

Skinard - I had to get a USB extension able to get this to work too.

Posted on
Thu Dec 15, 2016 6:20 am
johnpolasek offline
Posts: 911
Joined: Aug 05, 2011
Location: Aggieland, Texas

Re: Yale - YRD220-ZW Lock - Added as device but wont lock/un

My Kwikset 910 was so far away I had to use a USB to WIFI bridge... it appears that inclusion is a very intensive process and there can be no interference or dropped packets during it.

Posted on
Sat Dec 17, 2016 12:41 pm
dz1rfj offline
Posts: 135
Joined: Mar 13, 2016

Re: Yale - YRD220-ZW Lock - Added as device but wont lock/un

johnpolasek - Can you detail what you used to create a USB to WIFI bridge?

My kwikset will not include correctly, using the usb stick, and it will not include with the stick in the mac, despite the fact that I have a zwave bulb right near the doorlock on the exterior of the cynderblock garage, and an aeotec repeater in the garage.

Thanks!

Thanks
-Brian

Posted on
Tue Jan 31, 2017 7:41 pm
Dewster35 offline
Posts: 1030
Joined: Jul 06, 2010
Location: Petoskey, MI

Re: Yale - YRD220-ZW Lock - Added as device but wont lock/un

This fixed me up too guys! Thanks!

Posted on
Sat Jul 27, 2019 7:19 pm
akimball offline
Posts: 559
Joined: Aug 07, 2013
Location: Sandy, Utah

Re: Yale - YRD220-ZW Lock - Added as device but wont lock/un

Here are the steps I took that finally worked thanks to this thread (yale YRD226ZW):

If previously included but no encryption, select Interfaces -> zwave -> Start controller exclusion mode.
Quickly enter your unlock code ->7 -> wheel -> 3 -> wheel.
(Device excludes from z-wave network)

Remove the lock from the door if installed. Assemble using keypad, battery-pack, and tongue bolt in the right orientation so the “handedness” will be on proper side.

Carry entire dern lock to the computer running indigo and place z-wave aeotec gen5 plus about 1-foot away. Do NOT unplug the z-wave stick like any normal person might want to do!

Factory reset the lock. (Lock must be partially removed from door to reach reset button but it’s already apart.). Remove 1 battery, press the reset button while re-inserting the battery and keep holding button for 4 or 5 seconds. Lock will factory reset.

Re-enter your code.... reset the handedness.... open a new z-wave device in indigo... press “define and sync...”

...make sure the z-wave stick is about 12-inches away from lock for the following...

THEN, enter your code >7 > wheel > 1 > wheel (work fast here)........make sure the correct node device number in indigo’s z-wave is there....finally press “New with Encryption Enabled” and .... it finally worked.

I may buy another one someday so I’m posting for posterity. Oh yeah...don’t forget to re-install the lock.

-Al

Page 1 of 1

Who is online

Users browsing this forum: No registered users and 5 guests