Z-Wave Schlage Lock Setup

[Scyto]

My whole house is populated with Jasco switches (mostly on/off) and they do report status to the ISY when operated locally. However, I believe they have to be in range of the ISY directly to do so. I wish I totally understood why these do and others don't. Jasco does not use "Instant Status".

 

Wow! Don't know how I ended up responding to an 8 day old post. Sorry!

I have switches definitely not in range and they seem to report status ok.

 

Wow! Don't know how I ended up responding to a 28 day post

[Scyto]

Hi Alex,

 

The associations look good.

 

It's quite possible that it's a timing issue: nonce/key exchange should not take more than 10 seconds otherwise they get invalidated. So, it seems that the key is not being transported and propagated properly.

 

Both #1 and #2 are excellent. I do very much appreciate all the help and support as we definitely have to get to the bottom of this issue.

 

With kind regards,

Michel

sorry still haven't got around to this, I only just got the vera setup.  Is it ok for me to shift primary to the vera and then turn the ISY off to test inclusion / exclusion with the vera?  I am still seeing very strange behavior with the lock in this 'far location', I have two of them and it is consistent.  I also note when adding the vera as a secondary z-wave controller I had to do it multiple times because this lock was unreachable during the key exchange the ISY facilitated. - just a FYI

[Michel Kohanim]

Hi Scyto,

 

Yes, it's ok.

 

With kind regards,

Michel

[Philbo86]

Hi everyone,

 

I had visited this post a couple of weeks ago when I was trying to add my Schlage BE469 lock to the ISY-994i.  I followed a lot of advice on this forum, spoke with both Universal Devices and Schlage support, but nothing worked.  I just wanted to share my experience on how I finally got a BE469 lock added in case anybody else is having similar issues.  So, after trying pretty much everything under the sun, the Schlage representative agreed to send me a brand new lock free-of-charge, as we concluded it was probably an issue with outdated firmware.  My original lock had firmware version 5.8.  The new lock they sent me is now on firmware 6.8.  You can find this information either on the sticker on the back of the instruction manual or on the lock itself; just take off the cover on the inside of the door and there's a sticker on the back of the cover.  FW Ver.: MAIN_6.8 is the most recent, at the time of this post anyway.

 

So, once I got my new lock I moved the ISY and PLM to the entryway so they were less than a foot away from the lock.  It started to add on the first try, but about half-way through the process, it stopped and not all of the functionality was there.  So, I excluded the lock.  After I excluded the lock, every time that I tried to include it again, the admin console kept popping up with an error message telling me to exclude the lock and try again.  So, after a few rounds of successfully excluding only to have the error message keep popping back up, a lot of restarting the admin console, and a few choice words, I decided to unplug the battery pack from the lock itself.  After plugging the battery pack back into the lock...  Eureka!  Success!  I was able to include the lock on the first try, with no hiccups.  Now, by this point, I did have the ISY basically touching the lock when I was adding it.  I'm not sure that it needs to be that close, but I wasn't leaving anything to chance at this point.

 

Anyway, I just wanted to share my story in case anybody else comes looking for a solution and still might be having issues.  I hope this helps!

[Xathros]

Hi everyone,

 

I had visited this post a couple of weeks ago when I was trying to add my Schlage BE469 lock to the ISY-994i.  I followed a lot of advice on this forum, spoke with both Universal Devices and Schlage support, but nothing worked.  I just wanted to share my experience on how I finally got a BE469 lock added in case anybody else is having similar issues.  So, after trying pretty much everything under the sun, the Schlage representative agreed to send me a brand new lock free-of-charge, as we concluded it was probably an issue with outdated firmware.  My original lock had firmware version 5.8.  The new lock they sent me is now on firmware 6.8.  You can find this information either on the sticker on the back of the instruction manual or on the lock itself; just take off the cover on the inside of the door and there's a sticker on the back of the cover.  FW Ver.: MAIN_6.8 is the most recent, at the time of this post anyway.

 

So, once I got my new lock I moved the ISY and PLM to the entryway so they were less than a foot away from the lock.  It started to add on the first try, but about half-way through the process, it stopped and not all of the functionality was there.  So, I excluded the lock.  After I excluded the lock, every time that I tried to include it again, the admin console kept popping up with an error message telling me to exclude the lock and try again.  So, after a few rounds of successfully excluding only to have the error message keep popping back up, a lot of restarting the admin console, and a few choice words, I decided to unplug the battery pack from the lock itself.  After plugging the battery pack back into the lock...  Eureka!  Success!  I was able to include the lock on the first try, with no hiccups.  Now, by this point, I did have the ISY basically touching the lock when I was adding it.  I'm not sure that it needs to be that close, but I wasn't leaving anything to chance at this point.

 

Anyway, I just wanted to share my story in case anybody else comes looking for a solution and still might be having issues.  I hope this helps!

Thanks Philbo86-

 

I fully suspect the power cycling of the lockset fixed the issue.  I have added my 469 from about 25' away from the ISY without any problems so I don't believe range is that poor during a secure add.

 

-Xathros

[EACAsocal]

I have a Schlage BE468 that has only limited functionality.  I can only "unsecure" or "query" it.  Both of these functions work.  I can remove and exclude this lock at will. 

 

I factory reset the Z-wave dongle and then included the lock again:

Sun11/01/2015 06:53:21 PM : Device 6 excluded from Z-Wave network
Sun11/01/2015 06:54:38 PM : Listening for Z-Wave devices to add to the network
Sun11/01/2015 06:54:53 PM : Z-Wave device detected, retrieving info 2
Sun11/01/2015 06:54:53 PM : Z-Wave device detected, retrieving info 3
Sun11/01/2015 06:54:53 PM : Z-Wave device detected, retrieving info 5
Sun11/01/2015 06:54:53 PM : Adding Z-Wave devices stopped
Sun11/01/2015 06:54:54 PM : Exchanging data with secure Z-Wave device 2 of type 4.64.3
Sun11/01/2015 06:54:54 PM : Adding secure Z-Wave device
Sun11/01/2015 06:54:58 PM : Adding ISY node(s) for new Z-Wave device 2 type 4.64.3
Sun 11/01/2015 06:54:58 PM : Adding associations for new Z-Wave door lock 2
Sun11/01/2015 06:54:59 PM : Querying new Z-Wave door lock 2

 

Still the same limited functionality.

Thank you,
 

[stusviews]

The lock an PLM need to be fairly close, less that 6 feet, when including or very close to a Z-Wave repeater. You should also try Z-Wave > Tools > Heal Z-Wave Network.

[fryfrog]

The lock an PLM need to be fairly close, less that 6 feet, when including or very close to a Z-Wave repeater. You should also try Z-Wave > Tools > Heal Z-Wave Network.

 

Srsly, I had such a hassle with it after pre-installing all my Yale locks, my firm policy is to now unwrap a lock, put the batteries in and pair it sitting at the desk near my ISY and then leaving it for hours. So much easier than trying to re-locate the poor ISY to each lock.

[stusviews]

I do a similar procedure with each new Insteon device

[fryfrog]

I do a similar procedure with each new Insteon device

 

Even RF + Power line ones? Granted I have a *lot* of Insteon devices, but I've literally never had a problem getting any device to bond from anywhere in my house. Those are some of the few things I love most about Insteon.

[stusviews]

I factory reset and bench test every device. I don't have a difficulty adding devices installed anywhere, but bench testing and linking insures that the device is fully functioning before installing and/or replacing.

[Scyto]

I gave up with the ISY and the BE468, i see comms errors intermittently and never got it to include when it was anything other than right next to the ISY (i.e. going though a hop).  The vera goes through the same hops and works perfectly.  I gave up trying to figure it out and have the vera as the primary controller and the ISY as the secondary.  Whats awesome is by bedtime program on the ISY works just fine yo lock the locks at night, never had a failure.

 

Lock and unlock work perfectly, but gives me errors like request failed and timeout etc.  Same symptoms with two locks. I believe (though Michael probably doesn't agree ) that there is some fundamental issue (i am not saying whos issue it is - i have no idea, could be something bum about the firmware on the lock). 

 

( i note in some of my earlier posts i am a dumbass and said it was 469. its not it is a 468)

[lilyoyo1]

A friend of mine has 6 of those locks installed in his home without issue. ISY controls it like a charm. I know a few others that use multiples of that particular lock as well without problems. I would exclude once more and then include it with the lock close to the ISY. Test is in the area to see if you have comm issues before installing. 

[Scyto]

A friend of mine has 6 of those locks installed in his home without issue. ISY controls it like a charm. I know a few others that use multiples of that particular lock as well without problems. I would exclude once more and then include it with the lock close to the ISY. Test is in the area to see if you have comm issues before installing. 

Maybe, but if you look up in the thread (feb) where i tried multiple options.  The lock is fine when there are no hops.  When their are hops it is terrible.  I even unplugged all z-wave devices and just had two supposedly know good repeaters (the aeotec siren and the aeotec repeater) as the only z-wave devices in the house.  No joy.  I have a vast z-wave mesh in the house.  this is why i think it may be specific to specific versions of the lock (i bought the two locks at the same time).  Schlage support was useless.  Given i need the Vera to access the multistream features of many of my devices i am ok using that for everything advanced with the lock and the ISY doesa fine job of unlock/lock - at this time there is no more point in me excluding and re-including these for about the 30th time.  But good suggestion

[BamBamF16]

I don't now about prior versions but the gen5 stuff can be paired secure or unsecure. For my multi sensor had to press the activity button twice in one second to pair securely. Possible issue?

[fryfrog]

Maybe, but if you look up in the thread (feb) where i tried multiple options.  The lock is fine when there are no hops.  When their are hops it is terrible.  I even unplugged all z-wave devices and just had two supposedly know good repeaters (the aeotec siren and the aeotec repeater) as the only z-wave devices in the house.  No joy.  I have a vast z-wave mesh in the house.  this is why i think it may be specific to specific versions of the lock (i bought the two locks at the same time).  Schlage support was useless.  Given i need the Vera to access the multistream features of many of my devices i am ok using that for everything advanced with the lock and the ISY doesa fine job of unlock/lock - at this time there is no more point in me excluding and re-including these for about the 30th time.  But good suggestion

 

Did you do a zwave heal after including it near your ISY? It has to learn the new routes if you pair it close and then move it away. The Vera runs a heal every night, I'm pretty sure... so that might explain why it works there and not on your ISY (which needs you to run the heal manually).

 

I've got Schlage and Yale ZWave locks and they work fairly well for the most part, but my ZWave network is composed of only a few devices because I use Insteon primarily.

[Scyto]

great suggestion on the heal, no joy.  As I say unlock and lock work but error with 'not communicating' a subsequent query of the device then works perfectly.

If i had to gut check it i would say the device is not ready to respond while it is doing the unlock action and the ISY does no retries.  I.E. the 20 second wait the ISY does is not long enough, but that just a SWAG as don't really know whats going on!

 

This is sequence of lock / query / unlock / query - the errors manifested as comms errors - to be clear the lock worked perfectly for the lock/unlock and query (though this set of errors makes it impossible for me to program user codes from the ISY)

ZW027_1 SECMD 0   2015/11/24 12:23:37 Web user 5
ZW027_1 ERR 1     2015/11/24 12:23:56 System 5
ZW027_1           2015/11/24 12:23:56 System -2
ZW027_1 SECMD 0   2015/11/24 12:23:56 Web user -1
ZW027_1 ERR 0     2015/11/24 12:23:57 System 5
ZW027_1 ST Query  2015/11/24 12:24:08 Web user 5
ZW027_1 ST 0      2015/11/24 12:24:10 System 5
ZW027_1 BATLVL 79 2015/11/24 12:24:12 System 5
ZW027_1 SECMD 1   2015/11/24 12:24:14 Web user 5
ZW027_1 ERR 1     2015/11/24 12:24:33 System 5
ZW027_1           2015/11/24 12:24:33 System -2
ZW027_1 SECMD 1   2015/11/24 12:24:33 Web user -1
ZW027_1 ST Query  2015/11/24 12:24:39 Web user 5
ZW027_1 ERR 0     2015/11/24 12:24:41 System 5
ZW027_1 ST 100    2015/11/24 12:24:41 System 5

As an aside, i love using the new ISY portal to get event entries (if only cut and paste maintained formatting)

[fryfrog]

Are *you* triggering a query via program or manually? Or is "ZW027_1 ST Query  2015/11/24 12:24:08 Web user 5" just something that happens naturally?

If you're doing the first in some way, maybe you don't need to? My setup doesn't force any queries and works fine via status and control and the normal programming things. The lock reports it was unlocked via keypad and by what user code, no query needed.

 

If I *do* query (by hand, none of my programs do it), it is far less reliable.

[Scyto]

I am doing the lock / unlock and query manually in the ISY UI to prove if the device is functioning correctly.  No more.  However I get a weird TCP communications error on the unlock and a generic error on the lock (which makes no sense as there is no TCP involved AFAIK)  the UI errors are not logged.

 

As an example, here is one error - what the heck does DHCP have to do with anything...., sometimes i get just the cannot communicate and sometime i get with DHCP / TCP and other strange errors - if in ping the 

ISY at the same time as doing this there is no evidence that the ISY is dropping off the network or having general IP connectivity issues.  And to be clear i have NEVER had the lock fail to lock or unlock when told by the ISY- it is the reporting and querying that seems to be the issue.

[BamBamF16]

I had this same issue. Chalked it up to battery device that won't query correctly because it isn't awake all the time.

[stusviews]

All of my Schlage locks respond correctly to a Query (i.e., shows stat and battery level).

[Scyto]

To be clear query works just fine - never errors.

Just lock / unlock / pin code changes.

 

the new gen5 aeotec smart switch 6 did not fix this (i was hoping their newer repeater would help); the new switches are a nice bit of kit BTW.

[Michel Kohanim]

Hi Scyto,

 

Please note that for Schlage door locks, you cannot send rapid commands. They have a security feature which NACKs if the next event is less than 10 seconds before the last. So, does it work if you send commands (except for query) 10 seconds apart?

 

With kind regards,

Michel

[Scyto]

Hi Michael

 

I get comms error in the ISY UI on EVERY lock and unlock initiated via the ISY UI (never query) that indicated the ISY couldn't communicate with the lock.

The lock and unlock command work EVERY time (i.e. they lock locks/unlocks) - because of this i have ignore issue as i never actually really use the ISY UI for anything other than testing and my programs always succeed as do commands from mobilinc)

 

 

 

alex

[Michel Kohanim]

Hi Alex,

 

Understood. So I would think the issue is the door lock itself.

 

With kind regards,

Michel