- Generate Z Wave Network Key Random Generator
- Generate Zwave Network Key Random Key
- Generate Random Number
- Generate Zwave Network Key Random Numbers
Generate random passwords (maximum 100). Each password should be characters long (minimum 6, maximum 24). The passwords will not contain characters or digits that are easily mistaken for each other, e.g., ‘1’ (the digit one) and ‘l’ (lowercase L). Encryption is done with a key, which is a set of binary bits, not a password, which implies a human-readable string. To go from a password to a key, one can use a Password Based Key Derivation Function, such as PBKDF2. Crypto-JS already has a PBKDF2 function built-in, i.e. The Wireless LAN Key Generator allows for quick and valid WEP/WPA key generation. You can use the Random WEP/WPA Key Generator to generate a random WEP or WPA key. Simply choose the desired key length using the drop-down menu, and one will be generated for you. The WEP/WPA Key Generator supports 64bit, 128bit, 152bit & 256bit WEP keys,. The Z-Wave network info screen is available under setup hardware. If there is a Z-Wave controller in the system (a USB-stick for instance), there is a 'Setup' button beside it. Click this and the list of controlled nodes appears. At the top right the node management button houses the 'groups & network' button. Exclusion — is the process of removing Z-Wave devices from the network. Association — is a control relationship between a controlling device and a controlled device. Wakeup Notification — is a special wireless message issued by a Z-Wave device to announces that is able to communicate.
- 5Running Domoticz as a secondary controller
Domoticz use an open source library named 'OpenZWave' library. It's commonly written 'OZW'.As Z-Wave protocol isn't 'free' not all the devices or functionnalities are known in OZW. Most devices are fully working (Fibaro, BeNext, Aeon for the most known), others are just referenced without action (fortrezz, and others, ..).
To be usable in Domoticz, you'll have first to check if your Z-Wave devices are usable with OZW. If not, follow the Adding Devices instructions to get yours included in the OpenZWave Device Database.
List: OZW devices
| OZW : Supported devices
| OZW : Adding-Devices
| OZW : List of open issues
| OZW : forum support
The Z-Wave network info screen is available under setup > hardware. If there is a Z-Wave controller in the system (a USB-stick for instance), there is a 'Setup' button beside it. Click this and the list of controlled nodes appears. At the top right the node management button houses the 'groups & network' button. The screen above appears. To the left is a chord diagram that shows which nodes see each other. This is a feature of the Z-Wave mesh network; some devices do not see each other directly but communicate through intermediate nodes. This graph helps you understand how the network communicates. If the Z-Wave network controller has just started up (due to Domoticz start or reboot), it takes a while for the connections to display. Please wait a moment and return to this screen.Hover the mouse over a node to only display the connections for that node; this makes it easier to examine specific connections.
To the right is the group table. It shows the reported groups for each node, plus the nodes that are in the group. Z-Wave groups are an essential part of a functioning system; it operates even without Domoticz or the controller active, so it is a good thing to understand how they work and how they are setup. Groups are not global, but exist per node. Each node has its own group(s), in which you can place other nodes as listeners. If two nodes (devices) have a group 2, this is not the same group.Clicking a node number shows the option to remove the node from that group. If there is a plus symbol in a group, the node has this group enabled. Click the plus symbol to add another node to that group.
An example: the tz66-d wall switch has two paddles (left and right). The left paddle controls the lamp attached to it physically. The right paddle only signals groups. The tz66-d has four groups:
- Group 1: gets a signal when the left paddle is pressed
- Group 2: gets a signal when the right paddle is pressed
- Group 3: gets a signal when the right paddle is pressed twice
- Group 4: gets a signal when the tz66-d is commanded to turn on or off.
Using the group table, you can include another node (lamp for instance) in one of the tz66d's groups. By putting it in group 2, you can control it though the right paddle. By putting another lamp in group 3, you control that one via a double tap on the right paddle, etc.
Groups also play a big role in where measurement devices (temperature for instance) send their data. Some devices (like the Aeon 4in1) can be configured to send to group 1 (where the controller and thus Domoticz is), but others just send to a fixed group, which requires a receiving device to be put in that group.
The info screen will be extended with more functionality in the future. For now it has the bare necessities ;)There is no scene management (yet), since that can be done through Domoticz itself.
First Include the device in the zwave network, you should see this in the node overview of OpenZWave
Important : Make sure the controller (node 1) is associated in the SAME GROUP of the tag reader (See Groups and Network in the OpenZWave setup)
Important : Make sure the controller (node 1) is associated in the SAME GROUP of the tag reader (See Groups and Network in the OpenZWave setup)
By default no tags are programmed inside the reader.
The reader sends its current codes to OpenZWave when it is awake, to force todo this, press the tamper switch, or press the away button and scan a tag.
You also have todo this after a restart of Domoticz when you want to add/remove tags.
(Best done after all awake-nodes have been queried)
To program a new tag in the reader proceed as follow:
- 1. press the tamper switch on the reader and wait 5 seconds (to force the reader to wake up and sends its current code list)
- 2. go to the hardware setup of OpenZWave
- 3. select the tag reader from the node list.
- 4. from the 'Node Management' select the option 'Start User Code Enrollment'
- 5. press the away button on the reader, when the red light is on, scan the tag.
- 6. the tag should now be included (you can follow this in the log screen)
- 7. press the tamper switch again to force the reader to send the current code
- 8. from the 'Node Management' select the option 'User Code Management'
- 9. you should now see the new tag
- 10. make a note which Code/Value belongs to which tag
After you included a tag you can press the Home/Away button and scan your tag.
When you do this, you will receive a device update for a switch (on/off) that indicates the Home/Away status
To remove a tag from the reader:
- 1. press the tamper switch on the reader and wait 5 seconds (to force the reader to wake up and sends its current code list)
- 2. go to the hardware setup of openzwave
- 3. select the tag reader from the node list.
- 4. from the 'Node Management' select the option 'User Code Management'
- 5. select the tag you wish to remove, and press the 'remove' button
- 6. to force a quick update in the reader (specially for battery operated devices), press the tamper switch again (and wait 5 seconds)
- 7. press the 'Refresh' button, and the tag should be removed
A secondary controller can receive all Z-Wave signals as the master, and thus can act also as a router in 3.20 protocol. A secondary controller can also send orders. This way, a Domoticz Z-Wave box can work as a supplementary box of its own.
To achieve this, the Domoticz version must be superior to 1660. The actually tested configurations are from Vera systems (and fibaro lite to be confirmed) as master in 3.20 version of Z-Wave and Domoticz running the Aeon S2 (given it will work also with other adapters to Domoticz).
Considerations on using a secondary controller
Please remember that Z-Wave device configuration isn't stored in the Z-Wave device so it is the master who has stored device parameters, and thus for Domoticz you'll have to reset all devices parameters.
After some tests, when Domoticz is used as secondary controller, all the parameters in the hardware tab of Z-Wave device are ignored. It's the master controller parameters which are used.
To check this, you can watch Watt consumption on a device on the Vera and on Domoticz. With no modification in Domoticz you can see the same value.
Another test with a Fibaro switch, if you use an 'auto-release' you will see that it's the same as the master when using Domoticz.
Despite of those observations, Domoticz will display default value and not the primary controller value.
Steps to make Domoticz a secondary controller
- First you have to put the Master in full inclusion power mode, and then set Domoticz (through Hardware / your Z-Wave adapter) in 'receive configuration from other controler' after activating vera to include domoticz.
- For the Vera, the Domoticz Z-Wave adapter is recognized as a scene controller, but not well configured.
- Then the list of device will get transferred to the Domoticz server (Hint: making a heal from Vera may speed-up things).
To generate a random security key for your OpenZwave device you can use the following command from Linux, it requires pwgen to be installed
apt-get install pwgen
pwgen -s 16 1|od -A n -t x1|sed 's/ /,0x/g'|sed 's/,//'|sed 's/0x0a//'
0x46,0x6e,0x4c,0x75,0x4d,0x6f,0x6e,0x38,0x59,0x6b,0x55,0x6d,0x42,0x70,0x39,0x78
Alternatively you can take the output from this link, prefix it with 0x, remove spaces and separate with commas so it looks like the output above
Please note once you change your key, any devices already securely paired will be unable to communicate. you should do this BEFORE including secure devices.
- Domoticz API/JSON URL's, section 12
Retrieved from 'https://www.domoticz.com/wiki/index.php?title=Zwave&oldid=11351'
Popp
SKU: POPE700045
Quickstart
This is a secure Keypad for Europe . To run this device please insert fresh 4 * AAA batteries. Please make sure the internal battery is fully charged.
The device can run in two different modes determined by the way its included:
- Stand-Alone: Include a new device to the keypad using key 1
- Network Mode: Be Included into your central controller using key 4 (Central Controller is needed). This is equivalent to activating the Learn mode.The sequence is shown in the image below:
Enter Management mode by removing the back-cover (all LEDs will light up) - this will only work in factory default! Here is a quick overview of the commands in management mode:
- Include Node: MM-> 1 -> * (turns into Stand alone Mode)
- Exclude Node: MM-> 2 -> * (only in Stand alone Mode)
- Primary Shift: MM-> 3 -> * (turns into Network Mode)
- Include (as inclusion or secondary controller): MM-> 4 -> *(turns into Network Mode)
- Reset: MM-> 5 -> * for 10 seconds (keep * pushed for 10 seconds).
- Association Set: MM-> 6 -> * -> Group-Number (2,3) -> *, then wait for device NIF for 10 seconds
- Association Remove: MM-> 7 -> * -> Group-Number (2,3) -> *, then wait for device NIF for 10 seconds
- New User Code: MM-> 8 -> * -> NUMBER -> * -> PIN -> *
- Remove User Code: MM-> 9 -> * -> NUMBER -> *
- Wakeup: hit RING button
- Send Node Information Frame: Double click Bell button
- Test the control of an included Door lock (Stand Alone Mode only) : MM-> * -> 0000 -> *
- Firmware OTA: push ring quickly followed by *
Important safety information
Please read this manual carefully. Failure to follow the recommendations in this manual may be dangerous or may violate the law.The manufacturer, importer, distributor and seller shall not be liable for any loss or damage resulting from failure to comply with the instructions in this manual or any other material.Use this equipment only for its intended purpose. Follow the disposal instructions.Do not dispose of electronic equipment or batteries in a fire or near open heat sources.What is Z-Wave?
Z-Wave is the international wireless protocol for communication in the Smart Home. This device is suited for use in the region mentioned in the Quickstart section.
Z-Wave ensures a reliable communication by reconfirming every message (two-way communication) and every mains powered node can act as a repeater for other nodes (meshed network) in case the receiver is not in direct wireless range of the transmitter.
This device and every other certified Z-Wave device can be used together with any other certified Z-Wave device regardless of brand and origin as long as both are suited for the same frequency range.
If a device supports secure communication it will communicate with other devices secure as long as this device provides the same or a higher level of security. Otherwise it will automatically turn into a lower level of security to maintain backward compatibility.
For more information about Z-Wave technology, devices, white papers etc. please refer to www.z-wave.info.
Product Description
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.
Prepare for Installation / Reset
Please read the user manual before installing the product.
In order to include (add) a Z-Wave device to a network it must be in factory default state. Please make sure to reset the device into factory default. You can do this by performing an Exclusion operation as described below in the manual. Every Z-Wave controller is able to perform this operation however it is recommended to use the primary controller of the previous network to make sure the very device is excluded properly from this network.
Reset to factory default
This device also allows to be reset without any involvement of a Z-Wave controller. This procedure should only be used when the primary controller is inoperable.
Open the device, hit button '5', then keep button '*' pressed for 10 seconds. The blue LED will start flashing the last 5 seconds of the waiting time.
Safety Warning for Batteries
The product contains batteries. Please remove the batteries when the device is not used. Do not mix batteries of different charging level or different brands.
Installation
The device can be mounted on all flat walls or can also be simply put on a table. Due to the IP rating of 44 it can be used outside the house e.g. to operate the main door. Unscrew the little screw on the bottom side of the device to open the enclosure. the back side is mounted ot the wall using screws. There is an isolation foam provided for uneven wall backgrounds
The image above shows the main functions an buttons of the device.
The image above shows the main functions an buttons of the device.
The device has a standard operation mode to ring the bell and to apply key codes to operate a door lock or generate events in the central controller. All setup and management functions however are performed in a management mode. The management mode can be entered in two different ways:
- When you open the device (remove the backside cover) the management mode is activated if master user code (20) is not present. Otherwise only entering master user code(20) will activate management mode.
- Entering the key code #20 will enter the management mode even when the tamper switch is closed.
The keypad is powered by 4 standard batteries. Two of them always run in parallel therefore the device will work if only two batteries are inserted. However the lifetime will be 50 % only. The device can be powered by a 5V DC external power supply. Between the batteries there is a small connector for the external power supply. It is safe to keep the batteries inserted for fall-back.
Inclusion/Exclusion
On factory default the device does not belong to any Z-Wave network. The device needs to be added to an existing wireless network to communicate with the devices of this network. This process is called Inclusion.
Devices can also be removed from a network. This process is called Exclusion. Both processes are initiated by the primary controller of the Z-Wave network. This controller is turned into exclusion respective inclusion mode. Inclusion and Exclusion is then performed doing a special manual action right on the device.
Inclusion
2. Insert the batteries.
Exclusion
1. Open the housing.
2. If a management code has been assigned, enter the code.
2. If a management code has been assigned, enter the code.
Product Usage
![Random Random](/uploads/1/2/5/8/125869899/811644850.png)
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 immeditately 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 bell key will immeditately 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.
Stand Alone Mode
test of included stike lockTest of included bell switch | The purpose of the stand-alone mode is to use the keypad together with a door lock and a indicator device (Door bell, light switch ? to indicate bell ring). The keypad has two control groups (in Z-Wave language association group), one to control a door lock using key codes and one controlling the door bell using the bell key. So simplify the setup process the keypad will automatically place the first included door lock into the control group for door locks (#2) and the first included binary switch into control group for doorbell (#3). The two image sequences below show how to include a door lock (e.g. strike lock) and/or a a switch acting as door chime into a stand alone key pad. Hence to setup the keypad for simple door control, perform the following steps:
|
It is also possible to manage the keycodes to operate the door lock when being in the management mode. The image sequence shows how to do this.
|
Network Mode
The purpose of the network mode is to use the keypad as control device for the whole Smart Home.
This means that after including the keypad into the network of the central controller this very controller will receive event notifications for all actions performed on the keypad:
This means that after including the keypad into the network of the central controller this very controller will receive event notifications for all actions performed on the keypad:
- Entering a valid key code (Scene ID 20 is issued). Its possible to issue the key code number as scene ID by setting the configuration parameter #5 accordingly
- Hitting the bell button once: Scene ID 21
- Hitting the bell button twice within one second: Scene ID 22
- Entering a invalid key code : Scene ID 23
Generate Z Wave Network Key Random Generator
The central controller will see the keypad as a kind of remote control with various buttons (key codes and real buttons). Additionally the tamper switch status is reported to protect the device against tampering.Attention: If you use the keypad as device with Popp-Hub or any other Z-Way based controller you need ot install the app Keypad for
- managaging user codes
- accessing the usage history (keycodes entered, failed attempts)
Management
- In network mode the management of user codes can be done both locally on the keypad and using the central controllers Graphical User Interface. In case the central control offers a user interface for door lock management a history of valid and invalid key code entries can be accessed.
- While in network mode the keypad can also directly control door locks and bells using the association functions built in. Just include the door lock and the switch from your central controller and use the central controllers Z-Wave association management interface to place the lock in association group 2 and the bell switch in association group 3. Its also possible to use the key codes mentioned in the quick start to set and unset these associations.
Indications
- When the device is in standby no LED is on.
- Turning on management mode or activating the button for further button entry turns the blue LED on. Every recognized button push will turn off the blue background for a moment to confirm successful button press
- Depending on Configuation Parameter 6 the buzzer will sound to confirm any button press.
- The status LED indicates:
- Success: green blinks for one second
- Error: red blink for 3,5 seconds
- Learn Mode: blue/green are blinking constantly
- Next Menu: blue LED blinks for one second
- Waiting for user code: blue LED blinks fast
- Waiting for reset: blue LED blinks very fast
- Management Mode: green blinking slowly
- Inclusion/Exclusion: red/green LEDs are blinking constantly
Notifications
The device sends the following notifications to the central controller using Lifeline:
The device sends the following notifications to the central controller using Lifeline:
Generate Zwave Network Key Random Key
- Access Control (0x06): 'Manual code exceeds limits (0x13)'; Sent, when pin code entered is more then 10
- Access Control (0x06): 'Invalid User Code (0x14)';Sent, when entered pin code doesn?t exist
- Access Control (0x06): 'Keypad Unlock (0x06)'; Sent, when entered pin code is correct and door is opened. This command also encapsulates the USER_CODE_REPORT with the pin entered
- Access Control (0x06): 'All User Codes Deleted (0x0c)';Sent, when all pin codes arre removed by command from controller
- Access Control (0x06): 'Single User Code deleted (0x0d)';Sent, when new pin code is removed by command from controller, or manually on the keypad
- Access Control (0x06): 'New User Code added (0x0e)'; Sent, when new pin code is added by command from controller, or manually on the keypad
- Access Control (0x06): 'New User Code not added (0x0f)'; Sent, when after attempt to add new pin code, using keypad
- Burglar Alarm (0x07): 'Tamper Removed'; When keypad is unmounted and enclosure is opened
BASIC Command Handling
Basic Command Class is not supported and received Basic commands are ignored.
Known Problems
Association Group2 do not send DoorlockCC: Include the Popp Keypad second time again after door lock
Basic Command Class is not supported and received Basic commands are ignored.
Known Problems
Association Group2 do not send DoorlockCC: Include the Popp Keypad second time again after door lock
Node Information Frame
The Node Information Frame (NIF) is the business card of a Z-Wave device. It contains information about the device type and the technical capabilities. The inclusion and exclusion of the device is confirmed by sending out a Node Information Frame. Beside this it may be needed for certain network operations to send out a Node Information Frame. To issue a NIF execute the following action: Hit 0 plus * (Star Key) in Management Mode
Communication to a Sleeping device (Wakeup)
This device is battery operated and turned into deep sleep state most of the time to save battery life time. Communication with the device is limited. In order to communicate with the device, a static controller C is needed in the network. This controller will maintain a mailbox for the battery operated devices and store commands that can not be received during deep sleep state. Without such a controller, communication may become impossible and/or the battery life time is significantly decreased.
This device will wakeup regularly and announce the wakeup state by sending out a so called Wakeup Notification. The controller can then empty the mailbox. Therefore, the device needs to be configured with the desired wakeup interval and the node ID of the controller. If the device was included by a static controller this controller will usually perform all necessary configurations. The wakeup interval is a tradeoff between maximal battery life time and the desired responses of the device. To wakeup the device please perform the following action: hit Ring Key
Quick trouble shooting
Here are a few hints for network installation if things dont work as expected.
- Make sure a device is in factory reset state before including. In doubt exclude before include.
- If inclusion still fails, check if both devices use the same frequency.
- Remove all dead devices from associations. Otherwise you will see severe delays.
- Never use sleeping battery devices without a central controller.
- Dont poll FLIRS devices.
- Make sure to have enough mains powered device to benefit from the meshing
Firmware-Update over the Air
This device is capable of receiving a new firmware 'over the air'. The update function needs to be supported by the central controller. Once the controller starts the update process, perform the following action to confirm the firmware update: hit * (Star Key)
Association - one device controls an other device
Z-Wave devices control other Z-Wave devices. The relationship between one device controlling another device is called association. In order to control a different device, the controlling device needs to maintain a list of devices that will receive controlling commands. These lists are called association groups and they are always related to certain events (e.g. button pressed, sensor triggers, ..). In case the event happens all devices stored in the respective association group will receive the same wireless command wireless command, typically a 'Basic Set' Command.
Association Groups:
Group Number | Maximum Nodes | Description |
---|---|---|
1 | 10 | Lifeline |
2 | 10 | Door Lock Control |
3 | 10 | Ring Button Control |
Special Operations as Z-Wave Controller
As long as this device is not included into a Z-Wave network of a different controller it is able to manage its own Z-Wave network as primary controller. As a primary controller the device can include and exclude other devices in its own network, manage associations, and reorganize the network in case of problems. The following controller functions are supported:
Inclusion of other devices
Communication between two Z-Wave devices only works if both belong to the same wireless network. Joining a network is called inclusion and is initiated by a controller. The controller needs to be turned into the inclusion mode. Once in this inclusion mode the other device needs to confirm the inclusion - typically by pressing a button.
If current primary controller in your network is in special SIS mode this and any other secondary controller can also include and exclude devices.
To become primary a contoller have to be resetted and then include a device.
Turn into Management Mode, hit button 1 and confirm with * (Star Key)
Exclusion of other devices
The primary controller can exclude devices from the Z-Wave network. During exclusion the relationship between the device and the network of this controller is terminated. No communication between the device and other devices still in the network can happen after a successful exclusion. The controller needs to be turned into the exclusion mode. Once in this exclusion mode the other device needs to confirm the exclusion - typically by pressing a button.
Attention: Removing a device from the network means that it is turned back into factory default status. This process can also exclude devices from it's previous network.
Turn into Management Mode, hit button 2 and confirm with * (Star Key)
Shift of Primary Controller Role
The device can hand over its primary role to another controller and become secondary controller.
Turn into Management Mode, hit button 3 and confirm with * (Star Key). To update the network informsation from a primary controller please activate Learn mode.
This operation will replicate all network functions and the information about the nwetwork topology from this device to the new primary controller. If yoi want to update the network information in other controllers without handing of the primary function, just reinclude this other controller.
This operation will replicate all network functions and the information about the nwetwork topology from this device to the new primary controller. If yoi want to update the network information in other controllers without handing of the primary function, just reinclude this other controller.
Configuration Parameters
Z-Wave products are supposed to work out of the box after inclusion, however certain configuration can adapt the function better to user needs or unlock further enhanced features.
IMPORTANT: Controllers may only allow configuring signed values. In order to set values in the range 128 .. 255 the value sent in the application shall be the desired value minus 256. For example: To set a parameter to 200 it may be needed to set a value of 200 minus 256 = minus 56. In case of a two byte value the same logic applies: Values greater than 32768 may needed to be given as negative values too.
Feb 26, 2018 Private keys are simply extremely large and random numbers; Public Keys are (x, y) points on an Elliptic Curve, generated by using the Private Key as a scalar. The public and private key are not really keys but rather are really large prime numbers that are mathematically related to one another. Being related in this case means that whatever is encrypted by the public key can only be decrypted by the related private key. Once keys are generated, we can use ToXmlString or ExportParameters method to read the keys. The ToXmlString method returns key information in XML as a string. The method takes a Boolean parameter. If passed false, it returns public key only. If passed true, it returns both private and public pair. The following code snippet returns a public key. It also contains the public and private key for each of your bitcoin addresses. Your bitcoin private key is a randomly generated string (numbers and letters), allowing bitcoins to be spent. A private key is always mathematically related to the bitcoin wallet address, but is impossible to reverse engineer thanks to a strong encryption code base. How are pubkic and private keys generated. Dec 30, 2016 Private Key and public key are a part of encryption that encodes the information. Both keys work in two encryption systems called symmetric and asymmetric. Symmetric encryption (private-key encryption or secret-key encryption) utilize the same key for encryption and decryption.
Parameter 1: Door Lock Automatic Secure Timeout
After this time a CLOSE command is sent to the controlled door lock. On default no CLOSE command is sent assuming that the strike lock has its own timeout set
Size: 1 Byte, Default Value: 3
Size: 1 Byte, Default Value: 3
Setting | Description |
---|---|
0 - 127 | Seconds |
Parameter 2: Ring Button Press Basic Command OFF Timeout
After this time the Door Bell will receive an OF command regardless of the actuall button is pressed or not
Size: 1 Byte, Default Value: 3
Size: 1 Byte, Default Value: 3
Setting | Description |
---|---|
3 - 127 | Seconds |
Parameter 3: Ring Button ON Command
This value is sent into Association Group 3 when the door bell button is pressed.
Size: 1 Byte, Default Value: 255
Size: 1 Byte, Default Value: 255
Setting | Description |
---|---|
0 - 99 | Basic Set Command Value |
255 | Basic Set Command Value |
Parameter 4: Ring Button OFF Command
This value is sent into Association Group 3 when the door bell button is released or the timeout has reached.
Size: 1 Byte, Default Value: 0
Size: 1 Byte, Default Value: 0
Setting | Description |
---|---|
0 - 99 | Basic Set Command Value |
255 | Basic Set Command Value |
Parameter 5: Central Scene ID for User Codes
This parameter defines if different user codes shall cause individual or similar scene ID sent to the main controller.
Size: 1 Byte, Default Value: 1
Size: 1 Byte, Default Value: 1
Setting | Description |
---|---|
0 | Constant Scene ID 20 for all User Codes |
1 | Individual User Codes 1 .. 20 |
Parameter 6: Buzzer Confirmation
Size: 1 Byte, Default Value: 1
Setting | Description |
---|---|
0 | Disabled |
1 | Enabled |
Technical Data
Dimensions | 120x75x25 mm |
Weight | 230 gr |
Hardware Platform | ZM5101 |
EAN | 4251295700045 |
IP Class | IP 44 |
Voltage | 5V DC |
Battery Type | 4 * AAA |
Device Type | Keypad |
Generic Device Class | Portable Controller |
Network Operation | Portable Controller |
Firmware Version | 01.05 |
Z-Wave Version | 6.51.10 |
Certification ID | ZC10-17085733 |
Z-Wave Product Id | 0115.0100.0103 |
Frequency | Europe - 868,4 Mhz |
Maximum transmission power | 5 mW |
Supported Command Classes
- Sensor Binary
- Association Grp Info
- Device Reset Locally
- Central Scene
- Zwaveplus Info
- User Code
- Configuration
- Alarm
- Manufacturer Specific
- Powerlevel
- Firmware Update Md
- Battery
- Wake Up
- Association
- Version
- Security
- Door Lock
Controlled Command Classes
- Basic
- Door Lock
Generate Random Number
Explanation of Z-Wave specific terms
Generate Zwave Network Key Random Numbers
- Controller — is a Z-Wave device with capabilities to manage the network. Controllers are typically Gateways,Remote Controls or battery operated wall controllers.
- Slave — is a Z-Wave device without capabilities to manage the network. Slaves can be sensors, actuators and even remote controls.
- Primary Controller — is the central organizer of the network. It must be a controller. There can be only one primary controller in a Z-Wave network.
- Inclusion — is the process of adding new Z-Wave devices into a network.
- Exclusion — is the process of removing Z-Wave devices from the network.
- Association — is a control relationship between a controlling device and a controlled device.
- Wakeup Notification — is a special wireless message issued by a Z-Wave device to announces that is able to communicate.
- Node Information Frame — is a special wireless message issued by a Z-Wave device to announce its capabilities and functions.