Yale real living keyless deadbolt displays incorrect status

Got it, thanks!

Wondering if I should have bought the august pro instead…

Well, I don’t think that helped. I had the ST hub about 1.5 feet away from the lock when I had it join the network and it is still that close.

But it, again, keeps reporting itself as unlocked even when it is clearly locked.

Yale is an excellent lock. I think you may just have a bad z-wave chip or a bad lock, their customer service is great!.

Are you sure you’ve got it installed the right way. One user installed the lock in reverse (upside down) while another user had an issue with the direction (left door or right door) (you can change the direction of the lock I think, see your manual). So every time it was locked it reported unlocked and when it was unlocked it reported locked.

If that’s what you’re seeing then it may be your settings.

I think it is pretty hard to install upside-down since they numbers would look wrong… My door opens right to left. It appears to be configured properly as it is right-side up with the deadbolt moving to the right.

I started working with Yale support, but they were pointing the finger at the ST hub, and suggesting I reset it and update firmware etc…

I’ve removed it, but old dumb deadbolt on. Waiting for new August. One thing I like about the august design is that it seems like their app is a better design (the twist unlock is just goofy IMHO).

Oh, I think my lock does “handing” when it is first installed. It basically tries to lock/unlock to determine if it is right/left handed. that part was done.

1 Like

Hi, I get the following error message when I use the code. Is there something that needs to be updated?
Any help is highly appreciated.

“No signature of method: script_app_metadata_546a016c_f039_416a_9c1f_a96c2e8d2303.metadata() is applicable for argument types: (script_app_metadata_546a016c_f039_416a_9c1f_a96c2e8d2303$_run_closure1) values: [script_app_metadata_546a016c_f039_416a_9c1f_a96c2e8d2303$_run_closure1@5cc72db5] Possible solutions: getMetadata(), getState(), setState(java.lang.Object), metaClass(groovy.lang.Closure)”


You’re copying and pasting the code as a smartapp, not a DTH (wrong section of the IDE).


Any donation for support is appreciated!


I would check your device handler and ensure you are using a custom one to start with. RBOY is worth the money and works well. Sometimes pairing sets up some wonky sh*t. Mine original shows up as a thing but even the standard lock device handler gave me fits. I also would use live logging in smartthing and see what it pulls. You can also try to do the simulator and see what its doing.

Thanks that helped.
Now when it does a poll at the end of the hour, the status is again displaying as unlocked in ST.

See my previous post.

If anyone is able to send me the rboy code for the yale locks to test out i
would love to see if it fixes my problems before i decide to shell out the
cash for it…


Davis Solomon Darvish Awesome Scientist Guy
[image: photo] Phone: 310.300.1337
Fax: 707.221.7039
Email: ddarvish@gmail.com
Website: DavisDarvish.com
Wiseintro: wiseintro.co/davisdarvish
http://us.linkedin.com/in/davisdarvish http://twitter.com/davisdarvish
IMPORTANT: The contents of this email and any attachments are confidential.
They are intended for the named recipient(s) only. If you have received
this email by mistake, please notify the sender immediately and do not
disclose the contents to anyone or make copies thereof.

Hi, just as a word of advice, a developer’s code with a copyright cannot be shared as he/she is entitled for royalties. What you’re asking is not only inappropriate but illegal.

To send you the code would be a violation of the Rboys license and someone who would do it could be prosecuted to the full extent of the law.

SmartThings is very sensitive to any copyright violation under its platform…I’ve personally asked SmartThings to remove code from developers who were not respecting my copyrights and the ST people have been very swift to remove the faulty code.


Ditto here.

Another thing to try is to run a z-wave repair several times and try to restart your ST hub. You may have a bad z-wave mesh at your home. Look for instructions on how to do a repair in the ST community forum.

Good luck.

Oh yeah, for some reason the Z-wave n/w repair was failing (unable to update mesh, issues with route) on a device that was never on the network. Got rid of the device (manually created a dummy device with same ID and force removed it) and now the Repair finishes successfully. Issue is resolved. Lock remains in Locked status!
Thanks for the tip!

Dang! I jumped the gun, its back to “unlocked” status now.:confused:

I use Rboy code and it works fine for my 5 YDR446. Noone can send code as that is illegal. If your lock is not close to smart things hub then you SHOULD have some kind of repeater (zwave plus electric outlet from ge is good) within 15 feet of the lock to make sure the lock statuses get sent as well as the lock opening/closing.

I also use the RBoy Lock Mgmt SmartApp with the Universal Z-Wave Device Handler.

I have two Yale YRD120s (T1L) that are approximately 30 to 35 feet away from the ST Hub. I have no Z-Wave repeaters in between and I have never had an issue with either lock dropping or false reporting. The only time I ever had an issue is if the lock jams (it will send notification) and doesn’t fully extend, it will report a few minutes later that the lock is unlocked, but that was a user issue to resolve the spacing problem.

Additional features allow me to program codes, setup a temp code that expires, enable / disable keypad functionality, audio, auto lock, and more.

One of two products I have paid additional monies for running in my SmartThings environment and worth every penny.

1 Like

You originally posted this issue in June of 2014 and you are still having an issue at the end of 2017? Surely you could have saved up $35 bucks to “shell out” in that period of time instead of trying to get someone to give you a copy of the code.

And posting every url, website, phone number and feed about yourself, hmmmmm.

C’mon Man!

1 Like

It appears that my network module is not compatible with ST. Its al ATT one and thats why its not displaying the correct status.
“You need to get a different zwave module with US2.0 printed on it. The part number of the module you need is AYR200-ZWV-USA.”