My Schlage deadbolt (for a vacation rental) used to work just fine for years then stopped working properly a few days ago. I deleted it from Vera 3 running the latest UI7 and did a hard reset on the lock. It starts to pair and goes through getting the name and getting secure classes then gets stuck on getting the manufacturer. Same as before the hard reset. It shows up on the dashboard as a lock but it won’t poll and I’ve tried to configure node over and over. Any ideas before I use it on a shed as a regular manual programmable deadbolt.
Two things I would try if I had this problem:
-
Patience. Give the pairing a couple of hours before giving up on it. Be sure that the lock has fresh batteries though.
-
Try taking the lock out of the door, and moving it close to Vera, then try the pairing. It could be a marginal radio connection that is causing the problem. If it will not pair while sitting next to Vera, then time for a new one.
I’ve tried #1 no luck. I may try #2 when I’m back out there Saturday and post an outcome but I’m taking an extra lock I have on my back garage door at home just in case. I don’t really need the z-wave feature on that one.
So I took my perfectly good working deadbolt from my house to the condo and paired it with the Vera 3 and same thing. I tried reseting the z-wave chip and then reset the whole z-wave network and rebuilt it to no avail. So I figured it was that Vera unit that was messed up. I brought the lock back home and now it’s doing the same thing on my home unit. This all started after upgrading to 1.7.513. Now I’m at a loss. Maybe I can downgrade firmware and see if that fixes it.
Hi there,
I apologize for the trouble you’ve been having but downgrading the firmware will not solve the connectivity issues.Especially because you’ve tried to re-add it and it most likely also changed the node ID and not even a backup will restore it.
Make sure you are excluding the lock from Vera with the lock near the unit(5 feet max with new batteries in the lock). But try to use the exclusion procedure, don’t simply delete it from the interface.
If you have the lock on your interface with the error, press on “Delete” and when prompted, select “unpair”, and do the unpairing procedure on the lock(check the manual of the lock). This will also delete any residual settings from the lock and if the procedure was successful, it will also disappear from the dashboard. If it’s not getting detected during the exclusion procedure and it does not delete it from the dashboard, then either the lock is too far, or you are doing the wrong steps on the lock.
Then try to add it again, after it got deleted, and if it’s within 5 feet, it should get detected and not fail at getting the manufacturer or else.
If you are still having trouble don’t hesitate to contact tech support over the phone or email at support@getvera.com so we can troubleshoot the setup and see how we can identify the issue and resolve it.
USA Toll Free: +18669662272
International: +17024879770
Email: support@getvera.com
Web: support.getvera.com
Hours of Operation: Monday ? Friday 12:00am to 6:00pm Pacific Time
I just downgraded the firmware to 1.7.374 on both units and the lock works again. Then I upgraded back to 1.7.513 because that fixes an issue with the start and end time not showing correctly for door code scheduling. That whole issue probably wasted 6 hours of my time.
mcvjohnm,
I guess you were wrong about the firmware not being the issue since it fixed it on both after doing so. Had you read that I had even did a factory reset to the lock to no avail. It had nothing to do with unpairing or how far away the lock was. I had it sitting on top of vera at one point. It was fixed with the downgrade while one of the locks is 40 feet away. They were pairing just not configuring.
I have the exact same problem with the exact same circumstances. I guess I’ll try the downgrade/upgrade. Will report back the results.
-GT
Hmmm … where do I find the older firmware (1.7.374 for Vera 3)?
-GT
http://download.mios.com/rt3662_betafirmware/rt3662_Luup_ui7-1.7.374-en-mios.squashfs
Just copy and paste that into your manual upgrade area.
Thanks so much. Downgraded yesterday and the lock started to work fine again and had no issues for a whole day, so clearly the problem is related to the firmware (or upgrade process). I just upgraded now to the latest and it seems to now be working fine (no errors and can poll the device manually).
I’ve had the exact same problem since upgrading to the newest firmware. It was working beautifully until the upgrade, and then VERA tried to automatically add the devices. The lock kept showing as being paired, but it got hung up and failed when it tried to connect with the secure whatever. It was so frustrating! I tried for a week and finally got it working today (while still staying on the latest firmware.) I had to unpair my Schlage, then plug the VERA in near the lock (I plugged in both network AND outlet plug because I had 0 luck pairing without a network). Instead of following the instructions I found on the Wiki, I unpaired the lock on the interface. Then I pushed the plus sign on my VERAlite and then went to “Add a device” on the interface. After two tries it finally worked.
SOMEthing in this new firmware version is different when it comes to interfacing with devices. I had to start from scratch and this is the first firmware release that has given me any headaches.
Same here, none of my Schlage locks are working, -----> please wait - getting manufacturer
I am having the same issue with a new Vera Edge and a FE599 Lever Lock. I have version 1.7.1018 of the firmware. Should I try and downgrade? How do I get a previous version of the firmware for the Edge?
The problem just returned for me (after fixing it with the downgrade/upgrade). What seems to have triggered it this time was that I had to add back a dimmer switch that somehow lost its association to the zwave network. I added it back and them started a zwave repair to update the zwave routing. After that the schlage lock was failing again. Will try downgrade/upgrade again … PITA!
Edit: downgrade/upgrade fixed it again.
You might be having two different problems (not just the Vera Firmware). I have found my older Schlage Locks just don’t work correctly if they are not talking directly to my Vera. I don’t think the older Schlage’s report the need for a secure beaming route correctly, so when you did the network heal it probably added a node between your Vera and the lock making it not work right.
I would suggest manually managing the route for your Schlage locks so they talk directly to the Vera and don’t travel through other nodes. If that is not possible (lock is two far away) make sure you are only routing through nodes that support secure beaming, but for my older locks they just won’t work if there is any nodes between them and the Vera.
I don’t think this is a problem unique to Vera, I had the same issue with my Alarm.com z-wave model. If there were any nodes in route between the Lock and the Z-wave controller it would stop working or become incredibly flakey.
Hmmm, that’s an interesting theory. My Schlage lock is first-gen as I bought as soon as they came out and none of my other devices support secure beaming. However, if it is to do with another node inserting itself between Vera and the lock, why does downgrading to earlier firmware solve the problem? I wonder if it is because the older firmware is somehow making sure not to allow nodes between itself and the lock, while the newer firmware is no longer doing this. Prior to the new firmware my lock was very reliable … had no problems.
The Vera Firmware might also be bad, if you can’t pair the device it is not a routing problem as pairing events are never routed (that is why you have to be close to the Vera for pairing). But if you can pair it fine but then it doesn’t seem to work after that, I would check the routing table and manually manage it so the signal goes directly to and from the Vera.
I too have a bunch of Cooper Light switches that don’t support secure beaming, if one of them gets in the routing table… my lock will stop allowing me to add or edit user codes, and lock/unlock commands will usually have a huge delay if they work at all, and will report malfunctions from time to time. Fixing the routing table seems to fix the problem.
Did anyone ever found solution to this? I’m having the same exact issue with vera 3 latest firmware and 1st gen schlage fe599 lock. It get’s stuck during configuration on “Getting manufacturer” Downgrading the firmware to 1.7.374 solves the problem.
The older Vera firmware works because you can manually control the route, I don’t believe on the latest firmware you can do that (not sure).
To include on the latest firmware try putting the two devices directly next to each other. You need to prevent any other node from being involved.