Ok, I managed to get it paired. Pain the butt to do so. Strongly recommend people not waste time bringing the Vera over and playing with the buttons on the back. Much easier to just take the lock off and bring it over to your computer and use “Method 2”.
Anyway, it paired ok but I do not get a green cog. It spins for quite a while and then says job failed. At this point most things are actually working on it. I’ve been able to add codes and to unlock, although it is frustrating because it takes so long spinning the cog (only to result in an error) everytime I make a change.
Here is the last bit of the log:
05/31/09 19:52:44.793 114 users_code 19.13 09-05-31 19:51:18 09-05-31 19:52:38 09-05-31 19:52:44 85.953990000 6.345130000 Successful Successfully got the response command 13 23 ZWaveDoorlock
05/31/09 19:54:35.768 115 cfg get #13 p1 09-05-31 19:52:44 09-05-31 19:52:44 09-05-31 19:54:35 110.822834000 110.796041000 Aborted Timed out waiting for the node to reply 13 23 ZWaveDoorlock
05/31/09 19:54:35.837 75 conf_jh#13 09-05-31 19:50:43 09-05-31 19:50:43 09-05-31 19:54:35 232.569132000 232.535127000 Aborted Failed at: Setting user configuration 13 23 ZWaveDoorlock
05/31/09 19:54:37.050 116 getnodedetails 2 09-05-31 19:54:35 09-05-31 19:54:35 09-05-31 19:54:37 1.188502000 1.165298000 Failed
05/31/09 19:54:37.071 85 conf_jh#2 09-05-31 19:50:52 09-05-31 19:54:35 09-05-31 19:54:37 225.54937000 1.225983000 Aborted Unable to get any information on node 2 12 ZWaveController
I moved it so that it is only about 10 feet from the door. I believe it was also happening even when I had it off the door and right beside Vera. Do the log entries suggest a communications problem?
My concern is that you tried to pair the lock once or twice before without success. Then you had success on another attempt.
Failed installs result in possible erroneous info.
In Zwave a device must be uninstalled and not just reinstalled.
What can happen is that you install 1 wall switch, then you try to add a lock which fails, then you add another light switch. It is possible that the light switch becomes the node of the lock. Thus the network is corrupted. The only way to solve this is to unistall all susspected devices( use the unistall node process) Reset the Zwave network then Reinstall all nodes
I personally would install the lock first. Check the log . should take a few minutes to go through all commands and the 19 user codes.
If the lock fails to communicate from the installed location then you need to purchase a module that supports the " Beam" to act as the last repeater in the network. The only one avail I know at retail is the schalge. You can get it at lowes.com
I had problems too until I did a factory reset on the lock and ran a USB extension cord from the Vera to the basement so it would be closer to the back door.
Perhaps a network heal will also help, maybe the Vera is trying to route through other nodes first before it tries to connect directly with the lock.
"Perhaps a network heal will also help… "
If the network is corrupted ony a uninstall of all devices and reset the network will solve the problem.
“maybe the Vera is trying to route through other nodes first before it tries to connect directly with the lock.”
Only a node that has “beam” technology can route to a device like the schlage door lock.
The device that has the "beam " needs to be the last device in the route as the other devices must just be always on.
Is Vera (or z-wave) smart enough to make sure the route to the lock is good, or do I have to worry that it might be trying to route via a node that doesn’t support “beam”?
That is a great question I don’t know exactly. I would think it would try.
This is a question for micasa. CJ???
This is why i would try the lock first before adding other devices. See if it will work.
Hopefully there will be other devices soon that will support the beam other than the light module.
[quote=“zmistro, post:6, topic:164522”]"Perhaps a network heal will also help… "
If the network is corrupted ony a uninstall of all devices and reset the network will solve the problem.[/quote]
Why do you believe “network healing” can’t repair corrupted network? I never tried it with Vera, but as far as I remember TE could do wonders on corrupted networks, and I suppose Vera does pretty much the same thing.
because the heal network will only rebuild routing tables. It cannot change faulty node information.
such as results from a improperly added or deleted node.
I can’t reference specific facts but I can tell you from my exact experience.
When I installed the lock, I migrated to the Vera as a primary to support the security class.
In doing so I reset every controller and physically reset every node so my network was built fresh.
I was not able to add the lock right successfully the first time so per wiki instructions I did a factory reset of the lock and it added just fine.
To my dismay, the door to which the lock is on was too far and I kept getting red cogs
I wired a 15ft USB extrender with the zwave dongle downstairs so it would be in line of sight with the lock. That fixed the problem.
But recently, my lock has been taking very long to activate scenes and report status. I reset the zwave chip soft and hard rebooted the router to know avail.
It was only after I did a network heal did things get back to normal
None of my devices moved other than the lock downstairs (and I think I did a heal after I moved it, but I forgot) , and it worked fine for a while. So I wonder how the routing tables get screwed up, or how a heal will make my lock work faster if the routing tables are fine?
I’m open to any lessons to help me understand my setup better.
Once lock is working, add remaining z-wave devices
I don’t know if it is relevant or related, but I’m also having trouble with some Intermatic controllers (I have twp table-top models and one handy remote). They are behaving somewhat the same as the lock in that they have a red cog, but still sort-of function (although some scenes don’t seem to have taken). I’ve also had no luck with a Cooper in-wall scene controller. It shows everything to be fine (green cog), but scenes do not fire from it. All my light dimmers & switches are behaving properly.
Delete the device.
Reconfig, but make sure you don’t make any configuration changes to the device after it’s initially configured.
Does the cog show up as green now?
Vera is giving me the red cog on several devices if I try to change it from the default configuration. (eg. battery level notification %, idle time, etc.)
(I don’t have the schlage lock yet)
I deleted the item (Method 2), then I did a factory reset on the lock, then I added it back again (Method 2). It works!
I’m suspecting that my original factory reset didn’t work. After I initially had trouble pairing it I thought I had successfully done a factory reset, but I noticed that the codes I had added were still there. I assumed that perhaps they weren’t wiped during factory reset, but reading the Schlage docs I see they said it does wipe all codes back to factory settings. After this reset I did lose all codes, so I think this may have been the problem all along.
That’s very good news. I thought it would be a simple door lock install too - half a day later I was very wrong.
Some other quick thoughts for you to ponder or help me with.
I actually moved my dongle to be within reach of both my front and back door. Still debating on getting another lock for the front door, finally got approval from the fashion police after she found how useful the back door lock was. I was hoping the Black&Decker lock would be out by now.
Scene Activation from the Lock is not as fast as I like, especially if you have more than one device in your scene. And it sometimes varies in activation time. The only way to fix that was a network heal. But I still would like to reduce overall time.
The FindVera servcie has been flaky. It seems to only text me 90% of the time with door events.
Vera also will not notify me if I create a “wrong code entered at the door” event.
[quote=“GT!, post:7, topic:164522”]Is Vera (or z-wave) smart enough to make sure the route to the lock is good, or do I have to worry that it might be trying to route via a node that doesn’t support “beam”?
-GT[/quote]
Right now there aren’t any devices that are supporting the secure classes and can re-route messages to the Door Lock.
So the communication between Vera and the Lock it is directly made. None of the actual devices will help to extend the rage up to the lock.
Best Home Automation shopping experience. Shop at Ezlo!