This Yale Assure Lock SL Z-Wave Door Lock Works AWESOME with HomeSeer and Z-Net!

[langenet]

I'm not sure about the others, but my z-wave plus is rock solid with this thing. If you want Zigbee, you'll need to order the Zigbee module. I also use Alex with it. Though, to unlock, you need to specify using another word other than "unlock". Unlock is not allowed for security reason... so,I do so with Jon's helper. Though, to be honest, I don' do it much. You could create a routine in the Alexa app as well. For me, this lock works perfectly and never misses a beat while reporting battery status everyday. I just changed my first set of batteries that came with it when I installed in July '19.

Robert

[randman]

I'm not sure about the others, but my z-wave plus is rock solid with this thing. If you want Zigbee, you'll need to order the Zigbee module. I also use Alex with it. Though, to unlock, you need to specify using another word other than "unlock". Unlock is not allowed for security reason... so,I do so with Jon's helper. Though, to be honest, I don' do it much. You could create a routine in the Alexa app as well. For me, this lock works perfectly and never misses a beat while reporting battery status everyday. I just changed my first set of batteries that came with it when I installed in July '19.

Robert

Thanks for the info. My front door currently has an old Kwikset Z-Wave deadbolt and a Schlage Z-Wave lever lock. I used two different vendors (Kwikset and Schlage) since these particular models were both able to fit in the same door (which is a challenge in general for smart locks given how huge they are). I'm looking to get new locks for a new door, so the Yale Assure Lock SL is a top candidate for the deadbolt. Ideally, I'd also like a lever lock, and the Yale assure lever (model YRL256) is a candidate. However, I'm not sure I can fit both the Yale Assure Lock SL (deadbolt) and the Yale Assure Lever in the same door. I'll have to take measurements, since the door holes may be too close. A lot of folks just put a smart deadbolt and a non-locking lever door knob. However, I prefer to have both the deadbolt and the lever be smart locks. If I have contractors that need to enter my home, I leave the deadbolt unlocked and I give them the code for the lever lock. This way, I can leave the deadbolt locked when I don't want to give grant access to folks who have a code to the lever lock (but not the deadbolt code).

[randman]

The specs for the Yale Assure Lock SL says that it supports HomeKit, Alexa, Google, SmartThings, Zigbee, Z-Wave Plus. I use HomeSeer with Z-NET and I also use HomeKit (some of my devices work with HomeKit directly, while other devices, such as Z-Wave devices, are exposed to HomeKit using homebridge). My question is: does the Yale Assure Lock SL support all these protocols (HomeKit, Alexa, Google, Z-Wave Plus, etc.) natively, or you need specific modules for specific protocols? If the lock can support these protocols natively, then can the lock be controlled via Z-Wave Plus and also via HomeKit (w/o homebridge), or do you have to pick a specific protocol that the lock will work with?

I found the answer online at Yale's web site:

"Which Yale locks work with voice assistants? (Amazon Alexa, Google Assistant, Siri)

All Assure Locks with the Wi-Fi and Bluetooth Upgrade Kit, work with all three voice assistants.

Assure locks using a HomeKit Smart Module will work with Siri

Assure Locks with a Z-Wave Plus Smart Home Module are compatible with Amazon Alexa enabled products via a compatible Smart Home Hub. Compatible hubs include, but are not limited to, Samsung SmartThings and Wink.

Assure Locks with a ZigBee Smart Home Module are directly compatible with the new Amazon Echo Plus. No additional Hub is required."

[ArthurLevinson@aol.com]

How are you getting all these features via Home Seer? I see only a few of these options on the HS Devices screen. Is there a plugin you are using or a 3rd party app?

[QuikDraw]

My door lock logging times are off by 1 hour, 1 hour ahead of actual time. for example Illegal Code Entered at Keypad Today at 7:11:20 PM User Code=0. Correct time was 6:11:20
Any ideas on a setting to correct this. Other than this I love the lock so far.
...

I too have logging times 1 hour ahead.
When I rescan the locks (I have 2 of them) Homeseer reports that they support setting the time, and it shows the correct local CST time in the rescan log.
At first I thought it was just one of the locks with the issue because I was having trouble with rescan saying it failed attempting to set the time. But I've since been able to successfully rescan both locks with no errors. And I tested them today, and they are both ahead by one hour.

Does anyone know of a parameter setting that can be sent to these locks to send them a time setting?

[moerderin@gmail.com]

Well this has been frustrating, especially seeing how easy it was for everyone else! I tried adding it to my zwave, and get an error:

Add Node started...
Activate the 'Add to Network' function on the device...
Activate the 'Add to Network' function on the device...
Activate the 'Add to Network' function on the device...
Activate the 'Add to Network' function on the device...
Activate the 'Add to Network' function on the device...
Activate the 'Add to Network' function on the device...
Activate the 'Add to Network' function on the device...
Activate the 'Add to Network' function on the device...
Activate the 'Add to Network' function on the device...
A new node is being added...
Adding a new SLAVE NODE...
DONE - Add Node Operation is Complete.
Done. Node 27 Added.
Reloading (importing) node information...
Synchronizing node information with HomeSeer and creating new device(s) as necessary...
Synchronize nodes finished. Number of device nodes to be created/added = 1
Adding using S0 Security, Negotiating or Verifying SECURITY SCHEME for node 27
Warning: Failed to get a SECURITY SCHEME or verify the key from node 27. Device may not be added properly to HomeSeer.
Warning: If this is an import, you may need to remove and add the device as some devices cannot be added with an import.

It then proceeds to add "fine", but when I try to interact or communicate with the lock at all, there's zero communication happening. I do a device "test", and the controller cannot communicate with it.

Thoughts?

[langenet]

How did you add it? I found I needed to use the "add/include a node" and not "add/include a node without security"

Robert

[moerderin@gmail.com]

How did you add it? I found I needed to use the "add/include a node" and not "add/include a node without security"

Robert

I did it the way you describe. No dice. I read in another thread that either:

• The lock might be falling asleep during the sync process
• The lock needs to be 1 inch from the z-wave stick

I'll try both of those when I get home. Will update here if either works.

[QuikDraw]

I did it the way you describe. No dice. I read in another thread that either:

• The lock might be falling asleep during the sync process
• The lock needs to be 1 inch from the z-wave stick

I'll try both of those when I get home. Will update here if either works.

I've never moved closer to the z-wave stick. One of my locks is about 35 feet away down a hallway, and another is outside inside a steel building about 40 feet away. I have a z-wave repeater in the steel building that seems to help. I also have a repeater in my attic. My experience is as long as the lock is in range of something that is communicating with the controller, it will add fine.
Sometimes it will add, but not correctly. Security isn't right, or child devices are either missing or wrong. Usually a "rescan" from the z-wave management page for the device will fix it. The device is already included in the network. The rescan basically erases what the controller thinks it knows, and queries it again to find and add its capabilities from scratch.
I've even had to do a full rescan from the controller management page for a couple of problem devices. I would delete the problem devices from the devices page (not exclude from network), then go to controller management page and do "Scan existing devices (light scan)." If the light scan doesn't work, the full scan option usually does.

Z-wave is a finicky network, and kind of mysterious. Good luck with your lock.

[devoir]

wished this was Inseon.... less mysterious and super reliable.....


Unfortunately Inseton doesn't have the Marketing STICK brand of Z-mis-behave...
Devoir

[brientim]

The Yale Z-wave normally needs to be within about a metre of the z-wave device. Yale recommends taking the lock as close as you can to the z-wave device and include prior to installation. I have four Yale locks and never had an issue with three of them but one was always a pain to enrol and as QuikDraw stated a rescan would resolve but not always.
The inclusion is in two phases, initial registration and then the security schema, and thus if you have already attempted this it is normally a good practice to exclude the lock before adding again.

[moerderin@gmail.com]

Just wanted to update my experience. I have two locks; both solved:

Lock A - About 50 feet away, one small pony wall between zwave stick and lock.

• Took several tries, but FINALLY I was able to get it fully recognized with all its features.
• I still got the security error mentioned on the other thread.
• I'm kinda leaning towards pretending I didn't see that error and assume everything will behave fine.

Lock B - About 60 feet away, 3 walls (including 1 sound proof, fire proof garage wall) in between lock & z-wave stick.

• When I start the inclusion process, it gets "detected", but I get the security error, and no "features" are recognized.
• I can't even exclude it from the network because when I try to even ping it, the zwave controller is completely unable to communicate further with the lock.
• I finally disassembled the lock, walked over to the z-wave stick, and included it about 3 feet away from the stick
• It included PERFECTLY, no security error, nothing. I walked back to the door, and put it on, and now it works fine.

How the heck I'm able to control the lock from far away, but not include it from far away is absolutely beyond me, but whatever, it's working. Wife is beyond ecstatic.

[QuikDraw]

For no apparent reason one of my Yale locks went flakey on me after working fine for four months. Wouldn't report status correctly. I rescanned it repeatedly without success. I excluded it and re-included it several times without success. I finally resorted to a factory reset of the lock. After that it included perfectly on the first try and is working perfectly again. And I did not move close to the controller to include it. This lock is 50 feet away from the controller in a steel shop with a brick wall in between.

Strange... Not a big deal except on this model, a factory reset requires partial dissassembly to get to the reset button that's behind the battery compartment. It would've been nice if it could be reset without a screwdriver!

[langenet]

Just wanted to update my experience. I have two locks; both solved.
How the heck I'm able to control the lock from far away, but not include it from far away is absolutely beyond me, but whatever, it's working. Wife is beyond ecstatic.

It's because both the inclusion and exclusion process requires direct line of site. The regular use of the lock with z-wave is facilitated by the mesh network.

[RogerL]

So I finally got the zwave module that was on backorder.
Installed it, no problem, added it to the network and it sees it but gives an S0 security error and the only device created is the name of it with no controls.
no battery, no nothing. any ideas?

I removed it and re-added it, same thing.