User Manual

CONFIGURATIONS
This product can be operated in any Z-Wave network with other
Z-Wave certified devices from other manufacturers. All mains operated
nodes within the network will act as a repeater, regardless ofvendor,
to increase the reliability of the network.
Association
Strips supports association group 1 (lifeline),
max 1 node, normally used to send Strips’
notification to the Z-Wave controller.
Tamper
Strips will send a tamper alert if it detects
that someone tries to wake up or
manipulate Strips.
A user command is successfully executed.
1 Long Blink
-User feedback during commands
-Successfully sent report
2 Short Blinks
The indication when Strips is not added to
a network.
Error (e.g. communication with controller
failed)
LEDNotifications(TableB)
5 Short Blinks
1 Short Blink
Factory Default
Reset
Wake Up
Place the controller into pairing or remove mode
and perform the "wake up" pattern described in the
first section of this manual.
You may need to reset Strips if your Z-Wave
controller is missing or not responding. Followthe
instructions for Wake Up above, but on the 3rd
repetition, keep the magnet at the rounded edge
for 10 seconds. A long LED signal indicates
success.
UserCommands(TableA)
Add/Remove
To wake up Strips manually for communication
with the Z-Wave controller, move the magnet
3 times according to the illustration above.
Execute user commands according to "Table A" by moving the magnet
according to the picture below.
User Command Sensor
For Command Classes and supported Notification Events please see: sensative.com/strips/Strips-Guard-700/
No Name Description Values Default
1
Notification
type (1 byte)
Select the notification type for the door and
window open or close events
0: Binary sensor report + Notification report
(Access Control)
1 : Notification report (Access Control)
2: Notification report (Home Security)
1
2
LED indication
(1 byte)
Turn On or Off LED for specific event indications
(ex. alarms)
0: Turns off LED for door open events
1:On
1
15
Activate
supervision
(1 byte)
Activate Supervision command for only
important alarm events or all events
*Supervised commands require a confirmation
from the gateway when a notification is received
0: Events sent with S2 Encapsulation only
1: Only Door Open Alarm Report (Events sent
with S2 and supervision encapsulation)
2: Unsolicited reports (Door Open/Close,Tamper
clear, Wake-up notification and Battery Report
events sent with S2 and supervision encapsulation)
1
22
Security Level
(1 byte)
Select the level of security
0: Standard (Forces parameter behavior
as follows: #16=10000, #17=Sensative
standard**, #18=0, #19=Off,
** Retries with an incrementally longer
period until reconnected
1: High Security (Enables parameters
16-19, #1=2, #15=2)
0
The below configurations are only used if parameter 22 is set to 1 (High security)
Parameters 16-19, 22 are categorized as ”Advanced Settings”
16
Supervision
wait time
(2 bytes)
The number of milliseconds to wait for a
Supervision response when a Supervised
message is sent
500-30000 (ms) 10000 (ms)
17
No. of failed
event retries
(1 byte)
Number of retries when a confirmation is not
received
0-5 1
18
Failed event
retry interval
(1 byte)
The minimum number of seconds between
retries
Min = 1 second, Max = 60 seconds 6 (seconds)
19
Heartbeat
interval
(1 byte)
Number of minutes between periodic battery
reports (Heartbeats)
5 - 70 (mins)
- Accepts multiples of 5 mins.
- Any arbitrary value in between 5 and 70
will be rounded up to a multiple of 5
70 (mins)
ConfigurationTable