I have installed this lock multiple times and it never gets past initializing. And it never says Yale lock or anything. The hub is a couple of rooms away. Could that be it? Having to remove the lock and take it to where the hub is seems like a lot of trouble, and I don't have a long enough ethernet cable to get the hub close to the lock.
Very likely. For security, locks pair in whisper mode. Also, I think using radio transmissions directly to the controller, as opposed to using repeaters. After pairing, beaming repeaters will work.
I have two Yale Locks. One is several years old, the second is less than a year old and is the Lever Lock version. Both of mine have the ZWave+ module.
I also have more than one Hubitat hub and I've toggled both locks back and forth between two hubs. (A C-4 and a C-7) Both have worked first time, both have taken 3 or more attempts. I've never encountered a requirement to have the lock right next to the hub.
Locks are strange critters because of their category. They are called "barrier devices" by the spec and over multiple years various features were deployed to make them resistant to interception. "Whisper" was one of those methods. The idea was to lower the transmit power so low that it would be impossible to intercept the radio traffic. Neither of my Yale locks require whisper... I've Excluded them from one hub then Included them to another more than 6 times in the past 8 months.
The best solution I've encountered for Include is to Exclude First, Every Time. I even walk around with an Aeon ZStick to assist with that
I have 3 Yale locks, all zwave, two plus. Ironically, I think the non-plus one (the YRD110) is the most rock solid of all of them. The rest are good though (they just have a few issues due to having 250 code slots).
The non-Plus one I was able to pair in place, and it's on a shed in my back yard. No issues at all. Hubitat reports it as paired S0.
The two Zwave Plus locks, a YRD226 and YRD256, paired mostly in place, but they're less than 15ft from the hub direct line. The 256 I had to open the door a bit to get it close enough to pair. I think most locks (or at least my old Schlage locks) "whisper" during pairing. They want to make sure they're talking to your hub, and not someone else's that happens to be in pairing mode. So they need to be close to hub. These paired S0 as well. The biggest issue was you then had to do a fetch all codes, and that took a few tries to complete. But they've been super reliable since I got them, especially compared to my Schlage's that were the exact opposite of reliable (yet they worked great in ST with rboy's driver/app).
Thank you all for your comments and suggestions. I pulled the lock from the door and brought next to the hub and got it successfully paired. So that's the issue. I have one more to do and I'm expecting it will go well, too.
Seems like it should be written somewhere to place the lock next to the hub as it would have saved me hours of frustration. Of if it is written, I overlooked it which could very well be the case. Thank again!
This shouldn’t be a problem with nearby repeaters and modern locks, but it’s definitely not covered by Yale documentation. We will add the appropriate suggestions to our Z-Wave help docs. Thanks for the feedback.
Indeed not in docs. Think i learned the whisper piece from DrZwave. The lock should work fine after moving to it’s normal home, now. Repeaters will be fine.
I kinda had thought this was one of the reasons for adding wifi dongle support. So you could move the hub close to devices like this for pairing...
No the WiFi adapter support was added because it was asked for many times over, and hub owners can now have another way to get their hubs into central locations of their homes for better overall signal distribution to their Zigbee and Z-Wave devices.
So often I’ve asked consumer clients where their WiFi modem was, and sure enough the ISP had installed it in the corner of their basement, because that’s either what the homeowner (with no knowledge that this was a bad idea) had asked them to do, or the installer did it because it used the least amount of cable and/or it was the easiest and fastest place to install it. Or all of the above.