| layout | title |
|---|---|
documentation |
700045 - ZWave |
{% include base.html %}
This describes the Z-Wave device 700045, manufactured by Popp & Co with the thing type UID of popp_700045_00_000.
The device is in the category of Remote Control, defining Any portable or hand-held device that controls the status of something, e.g. remote control, keyfob etc..
The 700045 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the Wakeup Information section below for further information.
This keypad is a security enabled Z-Wave Plus product. An security enabled Z-Wave controller must be used to fully utilize this product. The keypad allows securely controlling devices - such as door locks - and trigger actions in a gateway – such as arm/disarm alarm system– based on the entry of certain key codes. Additionally a bell key allows emulating a doorbell by operating e.g. a door bell or a light or both. The device can operate in two different modes. The mode is chosen the way the device is included into a Z-Wave network:
- Stand Alone Mode. In this case the keypad acts as the primary network controller and will include other devices such as e.g. a strike lock control or a door bell. No other central controller is needed. The management of user codes is done using the keypad itself.
- Network Mode. The keypad is included as additional device into an exiting network. In Z-Wave terms it will then act as inclusion (secondary) controller. It will send commands to a central controller and is managed by this controller. In this mode the device can still directly control door locks but it can also be used to trigger scenes in a central controller.
The device is protected by a tamper switch sending out an alarm message when the enclosure is opened.
Turn the device into management mode by removing the back cover or typing the master code if set. Hit button 4 and confirm with * (Star Key)
Turn the device into management mode by removing the back cover or typing the master code if set. Hit button 4 and confirm with * (Star Key)
The 700045 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour.
The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device.
Wakeup: Ring Key.
To issue a NIF: 0 plus * (Star Key) in Management Mode
The keypad allows typing in up to 20 different key codes and pressing certain dedicated buttons. Key codes are numbered 1...20 must have minimum 4 and maximum 10 digits as number between 0 und 9. All key codes are equal except key code #20 that will also activate the management mode. Beside the 10 numerical keys the devices offers a ENTER key (*), an ESCAPE key (#) and a Bell key. Every key entry needs to be confirmed by "*". Sequences can be aborted using the "#" key.
The bell key will immediately cause ringing a bell if there is a bell devices included in association group 3. They entry of the key code should be confirmed by "*". If no "*" is entered the entry will time out and use the key entered so far. This means its possible not to confirm by "*" and wait for the timeout of few seconds.
The following table summarises the channels available for the 700045 -:
| Channel | Channel Id | Category | Item Type |
|---|---|---|---|
| Binary Sensor | sensor_binary | Door | Switch |
| Scene Number | scene_number | Number | |
| Alarm (access) | alarm_access | Door | Switch |
| Alarm (burglar) | alarm_burglar | Door | Switch |
| Battery Level | battery-level | Battery | Number |
Indicates if a sensor has triggered.
The sensor_binary channel supports the Switch item and is in the Door category. This is a read only channel so will only be updated following state changes from the device.
The following state translation is provided for this channel to the Switch item type -:
| Value | Label |
|---|---|
| ON | Triggered |
| OFF | Untriggered |
Triggers when a scene button is pressed.
The scene_number channel supports the Number item.
This channel provides the scene, and the event as a decimal value in the form <scene>.<event>. The scene number is set by the device, and the event is as follows -:
| Event ID | Event Description |
|---|---|
| 0 | Single key press |
| 1 | Key released |
| 2 | Key held down |
| 3 | Double keypress |
| 4 | Tripple keypress |
| 5 | 4 x keypress |
| 6 | 5 x keypress |
Indicates if the access control alarm is triggered.
The alarm_access channel supports the Switch item and is in the Door category. This is a read only channel so will only be updated following state changes from the device.
The following state translation is provided for this channel to the Switch item type -:
| Value | Label |
|---|---|
| OFF | OK |
| ON | Alarm |
Indicates if the burglar alarm is triggered.
The alarm_burglar channel supports the Switch item and is in the Door category. This is a read only channel so will only be updated following state changes from the device.
The following state translation is provided for this channel to the Switch item type -:
| Value | Label |
|---|---|
| OFF | OK |
| ON | Alarm |
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 battery-level channel supports the Number item and is in the Battery category.
The following table provides a summary of the 6 configuration parameters available in the 700045. Detailed information on each parameter can be found in the sections below.
| Param | Name | Description |
|---|---|---|
| 1 | Automatic Secure Timeout | After this time a CLOSE is sent to the door lock. |
| 2 | Ring Button OFF Timeout | After this time the Door Bell will receive an OFF. |
| 3 | Ring Button ON Command | Value to send on ring button press. |
| 4 | Ring Button OFF Command | |
| 5 | Central Scene ID | Defines if different user codes shall cause individual or similar scene ID. |
| 6 | Buzzer Confirmation | |
| Wakeup Interval | Sets the interval at which the device will accept commands from the controller | |
| Wakeup Node | Sets the node ID of the device to receive the wakeup notifications |
After this time a CLOSE is sent to the door lock.
Values in the range 0 to 127 may be set.
The manufacturer defined default value is 0.
This parameter has the configuration ID config_1_1 and is of type INTEGER.
After this time the Door Bell will receive an OFF. After this time the Door Bell will receive an OFF command regardless of the actuall button is pressed or not Values in the range 3 to 127 may be set.
The manufacturer defined default value is 3.
This parameter has the configuration ID config_2_1 and is of type INTEGER.
Value to send on ring button press.
Values in the range 0 to 255 may be set.
The manufacturer defined default value is 255.
This parameter has the configuration ID config_3_1 and is of type INTEGER.
Values in the range 0 to 255 may be set.
The manufacturer defined default value is 0.
This parameter has the configuration ID config_4_1 and is of type INTEGER.
Defines if different user codes shall cause individual or similar scene ID.
The following option values may be configured -:
| Value | Description |
|---|---|
| 0 | Constant Scene ID 20 for all User Codes |
| 1 | Individual User Codes 1 ... 20 |
The manufacturer defined default value is 0 (Constant Scene ID 20 for all User Codes).
This parameter has the configuration ID config_5_1 and is of type INTEGER.
The following option values may be configured -:
| Value | Description |
|---|---|
| 0 | Disabled |
| 1 | Enabled |
The manufacturer defined default value is 1 (Enabled).
This parameter has the configuration ID config_6_1 and is of type INTEGER.
The wakeup interval sets the period at which the device will listen for messages from the controller. This is required for battery devices that sleep most of the time in order to conserve battery life. The device will wake up at this interval and send a message to the controller to tell it that it can accept messages - after a few seconds, it will go back to sleep if there is no further communications.
This setting is defined in seconds. It is advisable not to set this interval too short or it could impact battery life. A period of 1 hour (3600 seconds) is suitable in most instances.
Note that this setting does not affect the devices ability to send sensor data, or notification events.
This parameter has the configuration ID wakeup_interval and is of type INTEGER.
When sleeping devices wake up, they send a notification to a listening device. Normally, this device is the network controller, and normally the controller will set this automatically to its own address. In the event that the network contains multiple controllers, it may be necessary to configure this to a node that is not the main controller. This is an advanced setting and should not be changed without a full understanding of the impact.
This parameter has the configuration ID wakeup_node 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 700045 supports 3 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.
Association group 1 supports 10 nodes.
Association group 2 supports 10 nodes.
Association group 3 supports 10 nodes.
| Command Class | Comment |
|---|---|
| COMMAND_CLASS_NO_OPERATION_V1 | |
| COMMAND_CLASS_SENSOR_BINARY_V2 | |
| COMMAND_CLASS_ASSOCIATION_GRP_INFO_V1 | |
| COMMAND_CLASS_DEVICE_RESET_LOCALLY_V1 | |
| COMMAND_CLASS_CENTRAL_SCENE_V3 | |
| COMMAND_CLASS_ZWAVEPLUS_INFO_V1 | |
| COMMAND_CLASS_USER_CODE_V1 | |
| COMMAND_CLASS_CONFIGURATION_V1 | |
| COMMAND_CLASS_ALARM_V5 | |
| COMMAND_CLASS_MANUFACTURER_SPECIFIC_V1 | |
| COMMAND_CLASS_POWERLEVEL_V1 | |
| COMMAND_CLASS_FIRMWARE_UPDATE_MD_V1 | |
| COMMAND_CLASS_BATTERY_V1 | |
| COMMAND_CLASS_WAKE_UP_V2 | |
| COMMAND_CLASS_ASSOCIATION_V2 | |
| COMMAND_CLASS_VERSION_V2 | |
| 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.