Zigbee communication in depth
For example, the Thermostat cluster (0x0201) supports several attributes to represent information,
such as the LocalTemperature attribute (0x0000) to display the temperature in degrees Celsius. This
cluster also includes the Setpoint Raise/Lower command (0x00) to increase or decrease the
temperature by the specified amount.
Note
A cluster is a set of commands and attributes. The Zigbee Cluster Library specifies common
clusters that can be used by public or private profiles.
Clusters implement a client/server model and are directional:
Outbound: The client is the side that initiates the transaction and sends the message to the
n
server. For example, a switch that sends an on/off command.
Inbound: The server is the side that actually contains the attributes and performs the work.
n
For example, a light that knows if it is on or off and completes the transaction by turning on/off
when a command from the switch (the client) arrives.
Endpoints
We know a Zigbee node may have several application objects running on it. That is, our thermostat
product, which is a node in the Zigbee network, is controlling the temperature and showing some
information in its display, each of which is an application. But, how do we send some information to be
shown to the display application object within the node? How do we route messages arriving at the
node to the appropriate application?
Each application on the node must be uniquely identified. We do this with endpoints. Endpoints are
service points and define each application object running in the Zigbee node.
XBee® Zigbee® Mesh Kit
Zigbee Application Framework
152
Need help?
Do you have a question about the XBee Zigbee Mesh Kit and is the answer not in the manual?