Schlage Dead Bolt - "failed at getting name" msg

Community Playground General Discussions
1

Quick Question - I installed a Schlage Dead Bolt last weekend and was working fine. Yesterday i installed several lamp switches and completed a stress test. The results came back and now the Dead Bolt is showing “failed at getting name”.

I’m new to this and can’t seem to figure out why? I also have a Schlage Level Lock and it is working fine.

Any advise would be very much appreciated.

thanks.

2

We are going to have to make a few assumptions here.

You did not do a configure node?

You did not run a heal network with configure nodes?

A stress test would not unconfigure your lock but obviously would stress it, I assume you checked the batteries? Weak batteries will reduce the range.

There were reports recently of devices becoming unconfigured so I have to assume you are running 1.1.1245?

Let us know.

JOD.

3

I will add a data point to this. Running 1.1.1047. When I switched from UI2 to UI4, I got/ am getting the same message as Tsscott on that unit only. Have tried configuring, healing. Nothing seems to work. I know my battery is around 65%, but its literally 4 feet from a Leviton Zwave switch, 10 ft from another, and 15 feet from another Schlage.

Does it make any sense to exclude and then re-include? What happens to the built-in codes?

4

Leviton switches today do not support the beaming technology used in the Locks. The new VRC0P-1LW http://www.smarthome-products.com/p-802-vizia-rf-vrc0p-1lw-plug-in-serial-interface-module-rs232-ascii-interface.aspx supports the beaming technology and the VRP03-1LW Dimmer Module which is due out somtime in June will be the first Leviton Z-Wave device 8)

5

@ballroller,
The biggest problem you have is that all your devices are trying to communicate directly with Vera regardless of any beaming devices you may or may not have. Try taking Vera closer to the lock to configure it. Or better yet, upgrade your FW and utilize the heal network function, it does not work in .1047

Personally I would not exclude to include.

JOD.

6

Interesting though that the upgrade to .1047 (@ballroller) and adding devices (@tscott) seems to have broken communications with a lock that was functional before those changes.

As @JOD said, get Vera closer to the lock, if able, and see if that fixes things, with .1245, so routing works.

7

A couple of points.

@kaldoon Isn’t Z-wave Z-wave? What is beaming technology? Now I’m completely confused that one Z-wave product can’t communicate with othe Z-wave products? What am I missing?

@JOD I upgraded to 1.1.1183 last night and have the same issues. I am going to move Vera right after this post and see if that makes a difference.

@oTi@ Is .1245 stable enough to upgrade to yet?

@tscott- I didn’t mean to hijack your thread- I can start another if you prefer.

edit: it’s going to be a bit before moving Vera- I had left my battery pack to “on” and it’s dead…

8

[quote=“ballroller, post:7, topic:168271”]A couple of points.

@kaldoon Isn’t Z-wave Z-wave? What is beaming technology? Now I’m completely confused that one Z-wave product can’t communicate with othe Z-wave products? What am I missing?

@JOD I upgraded to 1.1.1183 last night and have the same issues. I am going to move Vera right after this post and see if that makes a difference.

@oTi@ Is .1245 stable enough to upgrade to yet?

@tscott- I didn’t mean to hijack your thread- I can start another if you prefer.

edit: it’s going to be a bit before moving Vera- I had left my battery pack to “on” and it’s dead…[/quote]
@ballroller,
You mentioned you have Leviton switches near your lock. Typical advice is to place a beaming Z-Wave device near your lock to see if communications improve. But the Leviton’s don’t necessarily support beaming, so this wouldn’t help (hence @kaldoon’s remark). But perhaps your statement was just to point out that other devices near the lock work fine? (Beaming is a feature that was added to Z-Wave to help relay messages to battery operated devices, to extend battery life. Cheapest way is to have one of the GE plug-in modules near your lock.)

My guess is that @JOD meant for you to upgrade to .1245 and Z-Wave 3.20, as anything prior will have the Z-Wave bug where the routing table always says a device can be reached directly. I just meant to second that advice. But of course the migration to .1245 / 3.20 could present other issues. Personally, I’m happy with .1245 (and I have migrated; never done a Z-Wave Reset.). So perhaps try moving closer first (so we can be sure Vera can talk to the lock directly) and see if that helps. If you decide to upgrade, make sure to have backups.

9
Or better yet, upgrade your FW and utilize the heal network function
You have to run the heal network to set the routes. If not, everything will stay at hop 1. I've been running 1245 since the announcement with no issues, I did not make the switch to 3.2 as I'm running the Aeon dongle but the heal network works regardless and I can see my locks are at hop 2 (routed through a T-stat) by using ThinkEssentials.

3.2 gives you a different routing algorithm created by MCV which you will see as Edge Node in the heal report.

I’m VERY happy with this RC.

JOD.

10

Update.

I did a heal network- no change to the failure error.

Took Vera and put it within 8 feet of the Schlage- hit a couple of pin codes to wake it up. Still seeing a failure error.

I am going to change the batteries although I know they are good…

11

Batteries changed.

Failed at getting secured classes.

Why did this work beautifully with UI2 and not with UI4?? Nothing has changed as to switches/motions/locks, or Vera’s location.

12

After reading the .1245 beta thread and the issues that a lot of folks have, I am a bit ambivalent to do that upgrade until it’s stable. You have a much higher command of the software than many of us. While I like to experiment, I really like the way that my system is working-except for that one Schlage lock-and don’t want to flip the boat.

[quote=“JOD, post:9, topic:168271”]

Or better yet, upgrade your FW and utilize the heal network function

You have to run the heal network to set the routes. If not, everything will stay at hop 1.
I’ve been running 1245 since the announcement with no issues, I did not make the switch to 3.2 as I’m running the Aeon dongle but the heal network works regardless and I can see my locks are at hop 2 (routed through a T-stat) by using ThinkEssentials.

3.2 gives you a different routing algorithm created by MCV which you will see as Edge Node in the heal report.

I’m VERY happy with this RC.

JOD.[/quote]

13

All, thanks for the help. I ended up removing the locks and resetting my z -wave network. Reinstalling all my devices and it’s all working now. I think when i first included the lock, I didn’t give it enough time to properly set. It seems to be working perfectly now.

Thanks

14

When you exclude the lock and then re-include it, does it keep the codes that you created before the exclusion? I know the physical lock will do so, but what does the software show?

Thanks.

[quote=“tscott, post:13, topic:168271”]All, thanks for the help. I ended up removing the locks and resetting my z -wave network. Reinstalling all my devices and it’s all working now. I think when i first included the lock, I didn’t give it enough time to properly set. It seems to be working perfectly now.

Thanks[/quote]

15

I had to exclude and then do a lock reset. All seems good now.

16

Sorry to be a pain, but what do you mean by a “lock reset”?

17

Hi –

My experience is that doing an exclude and re-include the lock looses ALL the pin codes. I have had to re-type the pin codes 5 times for my schlage lock.

Lately when doing a network repair my Schlage deadbolt looses the pin numbers. This only happens to those pins that have a schedule set. Has anyone else experienced this problem?

 Don
18

And an update to my problem- MCV was most helpful in getting my Schlage to be configured again. We tried a few things over the email, and a phone call solved the problem. It was an include/exclude issue and distance from the Vera (even using the GE Lamp switches ver 2.0a).

19

I just did so. The lock will remember pin codes #1 & #2, but lose anything after that. I had to put back my #3 & #4 codes.