| layout | title |
|---|---|
documentation |
GED1800 - ZWave |
{% include base.html %}
This describes the Z-Wave device GED1800, manufactured by Black & Decker with the thing type UID of kwikset_ged1800_00_000.
The device is in the category of Lock, defining Devices whose primary pupose is locking something.
The GED1800 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices.
- Dramatically reduced interior size and sleek metal design.
- Featuring SmartKey® re-key technology; re-key the lock yourself in seconds in 3 easy steps.
- Deadbolt operated by electronic keypad or key; backlit for increased visibility at night.
- Keypad stays lit for 30 seconds after inactivity.
- Customized automatic door locking after 30 seconds for peace of mind.
- One touch motorized locking. Lock your door with a single touch. No additional turning/twisting needed.
- Features 30 user access codes and 1 master code option.
- ANSI/BHMA grade 2 certified/20 minute fire rating - UL certified.
- Fits most standard residential door preparations - installs in minutes with just a screw driver.
- Lifetime mechanical and finish warranty, One year electronics warranty.
- 4 AA, purchased separately.
- Full 128-bit encryption security.
Press button “A” on the lock one time to include it in your system.
Press button “A” on the lock one time to exclude it in your system.
Like most Z-Wave locks, the lock doesn't update its status (locked or unlocked) but signals it through alarms instead. Here is some sample output from the alarm_raw channel:
Locked by Controller:
{"notification":"ACCESS_CONTROL__REMOTE_LOCK","level":"1","type":"ACCESS_CONTROL","event":"3","status":"255"}
Unlocked by Controller:
{"notification":"ACCESS_CONTROL__REMOTE_UNLOCK","level":"1","type":"ACCESS_CONTROL","event":"4","status":"255"}
Locked by Hand (key or knob):
{"notification":"ACCESS_CONTROL__MANUAL_LOCK","level":"1","type":"ACCESS_CONTROL","event":"1","status":"255"}
Unlocked by Hand (key or knob):
{"notification":"ACCESS_CONTROL__MANUAL_UNLOCK","level":"1","type":"ACCESS_CONTROL","event":"2","status":"255"}
Locked by Keypad:
{"notification":"ACCESS_CONTROL__KEYPAD_LOCK","level":"0","type":"ACCESS_CONTROL","event":"5","status":"255"}
Unlocked by Keypad (Code #2):
{"notification":"ACCESS_CONTROL__KEYPAD_UNLOCK","code":"2","level":"2","type":"ACCESS_CONTROL","event":"6","parameter-1":"2","status":"255"}
When unlocked by keypad, code, type, and parameter-1 all indicate the code number (2 in the above example)
Sample rule in Openhab to update the lock status, with Door_Lock linked to the lock's lock_door channel, and Door_Lock_Alarm linked to its alarm_raw channel. Make sure you have the JSONPath Transformation installed under Paper UI - Add-ons - Transformations:
rule "Door lock status updates"
when
Item Door_Lock_Alarm changed
then
switch(transform("JSONPATH", "$.event", Door_Lock_Alarm.state.toString)) {
case "1", case "3", case "5" : Door_Lock.postUpdate(ON)
case "2", case "4" : Door_Lock.postUpdate(OFF)
case "6" : {
var userName = ""
switch(transform("JSONPATH", "$.code", Door_Lock_Alarm.state.toString)) {
case "1": userName = "Bill"
case "2": userName = "Ted"
default: userName = "Unknown"
}
mailActions.sendMail("[email protected]", "Door lock opened by code", "Door lock opened by " + userName)
Door_Lock.postUpdate(OFF)
}
}
end
The following table summarises the channels available for the GED1800 -:
| Channel Name | Channel ID | Channel Type | Category | Item Type |
|---|---|---|---|---|
| Door Lock | lock_door | lock_door | Door | Switch |
| Alarm Raw | alarm_raw | alarm_raw | String | |
| Battery Level | battery-level | system.battery_level | Battery | Number |
Lock and unlock the door.
The lock_door channel is of type lock_door and supports the Switch item and is in the Door category.
The following state translation is provided for this channel to the Switch item type -:
| Value | Label |
|---|---|
| ON | Locked |
| OFF | Unlocked |
Provides alarm parameters as json string.
The alarm_raw channel is of type alarm_raw and supports the String item. This is a read only channel so will only be updated following state changes from the device.
This channel sets, and provides the alarm state as a JSON string. It is designed for use in rules.
Represents the battery level as a percentage (0-100%). Bindings for things supporting battery level in a different format (e.g. 4 levels) should convert to a percentage to provide a consistent battery level reading.
The system.battery-level channel is of type system.battery-level and supports the Number item and is in the Battery category.
This channel provides the battery level as a percentage and also reflects the low battery warning state. If the battery state is in low battery warning state, this will read 0%.
The following table provides a summary of the 6 configuration parameters available in the GED1800. Detailed information on each parameter can be found in the sections below.
| Param | Name | Description |
|---|---|---|
| 31 | Status LED | Door lock status LED blinks every 6 seconds |
| 31 | Auto Lock | Automatically re-locks door 30 seconds after unlocking. |
| 31 | Buzzer | Internal Buzzer |
| 33 | SKU (1st half) | First 4 bytes of SKU |
| 34 | SKU (2nd half) | Last 4 bytes of SKU |
| 40 | Factory Default | Reset to factory default settings |
| Lock Timeout | Sets the time after which the door will auto lock |
Door lock status LED blinks every 6 seconds Door lock status LED blinks every 6 seconds. Factory default is ON. The following option values may be configured -:
| Value | Description |
|---|---|
| 0 | Off |
| 1 | On |
The manufacturer defined default value is 1 (ON).
This parameter has the configuration ID config_31_1_00000001 and is of type INTEGER.
This is a read only parameter.
Automatically re-locks door 30 seconds after unlocking. Lock automatically re-locks door 30 seconds after unlocking. OFF position is factory default. If this switch is turned on, it will be disabled if all codes are deleted from the lock. The following option values may be configured -:
| Value | Description |
|---|---|
| 0 | Off |
| 1 | On |
The manufacturer defined default value is 0 (OFF).
This parameter has the configuration ID config_31_1_00000002 and is of type INTEGER.
This is a read only parameter.
Internal Buzzer Internal buzzer enabled. Factory default is ON. It is recommended that the buzzer is left ON during programming. The following option values may be configured -:
| Value | Description |
|---|---|
| 0 | Off |
| 1 | On |
The manufacturer defined default value is 1 (ON).
This parameter has the configuration ID config_31_1_00000004 and is of type INTEGER.
This is a read only parameter.
First 4 bytes of SKU 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.
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. 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.
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. Getting parameter 33 will retrieve the first four bytes of the SKU. Getting parameter 34 will retrieve the last 4 bytes of the SKU.This is an advanced parameter and will therefore not show in the user interface without entering advanced mode. Values in the range 32 to 126 may be set.
The manufacturer defined default value is 32.
This parameter has the configuration ID config_33_4_7FFF0000 and is of type INTEGER.
Last 4 bytes of SKU 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.
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. 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.
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. Getting parameter 33 will retrieve the first four bytes of the SKU. Getting parameter 34 will retrieve the last 4 bytes of the SKU.This is an advanced parameter and will therefore not show in the user interface without entering advanced mode. Values in the range 32 to 126 may be set.
The manufacturer defined default value is 32.
This parameter has the configuration ID config_34_4_0000FFFF and is of type INTEGER.
Reset to factory default settings The configuration parameter 40 is a one byte field, used to set the lock to its default setting, known as a factory reset command.
Reading this parameter will always return a value of 0.
Writing a value of 1 to this parameter will cause both the lock and Z-Wave card to reset back to their default settings and will remove itself from the network. All network information, including associations will be cleared.This is an advanced parameter and will therefore not show in the user interface without entering advanced mode. The following option values may be configured -:
| Value | Description |
|---|---|
| 0 | Don't Reset |
| 1 | Reset to Factory Defaults |
The manufacturer defined default value is 0 (Don't Reset).
This parameter has the configuration ID config_40_1_wo and is of type INTEGER.
This is a write only parameter.
Sets the time after which the door will auto lock.
This parameter has the configuration ID doorlock_timeout and is of type INTEGER.
Association groups allow the device to send unsolicited reports to the controller, or other devices in the network. Using association groups can allow you to eliminate polling, providing instant feedback of a device state change without unnecessary network traffic.
The GED1800 supports 2 association groups.
The Lifeline association group reports device status to a hub and is not designed to control other devices directly. When using the Lineline group with a hub, in most cases, only the lifeline group will need to be configured and normally the hub will perform this automatically during the device initialisation. Per Z-Wave Plus requirements, group 1 is assigned to the Lifeline group and can only support 1 node.
Association group 1 supports 1 node.
Association group 2 is identified as the “Doorlock notify report” group. It allows at most 5 other nodes to be associated with the lock and will provide all Notification Reports, via the Command Class Notification, generated by the lock.
Association group 2 supports 5 nodes.
| Command Class | Comment |
|---|---|
| COMMAND_CLASS_NO_OPERATION_V1 | |
| COMMAND_CLASS_BASIC_V1 | |
| COMMAND_CLASS_DOOR_LOCK_LOGGING_V1 | |
| COMMAND_CLASS_SCHEDULE_ENTRY_LOCK_V2 | |
| COMMAND_CLASS_ASSOCIATION_GRP_INFO_V1 | |
| COMMAND_CLASS_DEVICE_RESET_LOCALLY_V1 | |
| COMMAND_CLASS_ZWAVEPLUS_INFO_V2 | |
| COMMAND_CLASS_DOOR_LOCK_V2 | |
| COMMAND_CLASS_USER_CODE_V1 | |
| COMMAND_CLASS_CONFIGURATION_V1 | |
| COMMAND_CLASS_ALARM_V4 | |
| COMMAND_CLASS_MANUFACTURER_SPECIFIC_V2 | |
| COMMAND_CLASS_POWERLEVEL_V1 | |
| COMMAND_CLASS_FIRMWARE_UPDATE_MD_V3 | |
| COMMAND_CLASS_BATTERY_V1 | |
| COMMAND_CLASS_ASSOCIATION_V2 | |
| COMMAND_CLASS_VERSION_V2 | |
| COMMAND_CLASS_TIME_PARAMETERS_V1 | |
| COMMAND_CLASS_SECURITY_V1 |
Did you spot an error in the above definition or want to improve the content? You can contribute to the database here.