I recently installed a Yale YRD220-ZW-619 Real Living Electronic Touch Screen Deadbolt with z-wave enabled of course. went through the simple setup I foundon the wiki. let the lock sit next to controller overnight after setup. but the dashboard always show the lock as Unlocked? even though its locked 90% of time due to it autiomatically locking itself after 30 seconds. I dont see how to change any of these options. Is this a firmware problem, if it might be can someone tell me hoe to find out the Yale lock firmware version. My Micasa Verde Lite is running the lastest release, no beta or anything. Im going to remove and re-add the device to see if that helps, I have also ordered a zwave “beaming” campatible lamp link hoping to better the lock signal through house, which does not seem to hop through the GE light switches in the wall between lock and controller. for the time being and until wife gets mad, I ran a 50ft ethernet cable on floor to front door to have controller sit next to lock during the re-add tonight… wish me luck, or give me some answers PLEASE… Thanks for your time, and any suggestions would help, I ran the searches on forum but just cant seem to find anything there, hopefully there is a known issue someone can inform me of…
Mine shows real time. does it show unlocked even after reloading? Try manually turning the lock while you watch the device online. I can see mine change over the cell network fairly quick I think maybe a range issue with lock and Vera try to have them about 4 or 5 feet apart and test reaction times I’m not sure how many devices you have but maybe need to update neighboring nodes I’m not sure how to do that, I’ve never had to try. I learned my devices in in a star patern starting with the closest device and working my way out my lock was the third or fourth one. Hope this helps and good luck
what firmware version are you using? the 1.5.408 has a problem in updating Yale Lock’s state. Contact MCV support to point you to a workaround firmware…
Im using the 1.5.408 firmware, just submitted ticket to support hopefully they get back to me soon
I just double checked mine and it is doing the same thing. I guess I haven’t looked at it that close since the last firmware upgrade. It still works fine but only shows the correct state when toggled remotely my scheduling and invalid pin notifications don’t seem to be working either ver.1.5.408
Well MCV support directed me to upgrade my firmware to a beta version 1.5.432. This seemed to work okay after the upgrade, removal and re-add the lock. But sadly After a few minutes it still reports the wrong status.
Is this problem with only the Yale lock or are other locks doing this as well if its only Yale ill call our sales rep and see what he says
is it consistently reporting the wrong status? some points to help in troubleshooting:
- how far is it from Vera? do you have nearby Z-wave devices with “beaming” support?
- do a “stress test” on the lock, do you get good results?
- check the neighbors list under “advanced” tab. does it report any neighbors?
Neighbors :1,2,3,4,5,6,7,8,10,11,12,13,14,15,17,
I too had a problem with my Yale Real Living Deadbolt reporting the correct status after firmware update 1.5.408 (MiCasaVerde tech support stated it was due to Yale changing their manufacturer ID) but my problem was fixed when they had me upgrade to beta firmware 1.5.420. I didn’t even realize there was a beta version 1.5.432 already.
[quote=“Ruetech, post:9, topic:173059”]@capjay
Neighbors :1,2,3,4,5,6,7,8,10,11,12,13,14,15,17,[/quote]
Appears that the lock can see its neighbors. can you verify that the list includes all nodes near the lock (ID 1 is Vera, the other IDs can be found under device/settings/ID).
if you go to the lock device / settings / click “stress test” does it respond well? if you click “poll now” does it update the gui with the correct status?
well, I have done the upgrade of the firmware originaly requested by MCV support, then removed/re-added lock as their next suggestion, I did a little research and found that having a Z-wave device with “Beaming” capibilities would help, I found the GE 45603 Z-Wave Technology Wireless Lighting Control Fluorescent Light & Appliance Module has this feature. I have added that to my little collections of devices, this info may help with suggestions, so heres what I got - 2 on/off GE switches right next to front door, which has the yale real living lock in it. the living room now has the GE lamp module with “Beaming” less than 6 feet from door. I also have a Dimmer z-wave switch in the bedroom on opposite side of house and 1 Aeon on/off energy monitoring switch in middle of house which is right next to the MC Vera Lite. except the MCV Lite spent the last 3 nights trying to pair with the lock, which it then sat on boxes within 6 inches of Yale lock. Wife not happen, with long cables running through house and boxes by front door, starting to loose her on this idea…
Now. the Lock is not reporting errors now and it works when used from the web interface. but still reports the wrong status. It always shows as unlocked. this I believe causes the iVera app to not send unlock commands to what it thinks is an unlocked door. Also the lock has not forgotten any of the previously set-up pins on the device. I can still use pins I set up on lock the first time I connected it to vera. Im going to let the system soak over night and give myself a break. then I think my next step it to factory default lock, and give the pairing another shot, with the added “Beaming” device. this is down right frustrating, every other device has been so easy, much easier than the Insteon install I helped a friend do.
which brings me to another question, I thought all Z-wave devices are repeators. now I hear this term “Beaming” and I feel Like I was lied to, devices repeat stuff, but they dont “Beam” it. Beam me outta here scotty…
jamminred:
You mentioned you were using the iVera app. Does the Yale lock report the correct status on the Vera UI? I was previously using iVera but switched to automator.app when iVera began giving me problems with my Yale lock status and my Foscam cameras. iVera has not been updated for well over a year (long before firmware 1.5.408 came out) but automator.app on the other hand is updated regularly and I believe is more compatible with Vera’s latest firmware updates.
If the Yale lock does not report the correct status under the Vera UI though, it may not have much to do with the iVera app.
[quote=“capjay, post:11, topic:173059”][quote=“Ruetech, post:9, topic:173059”]@capjay
Neighbors :1,2,3,4,5,6,7,8,10,11,12,13,14,15,17,[/quote]
Appears that the lock can see its neighbors. can you verify that the list includes all nodes near the lock (ID 1 is Vera, the other IDs can be found under device/settings/ID).
if you go to the lock device / settings / click “stress test” does it respond well? if you click “poll now” does it update the gui with the correct status?[/quote]
Yes, yes and yes honestly I’m not sure I even care, it auto relocks and sends a text if it fails it just doesn’t report current status and The only reason I know is because I read it had a problem on here and then started messing with it. I just did an update on my security panel that allows me to share user codes and disarm from the lock so maybe ill remove it from Vera and let my dmp system play with it for a while and see how it acts. It seems like this is a ui5 issue not Yale so I’m sure it will be fine. Maybe I can get it to report from my security panel to Vera. Thanks for the help
“beaming” is a bit different from repeating, only used for those security devices that send encrypted signals like locks (they have to be handled in a special way apparently), repeaters work with everything else.
Locks are different, because they are battery operated, yet you’d want to be able to communicate to the lock at any time. Compared to say a battery-operated sensor, which will typically report autonomously, either periodically or as an event occurs, without the need for the user to initiate communication.
Keeping the Z-Wave radio powered up all the time would drain the batteries quickly. So the battery-operated sensors are actually asleep most of the time, unless ‘there is something to say to the user’. But that doesn’t work for the case of locks, where ‘the user may have something to say to the lock’. So for those devices (locks are one example), a different technology is used to make it work without draining the batteries. That is beaming. The last node on the route to the device that is repeating the message, must support beaming.
Just out of curiosity if “beaming” is the issue why was it working before and not now?
IIUC, the firmware from MCV Tech Support helped getting the lock to work. But the OP has a remaining issue with status updates; which would be unaffected by beaming.
[quote=“agoodman82, post:13, topic:173059”]jamminred:
You mentioned you were using the iVera app. Does the Yale lock report the correct status on the Vera UI? I was previously using iVera but switched to automator.app when iVera began giving me problems with my Yale lock status and my Foscam cameras. iVera has not been updated for well over a year (long before firmware 1.5.408 came out) but automator.app on the other hand is updated regularly and I believe is more compatible with Vera’s latest firmware updates.
If the Yale lock does not report the correct status under the Vera UI though, it may not have much to do with the iVera app.[/quote]
yes, its also not reporting the proper status in the Vera UI, I can make changes to lock setting, I can pretty much do anything with lock on the Vera UI except have it report proper status, should be an easy fix right. I sure hope this bug can be fixed soon
well, thanks for the help with this guys, for now Im going to live with the wrong status being shown, the battery have finally stopped draining like crazy, the device is configurable and funtional (other than the status of it) from the UI. Things seemed to have settled, I can live with using a code instead of iVera app, its a sweet looking lock so Im keeping it. Just gonna wait very patiently for a good firware release or beta to help this device along.