30
Controlled and Supported Command Classes
Command Class is a concept which describes how different Z-Wave devices should send commands to
exchange (request/report/analyze) device functionality data, for example, commanding devices to turn
On/Off, requesting temperature/humidity/voltage values from different sensors etc.
All commands are sent in a form of short frames with the following structure:
<Command Class ID>
<Command ID>
<Specific Command data>
There are strict instructions which must be followed regarding particular Command Classes, so Z-Wave
devices of different manufacturers can interact using these instructions without problems.
A device can support and/or control a given Command Class.
If a Command Class is supported, the node implements all the Command Class functionalities and it can
be set and read back by other nodes. When a Command Class is supported, the whole Command Class
has to be implemented.
If a Command Class is controlled, the node permits the exchange of data, the read function and/or set
other nodes supporting the Command Class.
Nodes controlling Command Classes may use only a subset of the commands within a Command Class
(for example, only Set commands). Even when using a Command Class partially for control, this usage
must comply with the Command Class requirements.
Slave nodes may also control Command Classes. For example, a Set Command sent to Association
Group destinations is a form of Command Class control.
When Command Class control is mandated by the Device Type, a controlling node must permit data
exchange, the read function and set other nodes using the given Command Class. The controlling node
must also be able to use all commands of the controlled Command Class.
An Association Command Class allows and defines communication between devices. It is also used for
adding or removing nodes to/from an association group.
An Association Group is a group of multiple devices that is treated as a single device and thus controlled
with a single command. Usually association groups unite similar devices as they all receive the same
command. Each association group must include the following information:
— A grouping identifier
— A maximum number of devices that can be added to the group
— A description of how the association group is used and/or triggered by the product
Associations can be created via a central controller or an End Point. When creating an End Point
association, the Association Set command is sent to the actual End Point; not to the Root Device
(Controller).
The device can have a fixed number of nodes in their association group (not more than 25).
Association group 1 is always reserved for the Z-Wave Plus Lifeline service, and it should not be assigned
for any other purpose. The actual Device Type of a given product specifies mandatory commands which
the device must be able to send to a Lifeline group destination. A manufacturer may add support for
additional commands that can be sent to the Lifeline group.
Summary of Contents for ZL-100
Page 1: ...ZL 100 The World s Smallest Hub Online version...
Page 38: ...37 security_2 Manual part of interview...
Page 43: ...42 Printed Quick Start Guide...
Page 44: ...43...