Zwave ver 3.2, Firmware 1.1.1245
I’ve done the factory rest(s), changed the batteries, excluded… I can always seem to get the device added, but it does not configure.
I’ve got a good mesh network right up to and including the door/lock area.
The message under the device says “Failed at: getting the name” and it does not configure.
Does anybody have a suggestion at this point. Excluded, Rest, Included several times now, and I’m not sure what to try next.
How far away is the Lock form the Vera2? Try moving the Vera2 as close as possible to the lock when adding/configuring the lock. The lock and the Vera2 need to be close for the security configuration - once the lock is completely added you can move the Vera back to it’s normal location 8)
I’ve been taking the Vera2 to the lock on battery. I exclude (zwave light acts as it should) and still take it back and plug into Ethernet and look to make sure its gone. Do same when including, and it shows the device. I do the heal w/stress and it comes back as not configured. I leave it powered up on the battery the whole time - there are no power downs during the process.
It is 3 ft away while pairing, but its about 50 feet away, in the mesh, when plugged back into the network and I proceed to heal.
Z-Wave Locks go through a 2-Step during pairing or being added to the network - 1 all the normal information then 2 all the Security information for the Lock - If you have a long ethernet cable leave the Vera near the Lock until it is completely added.
Thanks kaldoon. I just took the lock to Vera.
Just curious. When I took the Vera to the lock (on battery) I left it there for about 20 min before taking it back and plugging it in. It never got the information it needed in that 2nd step. Is there ANY way to do that without having the Vera plugged in to the network??
I noticed step 2 only added about a few mins to the setup, but it never took 'til I brought it to the Vera and did it dashboard style. Just trying to understand what is happening.
Thanks again kaldoon!
Well, I took the lock back to the door, tested it over my cell phone and it worked fine serveral times. I went back to the dashboard and ran a new heal w/stress since the lock was now in its final resting place. Lost it. Now shows as not configured.
Once again… any ideas?
(Modify)
Ok, beaming??? Guess I need to go find Scotty and install something that will beam my signal to the Vera? Guess I’ll see if I have a Leviton VRP03 in the last few I bought recently, or just buy a GE Lamp Module and put it near my lock. Do I just need one near the lock and that will be ok, if it is in the mesh? Or, do I need a couple that support beaming in a direct chain to Vera?
When you do a heal, there is an option to reconfigure devices when done. It is checked by default. If your Vera is far, the reconfiguration can fail. At least it does for me. So, when doing a heal, uncheck the reconfigure button first and see if that resolves your issue.
The Schlage on the back door (furthest from Vera) gets a “Failed at getting name” error every time i do a heal (which I’ve stopped doing because it breaks way more than it fixes) and also when I change the batteries in it. I used to panic about it but I’ve learned that Vera just picks it up after a couple of days, I have no idea why but I make a point of using the lock more than I normally would and it just…fixes itself.
If anybody cares. I bought 3 GE/Jasco/Schlagelink style lamp/on-off modules (a variety) that all support ‘beaming’. The Schlage lock is 1 1/2 flights down, and about 45 feet from the utility room (so just 1 wall once upstairs on main level), were Vera is located. One module is about 4 feet around the corner from the door, another is directly above the first on the main floor, the third is about 33 feet from the second (line of sight), which makes it about 10 feet from Vera.
The chain is quite a bit shorter in between modules than I ever needed to attain a strong mesh network. You can move one of these by only a few feet, and the Schlage will fail to configure at all during a ‘stress heal’. I tried about every range and combination - very picky.
What I ended up with is very strong. Configs with 4 stars consistently, reports all notifications on open/close of bolt instantly. Haven’t done much else with it yet.
This is my home ‘play’ system, so I don’t have to shoot myself at the vacation property. If anybody wants me to try something for them, let me know.
And, If I’m just missing something here, and made some bad assumtions on what is working (or how), please let me know.
Just curious: still on .1245 / 3.20, right? Do you have MiOS routing enabled? ([tt]Z-wave device > Options[/tt])
I am running on .1245 and 3.2 now w/miOS routing enabled. When I tried it w/o MiOS routing, always seemed to get more ‘stars’ and was just more consistent through multiple ‘stress heals’. I ‘can’ loose config, or get down to 1 star with miOS config enabled, but most of the time it is fine if I just quit messing with it.
I’m always at .1245. So far 3.2 w/miOS routing - least stable, least consistent, can just report loss of config if you keep ‘stress healing’. Works fine if you leave it alone, but don’t feel real confident with it. Won’t be happening at the vacation home.
3.2 without miOS routing - more stable than with, more consistent, never lost configuration of lock or lamp modules, can loose/gain stars w/ multiple ‘stress w/heal’
2.78 (forget miOS routing) 5 stars on everything but lock which stays at 4. Nothing (rarely) changes with multiple ‘stress heals’ Seems most solid, have most confidence in.
I don’t dig into any advanced numbers, etc., not that much of a tester, but the vacation home is .1245 and 2.78 and… think it’s going to stay that way unless I learn something new. Maybe the little wizard and its stars and ‘no config’ signs is fibbing, but that’s all I’m looking at.
I do start from scratch when going from 2.78 to 3.2 and back again so I think I’ll do the easy back to 2.78 and call it a day? Any suggestions?