My Yale Real Living Deadbolt had been working flawlessly for the last few weeks, locking and unlocking remotely as well as reporting its correct status… until I upgraded my VeraLite to firmware version 1.5.408 the other day. Now in the Vera dashboard it shows a red light at the device (instead of the normal green), and gives an error underneath the device highlighted in red that says “Failed at: Getting the manufacturer”. I can still lock/unlock the lock remotely, but it now hangs at reporting the status, and has also reported the incorrect status (unlocked when it was actually locked). The same occurs when I try using my mobile iVera app. I tried the “configure node now” button in the device’s settings but I still have the error.
Any other Yale Real Living Deadbolt owners have any trouble with the lock after the upgraded firmware? Any ideas what I can do? Mcvflorin, have you heard of this issue? Thanks.
Yup! Me too! >:(
Spent hours reconfiguring my entire network only to find out there’s something wrong with the vera connection to the lock:
Symptoms:
[ul][li]PIN codes won’t trigger (http://forum.micasaverde.com/index.php/topic,8700.msg56961.html#msg56961)[/li]
[li]Lock response is significantly slower! Stress test: 1200ms? The nearby nodes (light switches) are 100ms. [/li]
[li]The status response is terrible! Now maybe more than 5-10 seconds after the lock has changed state. After which, it says “Polling”. Never saw this before. Probably because it was instantaneous before.[/li][/ul]
+1 for the delayed status response. Something is definitely not right. For me, the status updates were instantaneous before the upgrade, and now they are delayed, sometimes as much as 15-30 min.!
as for the stress test of 1200 ms, I think this is normal (I recall it was high before) encrypted communication and battery power contribute to this slowness in response.
I’m having the same problems. It’s really disappointing because I had told my parents that the alarm would already be disarmed after they successfully unlocked the door at the lock. (I run a scene based on which PIN is entered at the lock…
I tested it myself just to be sure and was shocked to see that this no longer worked. Things had been going well lately too…
[quote=“electnixon, post:6, topic:172051”]I’m having the same problems. It’s really disappointing because I had told my parents that the alarm would already be disarmed after they successfully unlocked the door at the lock. (I run a scene based on which PIN is entered at the lock…
I tested it myself just to be sure and was shocked to see that this no longer worked. Things had been going well lately too…[/quote]
Exactly! I had a similar thing set up that would turn the lights on in the entry if a code was entered at night. This no longer works. More importantly, the trigger for simply unlocking the door no longer works either!
I’m betting someone could provide a better config file for this lock and it would work, but at the moment, it’s simply a generic lock.
I’ve contacted tech support and one of Micasaverde’s techs is working with me on this. So far they gave me a beta firmware update to try, and while it did somewhat slightly improve the Yale deadbolt’s responsiveness, it is still not nearly as functional as it was before the firmware update, which I’ve relayed to MCV’s tech. They’re going to connect to my vera and investigate further. I’ll keep you guys posted. Vera has a lot of Yale owners and I think we just have to keep our voices heard until they fix the issue.
Nothing yet from tech support, I guess they’re still investigating.
For those of you that have had Yale deadbolts negatively affected by the firmware update, what method of checking the state of the lock was affected for you? Does the deadbolt still display it’s correct state in MiOS.com or are you using a 3rd party app? Using a beta firmware update they gave me to try, I’ve found that although much slower in polling the lock, MiOS.com (my dashboard) reports the correct status when I lock/unlock.
However, I had been using the iVera app to control all my z-wave devices. I still cannot get the correct status reported through iVera, which really defeats the purpose for me because I was only using the app to check my home’s status, not MiOS.com through a browser. Do you guys use another app like automator? I’m just wondering since iVera hasn’t been updated in so long, another app like automator might be a better fit for me now and might show the correct status with the patched firmware. It’s $15 so I wanted some feedback before I plunked more money down for something.
I guess we could always downgrade our firmware too?
Mine is not updating status (on Vera itself and MIOS site) except after a while (sometimes as much 30 min. or so). if your lock status is updated in MIOS, it sounds like something not right with the app your using (maybe compatibility issues with the new fw, try a different app just to be sure).
The .420 is the beta software MiCasaVerde tech support had me test in order to try to resolve my Yale Real Living deadbolt issues after the .408 update. I am happy to say that my Yale lock is back in action under the new .420 firmware, and correctly reports its current status. The .408 update broke the Yale lock’s reliability when using the iVera app on iPhone, but I’ve now changed over to automator.app and the lock functions perfectly under that.
I just installed the Yale Real Living Deadbolt and was promted to upgrade to 1.5.408.
I the PIN change messages say they transmit but I get a “Device failed to configure” message.
This is my first experience with micasaverde and the Yale lock and I’m not feeling very good about additional investment in this combination.
