Assa Abloy Yale Real Living Assure Lock YRD216-ZW3 Assembly Instructions

1
Yale Locks
Z-Wave Plus ™v2 System Integrators Guide
Yale Assure Electronic Deadbolts
YRD216-ZW3, YRD226-ZW3, YRD256-ZW3,
YRC216-ZW3, YRC226-ZW3, YRC256-ZW3,
YRD652-ZW3, NF-YRD622-ZW3, NF-YRD612-ZW3,
YRC652-ZW3, NF-YRC622-ZW3, NF-YRC612-ZW3,
YRD622-ZW3, YRD642-ZW3, YRC622-ZW3, YRC642-ZW3,
YRD410-ZW3, YRD420-ZW3, YRD430-ZW3, YRD450-ZW3
Document Revision: 1.9
November 2022

2
Contents
Revision History .......................................................................................... 4
Yale Z-Wave Plus ™Product Info ................................................................... 5
Network Operations ..................................................................................... 5
Enroll/Add device to network (SmartStart) ................................................... 5
Enroll/Add device to network (Classic Inclusion Mode) for Assure Lock
[YRC/D216/226/256/622/642/652, NF-YRC/D612/622] .................................. 5
Enroll/Add device to network (Classic Inclusion Mode) for Assure 2 Lock
[YRD410/420/430/450] ............................................................................. 6
Un-enroll/Remove device from network (Exclusion Mode)................................ 6
Factory Reset........................................................................................... 6
Supported Command Classes ........................................................................ 7
Command Class Z-Wave Plus ™Info, Version 2............................................. 7
Command Class Manufacturer Specific, Version 2*......................................... 7
Command Class Security, Version 1............................................................. 9
Command Class Security 2, Version 1 .......................................................... 9
Command Class Device Reset Locally, Version 1* .......................................... 9
Command Class Power Level, Version 1* .................................................... 10
Command Class Version, Version 3* .......................................................... 10
Command Class Battery, Version 1* .......................................................... 11
Command Class Door Lock, Version 4* ...................................................... 12
Command Class Door Lock Logging, Version 1* ........................................... 12
Command Class Schedule Entry Lock, Version 3*......................................... 12
Command Class User Code, Version 2* ...................................................... 12
Command Class Time Parameters, Version 1* ............................................. 16
Command Class Time, Version 2 ............................................................... 16
Command Class Firmware Update Meta Data, Version 5* .............................. 17
Command Class Association, Version 2* ..................................................... 18
Command Class Multi Channel Association, Version 3* ................................. 18
Command Class Association Group Info, Version 3* ..................................... 19
Command Class Notification, Version 8* ....................................................... 21
Command Class Configuration, Version 4*.................................................. 25

3
Command Class Application Status, Version 1 ............................................. 28
Command Class Transport Service, Version 2.............................................. 28
Command Class Supervision, Version 1 ...................................................... 28
Command Class Indicator, Version 3* ........................................................ 28
Command Class Basic, Version 2* ............................................................. 29
* This command class requires security.

4
Revision History
Rev.
Details
1.0
Initial Release
1.1
Made the following updates:
•Added Command Class Clock section.
•Added Clock Report to the Association Group Info commands list.
•Marked Time as a secure command class.
•Added the following note to Time, Time Parameters, and Clock
command classes: “If the controller does not support either the
Time CC, Time Parameters CC, or Clock CC, then scheduled users
will not have access.”
•Added a brief description of the time syncing mechanism to the
Command Class Time section.
•Changed Master Code slot from 0xFB to 0x00 in Notifications
Table.
1.2
Made the following updates:
•Marked the Version command class as secure.
•Added Basic command class.
•Added information about non-access user codes to the User Code
command class section.
1.3
Updated the Product ID description in the “Command Class
Manufacturer Specific” section.
1.4
Made the following updates:
•Added interconnected locks: YRC216, YRC226, YRC256
•Added configuration parameter 28 (expiration time) to the
Configurable Parameters table.
1.5
Made the following updates:
•Provided Version Report example
•Add mapping of Basic CC to Door Lock CC
•Updated CC descriptions that required security
•Updating Configuration Parameter Table
•Fixed the Max Nodes for Association
•Add information on how our Lock uses the Indicator feature
•Add information how to trigger unsolicited AGI Lifeline reports
•Add description of OTA internal step
•Updated User Code User ID Status Values from CC v1 vs v2
•Removed support for Clock CC
1.6
•Added NF-YRD612, NF-YRD622, NF-YRC612, NF-YRC622 and
YRC652
•Added SmartStart feature statement
1.7
•Added YRD622, YRD642, YRC622 and YRC642
•Expectations from User Code Set/Get vs Extended User Code
Set/Get Commands
1.8
•Added YRD410/420/430/450
1.9
•Added BLE Alarms from BLE locks

5
Yale Z-Wave Plus ™Product Info
Manufacturer ID: ASSA ABLOY (0x0129)
Z-Wave™Device Type: Door Lock Keypad
Z-Wave™Role Type: Listening Sleeping Slave (LSS)
Network Operations
Enroll/Add device to network (SmartStart)
SmartStart enabled products can be added into a Z-Wave™network by scanning the
Z-Wave™QR Code present on the product with a controller providing SmartStart
inclusion. No further action is required and the SmartStart product will be added
automatically within 10 minutes of being switched on in the network vicinity.
•Open the Z-Wave™system’s smart home app via smartphone or tablet and
follow the in-app prompts to add a new device.
•SmartStart works when the Z-Wave™system has the DSK saved and one of
the following are true:
oThe lock has the minimum Lock firmware version AND is in a factory-
reset state:
▪YRC/D216/226/256: v4.4.00
▪YRC/D652: v2.1.07
▪NF-YRC/D622: v2.1.11
▪NF-YRC/D612: v2.2.4
▪YRC/D622/642: v3.2.44
▪YRD410/420/430/450: v1.2.204
oAn internal key has already been established.
Enroll/Add device to network (Classic Inclusion Mode) for
Assure Lock [YRC/D216/226/256/622/642/652, NF-
YRC/D612/622]
•Enter the 4–8-digit Master PIN code followed by the key.
•Press the key followed by the key.
•Press the key followed by the key.
•Scan the QR code, if prompted, or…
•Enter the first five (5) digits of the DSK if prompted.

6
Enroll/Add device to network (Classic Inclusion Mode) for
Assure 2 Lock [YRD410/420/430/450]
Un-enroll/Remove device from network (Exclusion Mode)
•Enter the 4–8-digit Master PIN code followed by the key.
•Press the key followed by the key.
•Press the key followed by the key.
When the Yale lock is unenrolled/excluded from the network through the device
menu mode, any changes previously made to the user code database and
configuration settings will be retained, as opposed to set back to defaults.
Factory Reset
•Factory resetting the lock with the Z-Wave™module installed will clear the Z-
Wave™network settings, causing the device to be removed from the
network.
•The following is the method of performing a factory reset:
1. Manual factory reset, via power cycle while holding button on inside
lock escutcheon
▪See the Lock Installation Manual for details.
▪Please use the manual factory reset procedure only when the
network primary controller is missing or otherwise inoperable.

7
Supported Command Classes
The Yale Assure Z-Wave Plus ™deadbolts follow the Z-Wave™Command Class
Specifications for all command classes that are implemented. Please refer to these
specifications for specifics on how each command class works. The supported
command classes are listed below, and certain sections contain details about
operations that may be specific to the Yale lock. If a section is blank, then please
refer to the Z-Wave™specifications.
As a secure device, most of the command classes supported by the lock are
required to be sent securely with Z-Wave™security. During enrollment, the
controller can use the Security Command Class to get this list directly from the
lock. If a command class requires security, it is also indicated as such below.
Specification used: Z-Wave™Specifications Release Dec 2021 BCD
Command Class Z-Wave Plus ™Info, Version 2
The Z-Wave Plus ™Info command class reports the following information:
•Role Type: Slave Sleeping Listening (0x07)
•Node Type: Z-Wave Plus ™Node (0x00)
•Installer Icon Type: 0x0300
•User Icon Type: 0x0300
Command Class Manufacturer Specific, Version 2*
* This command class requires security.
The Manufacturer Specific command class reports the following information:
•Manufacturer ID: 0x0129
oThis is the manufacturer ID assigned to ASSA ABLOY.
•Product ID:
oThe Product ID can be used to differentiate between hardware
platforms, as well as between ZW2 and ZW3. See Table 1 - First 2
Digits of Product ID, below, for details.
oProduct IDs for the locks covered in this document are as follows:
▪0x4600 for older version of Yale Residential Deadbolt Lock
▪0x46D1 for YRD216-ZW3 (Keyed Push Button Deadbolt)
▪0x46D2 for YRD226-ZW3 (Keyed Touch Screen Deadbolt)
▪0x46D5 for YRD256-ZW3 (Keyless Touch Screen Deadbolt)
▪0x46C1 for YRC216-ZW3 (Interconnected Push Button
Deadbolt)

8
▪0x46C2 for YRC226-ZW3 (Interconnected Keyed Touch Screen
Deadbolt)
▪0x46C5 for YRC256-ZW3 (Interconnected Keyless Touch Screen
Deadbolt)
▪0x4DD5 for YRD652-ZW3 (2nd Generation Keyless Touch Screen
Deadbolt)
▪0x4DD2 for NF-YRD622-ZW3 (2nd Generation Keyed Touch
Screen Deadbolt)
▪0x4DD1 for NF-YRD612-ZW3 (2nd Generation Keyed Push Button
Deadbolt)
▪0x4DC5 for YRC652-ZW3 (2nd Generation Interconnected
Keyless Touch Screen Deadbolt)
▪0x4DC2 for NF-YRC622-ZW3 (2nd Generation Interconnected
Keyed Touch Screen Deadbolt)
▪0x4DC1 for NF-YRC612-ZW3 (2nd Generation Interconnected
Keyed Push Button Deadbolt)
▪0x52D2 for YRD622-ZW3 (2nd Generation Fire Rated Keyed
Touch Screen Deadbolt)
▪0x52D4 for YRD642-ZW3 (2nd Generation Fire Rated Keyless
Touch Screen Deadbolt)
▪0x52C2 for YRC622-ZW3 (2nd Generation Fire Rated Keyed
Interconnected Touch Screen Deadbolt)
▪0x52C4 for YRC642-ZW3 (2nd Generation Fire Rated Keyless
Interconnected Touch Screen Deadbolt)
▪0x45D1 for YRD410-ZW3 (2nd Generation Assure Keyed Push
Button Deadbolt)
▪0x45D2 for YRD420-ZW3 (2nd Generation Assure Keyed Touch
Screen Deadbolt)
▪0x45D3 for YRD430-ZW3 (2nd Generation Assure Keyless Push
Button Deadbolt)
▪0x45D5 for YRD450-ZW3 (2nd Generation Assure Keyless Touch
Screen Deadbolt)
▪
•Product Type ID:
o0x8004 for YRD216-ZW3 & YRCD216-ZW3 (Push Button Deadbolt)
o0x8002 for YRD226-ZW3, YRC226-ZW3, YRD256-ZW3, & YRC256-ZW3
(Touch Screen Deadbolt)
o0x8109 for YRD652-ZW3, YRC652-ZW3, NF-YRD622-ZW3, & NF-
YRC622-ZW3 (2nd Generation Touch Screen Deadbolt)
o0x810A for NF-YRD612-ZW3 & NF-YRC612-ZW3 (2nd Generation Push
Button Deadbolt)

9
o0x8103 for YRC/D622-ZW3 & YRC/D642-ZW3 (2nd Generation Fire
Rated Touch Screen Deadbolt)
o0x8104 for YRD410-ZW3, YRD420-ZW3, YRD430-ZW3 & YRD450-ZW3
(2nd Generation Assure Deadbolt)
Table 1 - First 2 Digits of Product ID
Z-Wave™
Type
Platform
Hex Value
[0x8004/0x8002]-ZW2
0
0
0
0
0
1
1
0
0x06
[0x8004/0x8002]-ZW3
0
1
0
0
0
1
1
0
0x46
[0x8109/0x810A]-ZW2
0
0
0
0
1
1
0
1
0x0D
[0x8109/0x810A]-ZW3
0
1
0
0
1
1
0
1
0x4D
[0x8103]-ZW2
0
0
0
1
0
0
1
0
0x12
[0x8103]-ZW3
0
1
0
1
0
0
1
0
0x52
[0x8104]-ZW2
0
0
0
0
0
1
0
1
0x05
[0x8104]-ZW3
0
1
0
0
0
1
0
1
0x45
Command Class Security, Version 1
This command class has been implemented per the Z-Wave™Specification.
Command Class Security 2, Version 1
This command class has been implemented per the Z-Wave™Specification.
Command Class Device Reset Locally, Version 1*
* This command class requires security.
The Yale door locks covered in this guide can be reset to their factory default
settings by manually resetting the lock or by BLE command via app for BLE locks
(by following the procedure outlined in the specific lock’s manual).
Upon factory reset, all Z-Wave™network settings are cleared, all the user codes are
erased from the lock (including the master code), and all configurable settings are
reset to default values, except for the language setting. A factory reset leaves the
lock in a completely unsecure state (waiting for master code to be set), so care
should be taken if using the configuration parameter to perform a remote reset.
However, if the DUT is unenrolled/excluded from the network through the device
menu mode, then the user code database and configuration settings will not be
reset to the defaults.

10
Command Class Power Level, Version 1*
* This command class requires security.
This command class has been implemented per the Z-Wave™Specification.
The Power Level command class was implemented to allow controllers to set the
transmit power for the door lock. This could be useful in large networks with many
nodes, so that the lock can find working routes back to the controller while
transmitting at a lower power. This ensures robust routes when the normal transmit
power level is restored.
Currently there is no way to initiate a low power enrollment; this command class
can only be used once the lock is enrolled successfully.
Command Class Version, Version 3*
* This command class requires security.
The Yale Real Living locks are a multi-processor system with 1 additional firmware
target. All processors can be updated through the Firmware Update Meta Data
command class. The firmware targets are numbered as follows:
•Firmware Target 0 = Z-Wave™Chip
•Firmware Target 1 = Lock Processor
To identify the firmware version for each target, the hex data in the firmware
version report must be converted to decimal prior to combining major and minor
version into the full version.
After a controller sends a Version Get command the log will display the Version
Report similar to the below:
The above Version Report will be defined as this in the Z-Wave™sniffer tool,
Zniffer:

11
For Firmware Target 0, the Firmware 0 Version (0x02) and Sub version (0x22)
translate to module firmware decimal value of “2.34”.
For Firmware Target 1 (the data under vg1), Firmware Version (0x2C) and Sub
version (0x00) translate to lock firmware decimal value of “4.3.00”.
Command Class Battery, Version 1*
* This command class requires security.
Per the Z-Wave Plus ™Specification, the lock will send a Battery Report with a
value of 0xFF to the Lifeline node when a critical battery level is reached (starting
at about 3.8V for Product Type IDs 0x8002 & 0x8004 and starting at about 4.2V for
Product Type ID 0x8109, 0x810A, 0x8103 & 0x8104). In addition, the Yale Locks
provide 2 earlier low battery alarms through the notification command class (see
Table 7 - Notification Table).
Low battery alarms will be generated if the lock is in a low battery state during one
of the following events: any motor activation (keypad lock/unlock, RF lock/unlock,
etc.), controller sends Get Battery command, or the unsolicited battery report was
triggered. Yale locks will generate an unsolicited Battery Report every 8 hours if a
node is listed in the Lifeline Group.

12
Command Class Door Lock, Version 4*
* This command class requires security.
Yale Z-Wave Plus ™locks support three door lock modes: Door Secured (0xFF),
Door Unsecured (0x00), and Door Unsecured with timeout (0x01). When Auto
Relock is enabled, the lock will automatically relock after all unlock events. Yale Z-
Wave Plus ™locks do not support any of the “Door Unsecured for outside Door
Handles”(0x20, 0x21) or “Door Unsecured for inside Door Handles” (0x10, 0x11)
modes.
Command Class Door Lock Logging, Version 1*
* This command class requires security.
This command class has been implemented per the Z-Wave™Specification.
Command Class Schedule Entry Lock, Version 3*
* This command class requires security.
Yale locks support Year Day Schedule types and Daily Repeating Schedule types.
Yale locks allow the controller to apply multiple schedules to a single user. Each
user has 1 Year Day Schedule slot (Slot ID 1) and 7 Daily Repeating slots (Slot IDs
1 –7). If user scheduling is used in the lock, then the controller MUST set the
lock’s time using the Time Parameters command class.
Command Class User Code, Version 2*
* This command class requires security.
Versions 1 and 2 of this command class can address user code slots 1 through 250
via the User Code Set/Get/Report commands. Version 2 of this command class also
includes extended versions of each of these commands, used to address the
extended range of users.

13
Table 2 –Expected Reports for Set/Get Commands
Command
Slots 1-250
Slot 251
Slots 252-254
Slot 255
Slots 256-
500
User Code CC
v1/v2: User
Code Get
User Code
Report
User Code
Report
User Code Report
User Code
Report
N/A
User Code CC
v1/v2: User
Code Set
User Code
Report
Master
Code
Report
User Code Report
User Code
Report
N/A
User Code CC
v2: Extended
User Code Get
Extended User
Code Report
Extended
User Code
Report
Extended User
Code Report
Extended
User Code
Report
Extended
User Code
Report
User Code CC
v2: Extended
User Code Set
Extended User
Code Report
Extended
User Code
Report
Extended User
Code Report
Extended
User Code
Report
Extended
User Code
Report
The master code can be accessed (read/write) using slot 251 (0xFB), if using
version 1 of this command class. For version 2, the Master Code Set/Get/Report
commands must be used.
Yale locks do not support bulk commands (setting or getting multiple user codes at
once) or CRC functionality for this command class.
It should be noted that the lock’s operation mode (called “User Code Keypad Mode”
in this command class) can be modified through Version 2 of this command class,
or through parameter 8 of the Configuration command class. This is the only
parameter that can be modified through more than one command class.
The following implementation notes apply specifically to non-access user codes:
•The usage of non-access users has changed slightly with ZW3, compared to
ZW2, but is still backwards compatible. If a User Code Set is transmitted
using version 1 of the command class, then the lock will accept a value of
0x04 as the status for the non-access user.
•Previously, a value of 0x04 was reserved for setting non-Access users, as
stated above. When using version 2 of this command class, a non-Access
(now called “Messaging”) user ID status is assigned a value of 0x03. This
value of 0x03 should be used with the Extended User Code Set command.
•A non-access user can be identical to a “normal”PIN code, aside from the
fact that it does not grant access.
•Any available user code slot (except the master code) can be used to store a
non-access user code.
•Schedules can be applied to non-access users.
Yale locks support the following User ID Status values:

14
Table 3 - User ID Status User Code CC v1 vs v2
User ID Status
User Code CC v1 Set
User Code CC v1 Report Value
Description
Value
Value
Available
0x00
0x00
Enabled / Grant Access
0x01
0x01
Disabled
0x02
0x03
0x03
Messaging:
The user code is accepted,
but the lock does not grant
access to the user. Instead, it
generates an alarm to the
Lifeline and does NOT take
preventative actions for
further attempts to enter the
User ID and/or User Code.
0x04
0x04
One-Time Use:
This PIN is disabled
immediately after being used
for a successful unlock
operation.
0x06
0x06
Expiring:
This PIN is disabled once a
specified amount of time has
passed after being used for a
successful unlock operation.
The expiration time is set
through the Configuration
command class.
0x07
0x07

15
User ID
Status
User Code CC v2: Extended
User Code Set
User Code CC v2: Extended User
Code Report Value
Description
Value
Value
Available
0x00
0x00
Enabled /
Grant Access
0x01
0x01
Disabled
0x02
0x02
Messaging:
The user code
is accepted,
but the lock
does not grant
access to the
user. Instead,
it generates an
alarm to the
Lifeline and
does NOT take
preventative
actions for
further
attempts to
enter the User
ID and/or User
Code.
0x03
0x03
One-Time Use:
This PIN is
disabled
immediately
after being
used for a
successful
unlock
operation.
0x06
0x06
Expiring:
This PIN is
disabled once a
specified
amount of time
has passed
after being
used for a
successful
unlock
operation. The
expiration time
is set through
the
Configuration
command
class.
0x07
0x07

16
Command Class Time Parameters, Version 1*
* This command class requires security.
The controller must set the Time Parameters in the lock anytime the lock loses
power. If the time is not set by the controller, then user codes with schedules
applied to them cannot be granted access. When the lock is powered up, it will
generate a Notification Report to indicate to the controller that power has been
applied (Alarm V1 Type = 0x82, Alarm V1 Level = 0x00, Event Type = 0x08, Event
Value = 0x01). This indicates to the controller that the lock no longer has a valid
time set.
If the controller does not support either the Time CC or Time Parameters CC, then
scheduled users will not have access.
Command Class Time, Version 2
The controller must set the Time Parameters in the lock anytime the lock loses
power. Even though the Time CC is not secure, the Time Set command must be
issued at the same or higher security level as when the device was enrolled in order
for time to be set otherwise it will be rejected by the device. If the time is not set
by the controller, then user codes with schedules applied to them cannot be
granted access. When the lock is powered up, it will generate a Notification Report
to indicate to the controller that power has been applied (Alarm V1 Type = 0x82,
Alarm V1 Level = 0x00, Event Type = 0x08, Event Value = 0x01). This indicates to
the controller that the lock no longer has a valid time set.
If the controller does not support either the Time CC or Time Parameters CC, then
scheduled users will not have access. A time sync should occur every 8 hours,
starting with the Time CC. If there is no response within a minute, the next step is
to issue a Time Parameters Get to sync time.

17
Command Class Firmware Update Meta Data, Version 5*
* This command class requires security.
Yale Z-Wave Plus ™locks support over-the-air (OTA) upgrading of 2 firmware
targets:
1. Firmware Target 0: Z-Wave™chip
2. Firmware Target 1: The lock main processor
Firmware Target 0 is used to determine the correct Z-Wave™processor image to
download. ID 1 is always 0xA5, to signal this is an ASSA ABLOY Z-Wave™image,
and ID 2 is specific to the region, with the lower nibble being 0x0 and the upper
nibble being the value in Table 4 - Region-Specific Values for Firmware ID 0.
Eventually the lower nibble will be used to separate builds within a specific region,
but this will also be 0 for now, since there is only a single build of firmware.
Table 4 - Region-Specific Values for Firmware ID 0 (Upper Nibble)
Region
Value
ANZ
0x1
CN
0x2
EU
0x3
HK
0x4
IL
0x5
IN
0x6
JP
0x7
KR
0x8
RU
0x9
US
0xA
Firmware 1 target will depend on which version of the lock is in use (mapped to the
Product Type ID).
•For YRC/D216-ZW3 (Push Button interface), Firmware 1 ID = 0x8004.
•For YRC/D226-ZW3 & YRC/D256-ZW3 (Touch Screen interface), Firmware 1
ID = 0x8002.
•For YRC/D652-ZW3 & NF-YRC/D622-ZW3 (2nd Generation Touch Screen
interface), Firmware 1 ID = 0x8109.
•For NF-YRC/D612-ZW3 (2nd Generation Push Button interface), Firmware 1
ID = 0x810A.
•For YRC/D622-ZW3 & YRC/D642-ZW3 (2nd Generation Fire Rated Touch
Screen Deadbolt), Firmware 1 ID = 0x8103
•For YRD410-ZW3, YRD420-ZW3, YRD430-ZW3 & YRD450-ZW3 (2nd
Generation Assure Deadbolt), Firmware 1 ID = 0x8104

18
After an OTA is performed (a Firmware Update Status Report should return with
successful), there is an additional step internally where we write/apply the image to
the lock/module. When the image is being applied to the lock, the lock is
unresponsive until completion of the apply image. Once the completion of the OTA
image is applied the lock silently reboots.
The following is the time it takes for each product to complete OTA image apply
phase:
•For Z-Wave™Radio Chip, ~10 seconds
•For YRC/D216-ZW3 (Push Button interface), ~ 3 minutes
•For YRC/D226-ZW3 and YRC/D256-ZW3 (Touch Screen interface), ~ 3
minutes
•For YRC/D652-ZW3 & NF-YRC/D622-ZW3 (2nd Generation Touch Screen
interface), ~ 13 minutes
•For NF-YRC/D612-ZW3 (2nd Generation Push Button interface), ~ 13
minutes
•For YRC/D622-ZW3 & YRC/D642-ZW3 (2nd Generation Fire Rated Touch
Screen Deadbolt), ~23 minutes
•For YRD410-ZW3, YRD420-ZW3, YRD430-ZW3 & YRD450-ZW3 (2nd
Generation Assure Deadbolt), ~23 minutes (full image) ~3 minutes
(patch/differential image)
Command Class Association, Version 2*
* This command class requires security.
This command class has been implemented per the Z-Wave™Specification.
Command Class Multi Channel Association, Version 3*
* This command class requires security.
This command class has been implemented per the Z-Wave™Specification.
Yale locks support only one group, which can contain up to 5 nodes.

19
Command Class Association Group Info, Version 3*
* Command Class Requires Security
Yale locks support the Lifeline Association Group.
Table 5 - Association Table
Group ID
Maximum Nodes
Description
Commands
1
5
Lifeline
•Command_Class Battery
oBattery_Report
•Command_Class_Configuration
oConfiguration_Report
•Command_Class_Notification
oNotification_Report
•Command_Class_Door_Lock
oDoor_Lock_Operation_Report
oDoor Lock Configuration Report
•Command_Class_Device_Reset_Locally
oDevice_Reset_Locally_Notification
•Command_Class_User_Code
oUser Code Report
oExtended User Code Report
oUser Code Keypad Mode Report
oMaster Code Report

20
The following are the actions to trigger the reports:
Table 6 –Lifeline Report Trigger Table
Report Command
RF Trigger
Manual Trigger
Battery Report
Any RF Lock Operation when lock is
under the battery thresholds
Any manual/keypad Lock Operation
when lock is under the battery
thresholds or Power Cycle Lock
Configuration Report
Configuration Set
Change Lock Settings via Keypad
Notification Report (Access Control)
Any RF Lock Operation
Manual or Keypad Unlock/Lock
Notification Report (Power
Management)
Any RF Lock Operation when lock is
under the battery thresholds
Any manual/keypad Lock Operation
when lock is under the battery
thresholds or Power Cycle Lock
Door Lock Operation Report
Manual or Keypad Unlock/Lock
Door Lock Configuration Report
Door Lock Configuration Set
Enable/Disable Auto-Relock Feature via
Keypad
Device Reset Locally Notification
HW Factory Reset
User Code Report
Add/Delete User Code via User Code Set
Command
Add/Delete User Code via Keypad from
Slots 1-250
Extended User Code Report
Add/Delete User Code via Extended
User Code Set Command
Add/Delete User Code via Keypad from
Slots 251-500
User Code Keypad Mode Report
User Code Keypad Mode Set
Enable/Disable Vacation Mode or Privacy
Mode (refer to Installation Manual)
Master Code Report
Master Code Set
Update/Modify Master Code via Keypad