
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:
You can press the button once to wake up the sensor and send wakeup notification to
gateway. If press successfully, LED light will blink one time.
Quick trouble shooting
Here are a few hints for network installation if things dont work as expected.
1.
Make sure a device is in factory reset state before including. In doubt exclude before
include.
2.
If inclusion still fails, check if both devices use the same frequency.
3.
Remove all dead devices from associations. Otherwise you will see severe delays.
4.
Never use sleeping battery devices without a central controller.
5.
Dont poll FLIRS devices.
6.
Make sure to have enough mains powered device to benefit from the meshing
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.