So I got my hands on a Yale Real Living touch-screen lock with a Zigbee radio (I dont think its available on the market). After I got it, I saw that ST doesn’t support Zigbee locks…I went and purchased a Yale Real Living ZWave radio off of Amazon and popped it in there.
It recognized it as a ZWave Lock and could poll it, however no commands worked…i could not get any kind of status. There were no errors in the pairing, so wanted to see what was going on.
Probably unknown raw commands. Probably just need a smarty pants to make a new device type, the hard part is getting documentation from yale identifying the commands.
It’s a supported door lock (The zwave one) but not fully supported. You should be able to get it to lock and unlock remotely, but you may not have remote support for changing custom lock codes.
That said, issues with locks are almost always due to distance.
The first time you pair the lock, for security reasons, the hub has to be very very close to the lock. Typically about 6 inches. This is a requirement of the lock manufacturer, not SmartThings, to make sure the lock doesn’t get accidentally paired to the wrong controller.
After that, you can move the hub back to its usual position.
However, there can still be an issue with getting messages to and from the lock if you do not have a repeater that supports zwave “beaming” within about 15 feet of the lock.
When I first set up my doorlock I had problems similar to the ones you described. I was able to fix it just by swapping two plug-in modules in the room. One supported beaming and one did not. I needed to have the beaming one be the one closest to the door lock so that the messages would be held until the lock picked them up.
But again, support can help with all that.
Good luck! Mine worked very smoothly once I had the devices positioned appropriately.
I just wanted to not that this restriction is now removed. On Saturday, I installed 2 Yale Real Living Touchscreen Locks and they both got paired to my ST hub that was about 20 feet away without any issues.
Having said that, I’m not sure about the Zigbee/z-wave part as the one I bought was the z-wave version from Amazon.
If pairing at that distance worked, it may be convenient, but it’s a security fail on the part of SmartThings or Yale, it’s not supposed to work that way.
Must be Yale because there was no mention at all about the distance thing in the instructions manual
That’s interesting to know! I had no idea about this while I was doing it. It took me a whole 20 minutes to set up both locks and to get them going with the ST hub.
The Yale manual just says follow the instructions of the network controller (in this case, SmartThings) to include the device. But it’s zwave certified as a secure lock, so it should be using low power pairing. Weird.
ST says “within 10 feet” but if you’re having trouble they’ll usually say to try closer. 20 feet is really pushing it.
Very much so. I have it set up so that my kitchen-to-garage door unlocks when I arrive (using geofencing on my cell phone). I wouldn’t do that with the front door because it’s the main point of entry but for my kitchen door, you still need to open the garage door.
Hey djraje, I’m having the same issue after just installing a 220. I’m using ethayer’s app and everything “appears” fine except for one thing. When I use Live Logging in the debugger I see messages sent for refresh, code change, etc. But when I try to issue a lock/unlock no message are even sent so obviously I can’t expect the lock to function. Let me know if you find any solutions.