INS14278-4
How to Use Certified Apps in Z-Wave 700
2019-03-22
| Building a more connected world.
Page 14 of 45
4.4
Libraries
This section introduces the different libraries available in the SDK 7.11. See [6], [9] for more
information.
Overall the SDK has 2 libraries: controller library and slave library. The controller library is used for
controllers running Z/IP Gateway and will not be used by end devices. The slave library is used by all the
Z-Wave certified applications for end devices.
The slave library can be configured for always on (mains powered) devices or for battery devices.
Always on Slave (AOS): End devices which are main powered. They are always listening and
act as repeaters in the network. Example usages are on/off switches.
Reporting Sleeping Slave (RSS): Battery operated devices, which remain in sleep mode until
they are triggered. Example usages are door/windows sensors and motion sensors.
Listening Sleeping Slave (LSS): Also known as a Frequently Listening Routing Slave (FLiRS). A
special variant of battery operated devices, which provide a mechanism to wake up the
device within one second, with battery drain very close to that of a fully asleep device. The
FLiRS device alternates between sleep mode and a partially awake mode in which it is
listening for a special wakeup beam signal at the rate of once per second. When the FLiRS
device receives this beam, it immediately fully wakes up. If the device does not hear a Beam
it goes back to full sleep for another period until it partially awakes again and listens for a
beam. It is this partially awake mode combined with the special beam that provides for
battery lives on par with fully sleeping devices while providing communications latencies of
around one second. Example uses are door locks.
4.5
Association Groups and Endpoints
An association is the creation of a logical connection between nodes. It provides the ability to instruct a
slave device to directly control other slave device(s) upon activation. A device must support at least one
association group (group 1), which is designated for “Lifeline Reporting" (as defined by the Z-Wave Plus
v2 Device Type, see [8]). Each group is responsible for controlling and/or reporting specific commands,
e.g. a temperature measurement. One group can hold multiple commands if needed.
Association Group Information (AGI) enables Machine-to-Machine interfacing as well as human user
interpretation of available association groups, thus eliminating the need for paper-based
documentation.
All device-centric events are mapped to the Lifeline group. This includes events such as Battery Low,
Tamper Alarm, and Device Reset Locally. The Lifeline concept allows a gateway to set up just one
association from a device to get all it needs.
In the example of a motion sensor, the sensor reading is mapped to the Lifeline group, while another
association group targets local application functionality such as turning on a lamp based on movement.
