Bumping this topic, because I just upgraded from a Vera Lite running UI5 to a VeraPlus running UI7.
Posted a bit more detail here…
http://forum.micasaverde.com/index.php/topic,37638.0.html
Am I correctly interpreting the responses here that excluding the lock, then re-including by bringing the lock next to my Vera unit, will solve the problem? Or am I just hosed because my Schlage lock is about 7-8 years old and it has old firmware itself?
So I thought I would try excluding/re-including my lock, which I just did by bringing the lock inside and setting it about 6 inches away from my VeraPlus unit. The inclusion process went fine. However, I’m getting the same behavior…stuck at “Please Wait! Getting the Manufacturer” and communication between the lock and Vera is virtually non-existent.
If I let it sit for a while, maybe 20/30 minutes, it seems to have exchanged some information because the lock state will eventually display correctly in the interface, and all of my PIN codes will show on the PIN code form (although I still can’t figure out how to get it to show the actual PINs instead of ****). But if I activate the lock through Vera, the response is either extremely slow, like 30-40 seconds before it locks or unlocks - or it just never responds at all. And then it starts the polling cycle again which eventually ends up at the annoying red message about …Getting the manufacturer.
I’m now fearing that this is indeed a problem with the age of my lock and it’s own firmware. I have logged a case with MCV, but I’m not hopeful. If anyone has any ideas on how to resolve this, assistance would be most appreciated.
VeraPlus has known issues with battery powered devices, hopefully it will get better with net update.
** UPDATE **
After spending some time on the phone with MCV support attempting to exclude/reset/include my Schlage lock, it became apparent that my 7-year old lock just wasn’t going to work with VeraPlus/UI7. MCV support sort of gave up telling me it’s the lock - I don’t necessarily hold that against them, but they couldn’t give me any reason, only suggesting that the zwave functionality in the lock had failed. That would be a HUGE coincidence, given it worked perfectly with my VeraLite up until the point I upgraded to VeraPlus.
In any event, I bit the bullet and purchased/installed a new lock (exact same model) today, and it works perfectly. So if anyone has an older lock and is still running VeraLite, be prepared for a possible failure if you move up to a VeraPlus.
[quote=“Sig, post:24, topic:186134”]** UPDATE **
After spending some time on the phone with MCV support attempting to exclude/reset/include my Schlage lock, it became apparent that my 7-year old lock just wasn’t going to work with VeraPlus/UI7. MCV support sort of gave up telling me it’s the lock - I don’t necessarily hold that against them, but they couldn’t give me any reason, only suggesting that the zwave functionality in the lock had failed. That would be a HUGE coincidence, given it worked perfectly with my VeraLite up until the point I upgraded to VeraPlus.
In any event, I bit the bullet and purchased/installed a new lock (exact same model) today, and it works perfectly. So if anyone has an older lock and is still running VeraLite, be prepared for a possible failure if you move up to a VeraPlus.[/quote]
Hi Sig link
Trying to narrow down the problem a bit.
Did you purchase the same EXACT lock or a completely different model. Was wondering if only the Z-wave daughter board needed to be updated for Z-wave plus compatibility?
Z
I purchased the exact same lock, the FE599. I wouldn’t be surprised if it was just a z-wave plus compatibility issue, but I had read somewhere else (possibly on this forum) that the zwave board in these locks was not upgradeable, so I assumed the old lock was a lost cause.
There are many version of the FE599 sold over the years. The original Z-wave FE559s Do not work with the latest firmware and the firmware on the lock cannot be updated, mine are the v1 version and the only controllers I have found they will work with are the Concord 4 z-wave control with Alarm.com (and only will work then if there are no-neighbors talking between them, I only have my Locks and Thermostats on that z-wave mesh, all my lights are on the Vera), and Nexia Bridge (which would make sense because they were designed for the Nexia Bridge). They do work with Vera on older Vera firmware but not on the newer “self heal” version of the UI7 firmware.
Newer version of the FE599 do have updatable firmware but they can only be updated if you have a Nexia Bridge (which requires a monthly fee, however, if you buya Nexia Bridge you get a month free and can then cancel which would allow you to update the firmware, assuming you have a newer version of the locks and not ancient ones like mine, you might be able to get your locks working if you buy a Nexia Bridge and update the lock firmware, bad news is you don’t know if you have updatable firmware version of the locks until you try it!).
the FE599 is not a z-wave plus device, and firmware alone won’t make it z-wave plus compatible but z-wave plus isn’t required to get it work. The latest versions of the FE599 do seem to work with the Vera Plus. So it is really just going to depend on the age of your Z-wave locks. If you have really old versions they are only going to work on UI5 or older version of UI7 They will not work with Vera Plus since it comes by default with the self healing firmware that doesn’t work with the older locks.
Hi, wondering if anyone can help me. I have brand new (about 3 months old) FE469NX lock & the new Mi Casa Verde VeraLite controller. It worked fine for about a month but now Im having this issue too ??? any advice would be great
Situations like what you described often happen after something occurs to the Z-Wave transmission. Have you added any mirrors, new appliances, duct work, 900Mhz devices, electronic dog fence… All of these can cause transmission issues. Adding additional devices that are AC/high powered like a lamp module will act as a repeater for the lock signal and should solve your issue unless there is a new 900Mhz device in your home. You could also try moving your VeraLite closer to your lock and that may do the trick as well.
Hi Mark
Bought 3 Leviton Outlet Outlet modules to do exactly what you recommended.
How close to the lock? Right next to it? Same room? I want to include these in my mesh network to help improve reliability of my Schlage locks In an out building. I’ve watched your video and enjoyed all of them but could you explain how to exclude the Schlage lock in ui7 before I include them after installing the wall modules. I bought a hundred foot ethernet cable to bring my Vera closer to the locks at the outbuilding or I can plug Vera in closer to it and use the buttons on the Vera ui7 module. Also I have three locks I’ll be reincluding should I start with the lock closest to my Vera and work my way to the outbuilding? Thanks
[quote=“reiserx, post:3, topic:186134”]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.[/quote]I had an issue when doing this with a kwikset lock. I just excluded, then included. If that doesn’t work, call tech support. They are the best although sometimes hard to understand.
I decided to see if anything new had posted on the board regarding the same issue with my Schlage FE599–that hasn’t worked with my VeraLite for ~2yrs. After reading the post by Shallowearth, I thought I’d try rolling my firmware back to 1.7.374. IT WORKED!!! I’ve periodically tried to unpair/pair and have spent countless hours trying to get this work. If you’re having this same problem…roll it back. All of my other outlets, switches, thermostats, etc. work fine with the earlier firmware. As a programmer and systems integrator in the large commercial and industrial industry, I’m confidently calling this is a bug.
For ease…here’s the link to paste into your Settings/Firmware, under Advanced as provided by [b]reiserx[b]:
http://download.mios.com/rt3662_betafirmware/rt3662_Luup_ui7-1.7.374-en-mios.squashfs
I hope MCV addresses this in future releases. Since I’ve rolled back, every time you refresh or login or sneeze, it bumps you over to Settings/Firmware/Upgrade page and lets you know there’s an update. Fortunately, I rarely use the dashboard and run everything from my phone but, it’s been annoying as I test my lock. For the past few hours, I’ve kept an eye on the dashboard for the infamous “Please wait! Getting the manufacturer”, added it to my HomeWave app, and have cycled the lock countless times (from dashboard and app)–no issues in 3+ hrs. Also, adding/deleting PIN codes works as well. Although, you have to back out/in to refresh added/deleted PINs. Don’t refresh the page or you’ll be forced over to your settings page and reminded that there’s a newer firmware.
MCV–If you’re not going to address this bug (2+ yrs), adding a feature to opt out of firmware updates would be nice…some of us don’t need reminded there’s a new release every time we login. Or, maybe, you could give the option to enable/disable the self-healing and allow manual routing in future releases. I (and probably the majority of users ???) don’t want to replace functional devices whenever new features arise. Just my two cents… ;D
Migrating my locks back to the Vera I encountered the same issue, the next firmware release has a fix relevant to door locks, I wonder if this is what broke it:
2 year laters I am having this issue lol. I have rolled back to every firmware in 2017 no luck…going to try this one next
Best Home Automation shopping experience. Shop at Ezlo!
© 2024 Ezlo Innovation, All Rights Reserved. Terms of Use | Privacy Policy | Forum Rules