|
| 1 | +<?xml version="1.0" encoding="UTF-8"?> |
| 2 | +<thing:thing-descriptions bindingId="zwave" |
| 3 | + xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" |
| 4 | + xmlns:thing="http://eclipse.org/smarthome/schemas/thing-description/v1.0.0" |
| 5 | + xsi:schemaLocation="http://eclipse.org/smarthome/schemas/thing-description/v1.0.0 |
| 6 | + http://eclipse.org/smarthome/schemas/thing-description/v1.0.0"> |
| 7 | + |
| 8 | + <thing-type id="kwikset_910_00_000" listed="false"> |
| 9 | + <label>Kwikset SmartCode 910 Touchpad Electronic Deadbolt with Z-Wave</label> |
| 10 | + <description><![CDATA[ |
| 11 | +Touchpad Electronic Deadbolt with Z-Wave<br /><h1>Overview</h1><p>Kwikset®, the leader in residential security, introduces the SmartCode™ 910 Touchpad Electronic Deadbolt with Z-Wave.</p> <ul><li>Backlit keypad with One touch locking</li> <li>30 user codes</li> <li>BHMA grade 2 certified</li> <li>Full 128-bit encryption security</li> <li>Drill and pick resistant backup keyway</li> <li>SmartKey: Re-key the lock in seconds</li> </ul><br /><h2>Inclusion Information</h2><ul><li>Initiate the process to add the lock to your system at your smart home controller.</li> <li>When prompted by your smart home system to add the lock, press button “A” on the lock interior one time. The red LED will illuminate when the lock enters Add Mode.</li> <li>Please allow time for the controller to add the lock to your system.</li> </ul><br /><h2>Exclusion Information</h2><ul><li>Follow your smart home system’s instructions to remove the lock from the network.</li> <li>When prompted by the system, press button A” on the lock interior once. </li> <li>The red LED will illuminate when the lock enters Remove mode. </li> </ul><br /><h2>Wakeup Information</h2><p>Even though the lock is sleeping, all buttons are active and can be used to initiate any lock activity.</p> <p>For the RF side, it will wake up every 1 second to check if there are any requests from your smart home controller</p> |
| 12 | + ]]></description> |
| 13 | + <category>Lock</category> |
| 14 | + |
| 15 | + <!-- CHANNEL DEFINITIONS --> |
| 16 | + <channels> |
| 17 | + <channel id="lock_door" typeId="lock_door"> |
| 18 | + <label>Door Lock</label> |
| 19 | + <properties> |
| 20 | + <property name="binding:*:OnOffType">COMMAND_CLASS_DOOR_LOCK</property> |
| 21 | + </properties> |
| 22 | + </channel> |
| 23 | + <channel id="alarm_access" typeId="alarm_access"> |
| 24 | + <label>Alarm (access)</label> |
| 25 | + <properties> |
| 26 | + <property name="binding:*:OnOffType">COMMAND_CLASS_ALARM;type=ACCESS_CONTROL</property> |
| 27 | + </properties> |
| 28 | + </channel> |
| 29 | + <channel id="alarm_burglar" typeId="alarm_burglar"> |
| 30 | + <label>Alarm (burglar)</label> |
| 31 | + <properties> |
| 32 | + <property name="binding:*:OnOffType">COMMAND_CLASS_ALARM;type=BURGLAR</property> |
| 33 | + </properties> |
| 34 | + </channel> |
| 35 | + <channel id="alarm_power" typeId="alarm_power"> |
| 36 | + <label>Alarm (power)</label> |
| 37 | + <properties> |
| 38 | + <property name="binding:*:OnOffType">COMMAND_CLASS_ALARM;type=POWER_MANAGEMENT</property> |
| 39 | + </properties> |
| 40 | + </channel> |
| 41 | + <channel id="battery-level" typeId="system.battery-level"> |
| 42 | + <properties> |
| 43 | + <property name="binding:*:PercentType">COMMAND_CLASS_BATTERY</property> |
| 44 | + </properties> |
| 45 | + </channel> |
| 46 | + <channel id="time_offset" typeId="time_offset"> |
| 47 | + <label>Clock Time Offset</label> |
| 48 | + <properties> |
| 49 | + <property name="binding:*:DecimalType">COMMAND_CLASS_TIME_PARAMETERS</property> |
| 50 | + </properties> |
| 51 | + </channel> |
| 52 | + </channels> |
| 53 | + |
| 54 | + <!-- DEVICE PROPERTY DEFINITIONS --> |
| 55 | + <properties> |
| 56 | + <property name="vendor">Black & Decker</property> |
| 57 | + <property name="modelId">Kwikset SmartCode 910</property> |
| 58 | + <property name="manufacturerId">0090</property> |
| 59 | + <property name="manufacturerRef">0003:0238</property> |
| 60 | + <property name="dbReference">1025</property> |
| 61 | + <property name="defaultAssociations">1</property> |
| 62 | + </properties> |
| 63 | + |
| 64 | + <!-- CONFIGURATION DESCRIPTIONS --> |
| 65 | + <config-description> |
| 66 | + |
| 67 | + <!-- GROUP DEFINITIONS --> |
| 68 | + <parameter-group name="configuration"> |
| 69 | + <context>setup</context> |
| 70 | + <label>Configuration Parameters</label> |
| 71 | + </parameter-group> |
| 72 | + |
| 73 | + <parameter-group name="association"> |
| 74 | + <context>link</context> |
| 75 | + <label>Association Groups</label> |
| 76 | + </parameter-group> |
| 77 | + |
| 78 | + <!-- PARAMETER DEFINITIONS --> |
| 79 | + <parameter name="config_31_1" type="integer" groupName="configuration" readOnly="true" |
| 80 | + min="0" max="15"> |
| 81 | + <label>31: Dipswitch Settings</label> |
| 82 | + <description><![CDATA[ |
| 83 | +Dipswitch Settings<br /><h1>Overview</h1><p>Configuration parameter is a one byte read only bit mask that returns the state of the user accessible dipswitches on the rear panel of the door lock. This is a read only parameter and cannot be used to set dipswitch settings.</p> <p>The following table shows the definition for the bits being used in the returned value: </p> <table><tr><td>Bit</td> <td>Description</td> </tr><tr><td>0 (0x01)</td> <td>Lock status LED (1:enabled)</td> </tr><tr><td>1 (0x02)</td> <td>Autolock setting (1:enabled)</td> </tr><tr><td>2 (0x04)</td> <td>Buzzer (1:enabled)</td> </tr><tr><td>3 (0x08)</td> <td> <p>Handing Invert (1:enabled)</p> </td> </tr></table><p><strong>Possible Values:</strong></p> <table><tr><td>0</td> <td>All features disabled</td> </tr><tr><td>1</td> <td>Lock status LED enabled</td> </tr><tr><td>2</td> <td>Autolock Enabled</td> </tr><tr><td>4</td> <td>Internal buzzer enabled</td> </tr><tr><td>8</td> <td>Handling invert enabled</td> </tr><tr><td>3</td> <td>Autolock & Lock status LED enabled</td> </tr><tr><td>5</td> <td>Internal buzzer and lock status LED enabled</td> </tr><tr><td>7</td> <td>Autolock, Internal buzzer, and lock status LED enabled</td> </tr><tr><td>15</td> <td>All Features enabled</td> </tr></table> |
| 84 | + ]]></description> |
| 85 | + <default>5</default> |
| 86 | + </parameter> |
| 87 | + |
| 88 | + <parameter name="config_33_4" type="integer" groupName="configuration" |
| 89 | + min="32" max="126"> |
| 90 | + <label>33: SKU</label> |
| 91 | + <description><![CDATA[ |
| 92 | +SKU (length = 8 bytes)<br /><h1>Overview</h1><p>The configuration parameters 33 and 34 are used to set and get the SKU part numbers. The SKU is made up of 8 bytes. Each parameter consists of four bytes of data. Parameter 33 contains the first four most significant bytes of the SKU, while parameter 34 contains the four least significant bytes of the SKU.</p> <p>When setting the SKU, it must be done in two set commands, one for each parameter. The order of programming the SKU does not matter.</p> <p>Setting parameter 33 will program the first four bytes of the SKU. Setting parameter 34 will program the last 4 bytes of the SKU. Most printable values are accepted for the set command.</p> <p>When getting the SKU, it must be done in two get commands, one for each parameter. The order of getting the SKU does not matter.</p> <p>Getting parameter 33 will retrieve the first four bytes of the SKU. Getting parameter 34 will retrieve the last 4 bytes of the SKU. </p> |
| 93 | + ]]></description> |
| 94 | + <default>32</default> |
| 95 | + </parameter> |
| 96 | + |
| 97 | + <parameter name="config_34_4" type="integer" groupName="configuration" |
| 98 | + min="32" max="126"> |
| 99 | + <label>34: SKU</label> |
| 100 | + <description><![CDATA[ |
| 101 | +SKU (length = 8 bytes)<br /><h1>Overview</h1><p>The configuration parameters 33 and 34 are used to set and get the SKU part numbers. The SKU is made up of 8 bytes. Each parameter consists of four bytes of data. Parameter 33 contains the first four most significant bytes of the SKU, while parameter 34 contains the four least significant bytes of the SKU.</p> <p>When setting the SKU, it must be done in two set commands, one for each parameter. The order of programming the SKU does not matter.</p> <p>Setting parameter 33 will program the first four bytes of the SKU. Setting parameter 34 will program the last 4 bytes of the SKU. Most printable values are accepted for the set command.</p> <p>When getting the SKU, it must be done in two get commands, one for each parameter. The order of getting the SKU does not matter.</p> <p>Getting parameter 33 will retrieve the first four bytes of the SKU. Getting parameter 34 will retrieve the last 4 bytes of the SKU.</p> |
| 102 | + ]]></description> |
| 103 | + <default>32</default> |
| 104 | + </parameter> |
| 105 | + |
| 106 | + <parameter name="config_35_2" type="integer" groupName="configuration" readOnly="true" |
| 107 | + min="0" max="65535"> |
| 108 | + <label>35: Lock Type</label> |
| 109 | + <description><![CDATA[ |
| 110 | +Report the Unique ID of the lock type<br /><h1>Overview</h1><p>The configuration Parameter 35 is used as read-only to report the Unique ID of the lock type.</p> <table><tr><td><strong>Released Board ID</strong></td> <td><strong>Unique ID</strong></td> </tr><tr><td>910 Z-wave (Legacy, FW 3.4)</td> <td>0x00 0x00</td> </tr><tr><td>912 Z-wave (Legacy, FW 3.2)</td> <td>0x00 0x00</td> </tr><tr><td>910 Z-wave</td> <td>0x02 0x36</td> </tr><tr><td>912 Z-wave</td> <td>0x03 0x36</td> </tr><tr><td>914 Z-wave</td> <td>0x04 0x36</td> </tr><tr><td>916 Z-wave</td> <td>0x06 0x42</td> </tr></table> |
| 111 | + ]]></description> |
| 112 | + <default>0</default> |
| 113 | + </parameter> |
| 114 | + |
| 115 | + <parameter name="config_40_1" type="integer" groupName="configuration"> |
| 116 | + <label>40: Factory Reset</label> |
| 117 | + <description>Reset Lock to Factory Default</description> |
| 118 | + <default>0</default> |
| 119 | + <options> |
| 120 | + <option value="0">Normal operation</option> |
| 121 | + <option value="1">have lock perform factory reset</option> |
| 122 | + </options> |
| 123 | + </parameter> |
| 124 | + |
| 125 | + <!-- ASSOCIATION DEFINITIONS --> |
| 126 | + <parameter name="group_1" type="text" groupName="association"> |
| 127 | + <label>1: Lifeline</label> |
| 128 | + <description><![CDATA[ |
| 129 | +<br /><h1>Overview</h1><p>Z-Wave Plus Lifeline Supports the following types of unsolicited messages: Battery Report - sends periodic battery reports containing the battery percentage. Door Lock Operation Report - upon power up, this message will be sent to allow the controller to sync up with the current lock status. Notification Report - many notification types will be sent for status and alarms. The following notification types are supported: Access Control (V2), Home Security (V2), and Power Management (V2). Device Reset Locally Notification - this message will be sent to notify the smart home controller that the lock is resetting back to factory defaults and will be leaving the network.</p> |
| 130 | + ]]></description> |
| 131 | + </parameter> |
| 132 | + |
| 133 | + <parameter name="group_2" type="text" groupName="association" multiple="true"> |
| 134 | + <label>2: Group 2</label> |
| 135 | + <description><![CDATA[ |
| 136 | +<br /><h1>Overview</h1><p>This group will provide all Notification reports as described for the Lifeline. This group allows other controllers, other than the lifeline, to receive these types of unsolicited messages as well.</p> |
| 137 | + ]]></description> |
| 138 | + <multipleLimit>5</multipleLimit> |
| 139 | + </parameter> |
| 140 | + |
| 141 | + <!-- STATIC DEFINITIONS --> |
| 142 | + <parameter name="node_id" type="integer" min="1" max="232" readOnly="true" required="true"> |
| 143 | + <label>Node ID</label> |
| 144 | + <advanced>true</advanced> |
| 145 | + </parameter> |
| 146 | + |
| 147 | + </config-description> |
| 148 | + |
| 149 | + </thing-type> |
| 150 | + |
| 151 | +</thing:thing-descriptions> |
0 commit comments