Yale Z Wave lock Programming

[potts.mike]

I just installed one of the Yale Zwave touchscreen locks and it is working fine stand alone. I am now trying to integrate it into my z wave network and am having some trouble. I am using a Leviton USB stick and a VRCop as the controllers. Is there a "program" button on the lock some where I am missing? I have searched the internet and found no document actually describing how to include the lock in a zwave network.

Any help much appreciated.

-Mike

 

[Jwbarrett]

Enter ther 6 digit programing code hit #
press 7 #
then its 1# to register or 3# to delete it from the network

If you do a google search for "HAI_Z-Wave_Lock_Integration_1-4-2012.pdf" it gives you a walk thru on setting up locks

 

[potts.mike]

I'll give that a shot, I didn't think to search for HAI since the vrcop isn't connected to a hai system.

 

[potts.mike]

I have the lock setup and it is included in the network as well as associated with the vrcop.

I am trying to unlock the door over hyper terminal using the instructions in this document http://communities.leviton.com/docs/DOC-2392

I enter: >N2SS98, 1 ,0

and recieve: <E014
<N002:152,128,004,158,096,240,023,117,150,035
<X000

Any idea what <E014 error is?

 

[Jwbarrett]

Try

N2SS98,1,0 Unlocks the door lock node 2 - No space before the 1 or after

 

[Dean Roddey]

Error 014 isn't defined in any of the documents I have.

 

[potts.mike]

I didn't see it either. I am out of town all weekend so I'll have to get back to this on Monday.

 

[potts.mike]

I started over resetting the network, included just the lock, the vrcop, and a 4 button controller and everything seems to be working fine.

 

[Dean Roddey]

Since I didn't have any locks when I wrote the driver, I went by eye, and it appears that the locks are not following the format that the VRCOP says will be used for the general report (by which it's reporting its status asynchronously.) The first byte isn't the command class, it's a zero, and everything else is shifted over by a byte. I have no clue why they would have done such a thing. I've updated the driver, so you can give it a try next time and see if it's doing better.