I’ve been having trouble with my Schlage BE469NXCAM619 deadbolt and VeraLite running 1.5.622 (same issues on 1.5.408).
I am able to enroll the device without issue and it seems to work fine initially, but after a few hours I am unable to control the device or see the proper status (ie, unlocking the dead bolt isn’t reflected in the MiOS UI). Trying to lock or unlock results in “Cannot send command to node”, and doing a stress test shows successful pings but no successful polls.
If I unplug the battery from the Schlage, then plug it back in, and do “Configure node right now”, the lock returns to fully operational for the next few hours.
Has anyone seen this behavior, or have suggestions? This is my first time using Z-Wave; I also picked up a Z-Wave PIR motion sensor which has worked flawlessly so far as compared to the deadbolt.
Thanks in advance for any suggestions!
How far is vera from the lock. If you do a search on the forum you’ll find many posts related to your question. Do you have other zwave devices? Like light switches, plug in modules, etc? Your issue sounds like a distance issue. Battery operated devices like locks are very picky. Try moving your vera close to the lock and see if you are having the same issue. If all is working, you’ll need to add more devices around the lock. Again search the forum and you’ll find losts of information about this.
Garrett, thanks for your reply. I did search around and wasn’t able to find anyone who had this lock with flawless performance for a few hours and then nothing after that.
Knowing from searches that distance could be a problem, I had run an extension cord so that the Vera was sitting on the stairs about 15feet away from the lock with unobstructed line of sight. Even with such close proximity, I have the same issue - after a few hours, the lock stops responding to commands/polls. I’ve also tried placing the VeraLite on the carpet on the next floor up, directly over top the door/lock, and have the same issue.
Because of this, I didn’t think that distance was the issue, which is what led me to post here looking for assistance.
I can see on the Schlage site that there is mention of a firmware update that is (supposedly) only installable using their Nexia bridge - is this firmware update useful or able to be applied using the VeraLite?
It’s not the distance. If you did search you would’ve found a thread with something like 17 pages on this lock. The problem is the firmware in the lock. Schlage came out with a new firmware just for the vera. If you look for the version your lock has, it’s either inside the lock or on the sticker on the manual, I bet you have MAIN_5.6. You need 5.7.
You’ll have to send the lock back to Schlage to get the update. They will send you a new one, takes 21 days for some reason??, then you send back the old.
Ahh, perfect, thanks guys - I realize now I had copy and pasted a typo in the model number when searching so I was only finding general Schlage threads. Sorry for that and thanks again!
For anyone else looking for the thread, it’s over here: http://forum.micasaverde.com/index.php?topic=13334.0
[quote=“Frunple, post:4, topic:175794”]It’s not the distance. If you did search you would’ve found a thread with something like 17 pages on this lock. The problem is the firmware in the lock. Schlage came out with a new firmware just for the vera. If you look for the version your lock has, it’s either inside the lock or on the sticker on the manual, I bet you have MAIN_5.6. You need 5.7.
You’ll have to send the lock back to Schlage to get the update. They will send you a new one, takes 21 days for some reason??, then you send back the old.[/quote]
??? I was all set to be dismayed about sending my brand new just installed locks back. Now I look, and I have one with MAIN_5.6 and another with MAIN_5.7! However, they BOTH have the same issue. Or similar - in UI5, it reports errors “Failed at getting Version” and I am suspicious that it isn’t accurately reporting the status of the lock. I’m going to try re-pairing the lock, but this time waiting until the “add” light stops blinking (I think I read that some where). Is there NO way to flash the firmware without having a Nexia subscription? I don’t want to have to send the locks away, this is seeming like a worse and worse idea to have changed from conventional deadbolts - at least all I had to do then was get keys cut. 
Longshot421 - I’ll be honest, I struggled with the darned things for a while too, eventually getting locked out because the keypad stopped working after I had left the house.
Not wanting to deal with the many week process to get replacements, I returned them and picked up Yale YRD220 touchscreen locks for a little more money - they are much higher quality and extremely reliable. Absolutely no issues with them and I wish I would have just spent a little extra for them in the first place.
Regarding the firmware, the answer appears to be “no, you must have nexia”, but even then, you may not be able to get the right firmware. Ditch the Schlage junk while you can still get in the house to do so 
I stuggled enough just trying to find Z-wave locks in my area! I have 4 (3 x BE469NX CEN 619, 1 x BE469NX CAM 619), I only installed them a couple of days ago, I haven’t had many of the issues reported, but I am having problems with MCV reporting “Failed to get version” and not always reporting the correct status of the lock (it updates when I poll the lock, but then as it goes through the checks I get the “failed to get version” message again. Frustrating, I thought this was a tried and true technology, I should have read more about it, but you kind of don’t know what to read until you start getting the problems! The whole reason for this was to cope with the fact that the kids EITHER leave the doors unlocked all the time, or the reverse, they lock our cleaning service out. Can’t win for trying here.
Just so you know, you don’t actually “send” the locks back. They give you a replacement, then you return the old in the box that came.
Yeah, I know, but it is a little better than having to put in another lock waiting for replacements.
I still can’t believe it takes 21 days for the new ones to come! Should be over-nighted.
I haven’t had the locks in for long, but SO FAR the only issue I’m having is that I get the error “Failed at: Getting the version” message and I’m not sure if it’s accurately reporting the lock status. I can toggle the lock position from my iPhone or the MCV website without a problem. I have not yet tried to pair the locks “completely” (i.e. “+” the lock and wait until the light stops flashing before I add another lock), so maybe the fix is as basic as that for me, I’m not sure yet. However, I’m worried that I’ll end up with the non-functioning keypad issues that others have reported. If “all” I have to do is wait for Schlage to send me locks that I can swap out, while not perfect, I can live with that, at least I’m not stuck with having to put in other locks until I get replacements. sigh Why can’t stuff just work like it’s supposed right out of the box?
I did this, and from what I can tell, the issue is resolved! ;D I receive no error messages from the locks now and can control them with the app on my iPhone and with the UI5 web tool as well, all statuses reported accurately. NOt 100% on noitifcations, but as I posted in another post, I suspect this is just an issue with polling frequency.