I am trying to get my Vera to work with the lock and have tried everything. I have even gone to the extent reset and cleared the entire network so I would only be working on the lock. I have reset the lock, and excluded and included using both the red/black button method 1 and the web interface method 2.
I always end up with the same result, the device is added but keeps the red cog.
I have moved Vera right next to the lock so range should not be an issue. I don’t know what else to do. I said to myself, “why can’t things just work.” Then I remembered the video of Vera before I bought it that said, “It just works!” Now I am .
I could never get method 1 to work (probably fat-finger syndrome). Doing a factory reset on the lock and then doing method 2 with the lock removed and right beside my PX & Vera worked. Until I did the factory reset on the lock I kept getting the red cog. In my case making absolutely sure the lock had properly factory reset was the key. I would suggest always doing a factory reset if you get a failed/pairing and red cog.
Don’t know if this will help, but it’s all I’ve got … good luck.
NOTE:
1) You need a Zwave dongle that has the security class built in. In Vera's setup page go to Setup -> Devices -> Z-Wave options, and look at the 'Version'. If the version is 2.40 your dongle does not have the security class implemented. Send a support request at micasaverde.com, support, with your serial number, name, address and email. We will send you a replacement dongle.
Ok. Please go to Advanced, Logs, and check Verbose Logging. Then, since it sounds like you can bring the lock close to Vera while still leaving Vera connected to the internet, try the pair sequence again please. After it fails, go to Advanced, Tech Support and fill out a trouble ticket checking the option to send logs.
All, thanks for your comments. I have done the factory resets and upgraded most everything. I have not specifically checked the firmware of the dongle though.
MiCasaVerde, thanks for these instructions. I am going to be covered up this week but I will try this on Thursday or Friday when I can unplug everything and take it over to the lock again.
jajojeeper, is it a steady blink once per second when power is first applied? Or a ‘double blink’ that comes on after 30-60 seconds? If it’s the former, this means the firmware image is corrupted, which means the power was cycled on Vera while it was in the middle of doing a firmware upgrade, and Vera will not boot without either (a) we send you a replacement, or (b) you follow the firmware flash steps in the wiki. Hopefully it’s the latter double blink, which just means Vera is working fine, but couldn’t get an IP address and internet connection on the WAN port. Just check your connections in that case.
I just looked at the updated Wiki and it states that if i have a dongle version says 2.40, I have the wrong one and it must be replaced for the lock to work.
I have version 2.40 L:1
Is this the correct one or do I have an old version. I sure hope this is not the case because my Vera the shipper forgot to pack one in my box and I had to call to have one sent. I would be sorely disappointed if I spent hours and hours working on this and because I had been given an outdated dongle.
My turn:
Just this morning, my otherwise working Schlage deadbolt began displaying a red cog in Vera’s Dashboard (later observed a spinning blue cog for several minutes, followed by the red cog again).
Yet the lock functions perfectly, initiates a scene when unlocked, etc., and its status is correctly updated in Vera.
Any clues what may have happened? No configuration changes (that I know of!) for many days now, and I’ve remained at firmware .899 (and dongle as shown in my Sig, below) for a while.
[quote=“LibraSun, post:17, topic:164581”]My turn:
Just this morning, my otherwise working Schlage deadbolt began displaying a red cog in Vera’s Dashboard (later observed a spinning blue cog for several minutes, followed by the red cog again).
Yet the lock functions perfectly, initiates a scene when unlocked, etc., and its status is correctly updated in Vera.
Any clues what may have happened? No configuration changes (that I know of!) for many days now, and I’ve remained at firmware .899 (and dongle as shown in my Sig, below) for a while.[/quote]
User error? Could not possibly be anything related to Vera.
Sorry just kidding you a bit. Seems there are a plethora of new problems between dongle and people moving to 0.899+ LUA firmware. Wish I could provide some insight.
Chimpware, you may be right in a sense … I haven’t left the house for a while; maybe Vera’s trying to say, “Go enjoy the nice outside!”
Thanks for the guffaw. I’ll monitor this issue at least until the next firmware is official.
We’ve seen this a lot. What happens is that during the configuration process Vera interrogates the lock a lot to find out all the existing user codes. For some reason there’s actually no efficient way to do this in Z-Wave without pulling each and every user code individually, which is why it takes so long. Z-wave, being wireless, is very susceptible to interference, and sometimes there’s a stronger signal than others. Locking/unlocking is pretty straightforward; you only need a good signal for a couple seconds to get that command through. But to do all the user code requests in the configure involves a lot more traffic back and forth, and if the lock is on the edge of the z-wave radio range, it can be that we can’t get through all the user code requests. Many users have reported this and said it’s related to 899. But, so far, every time that we’ve actually gone in and researched it, it hasn’t been at all related to 899 or Luup–it’s just signal strength. Installing a Schlage RP200 lamp module close to the lock has, so far, solved this problem in every case because it allows the mesh networking of Z-Wave to work. If there’s an RP200 near the Schlage lock, the lock can be 100’ away from Vera and the message still comes through because of the mesh networking. Without an RP200, Vera has to be in direct range of the lock, and if it’s more than 20-30’, it becomes if-y. The range on the Schlage lock is much less than on other Z-Wave devices because the antenna is inside that metal housing. But with an RP200 nearby, the lock’s signal only needs to make it to the RP200, and from there it will bounce around all your other z-wave nodes until it gets back to Vera.
.