Zigbee networks
On/Off - Used to switch devices on or off (lights, thermostats, and so forth)
n
Level Control - Used to control devices that can be set to a level between on and off
n
Color Control - Controls the color of color capable devices
n
Each cluster has an associated 2-byte cluster identifier (cluster ID). All application transmissions
include the cluster ID. Clusters often have associated request and response messages. For example, a
smart energy gateway (service portal) might send a load control event to a load controller in order to
schedule turning on or off an appliance. Upon executing the event, the load controller sends a load
control report message back to the gateway.
Devices that operate in an application profile (private or public) must respond correctly to all required
clusters. For example, a light switch that operates in the home automation public profile must
correctly implement the On/Off and other required clusters in order to interoperate with other home
automation devices. The Zigbee Alliance has defined a Zigbee cluster library (ZCL) that contains
definitions or various general use clusters that could be implemented in any profile.
XBee modules implement various clusters in the Digi private profile. You can also use the API to send
or receive messages on any cluster ID (and profile ID or endpoint). For more information, see
Rx Indicator frame -
Endpoints
The APS layer includes supports for endpoints. An endpoint can be thought of as a running application,
similar to a TCP/IP port. A single device can support one or more endpoints. A 1- byte value identifies
each application endpoint, ranging from 1 to 240. Each defined endpoint on a device is tied to an
application profile. A device could, for example, implement one endpoint that supports a Smart Energy
load controller, and another endpoint that supports other functionality on a private profile.
No TX Status frame is generated for API frames that have both 0xE6 as the destination endpoint and
0xC105 as the Profile ID as this combination is reserved for internal XBee 3 Zigbee RF Module
operations.
Endpoints 0xDC - 0xEE are reserved for special use by Digi and should not be used in an application
outside of the listed purpose. The reserved Digi endpoints are:
0xE8 - Digi data endpoint
n
0xE6 - Digi device object endpoint
n
0xE5 - Secure Session Server endpoint
n
0xE4 - Secure Session Client endpoint
n
0xE3 - Secure Session SRP authentication endpoint
n
Zigbee device profile
Profile ID 0x0000 is reserved for the Zigbee device profile. This profile is implemented on all Zigbee
devices. Device Profile defines many device and service discovery features and network management
capabilities. Endpoint 0 is a reserved endpoint that supports the Zigbee device profile. This endpoint is
called the Zigbee device objects (ZDO) endpoint.
Zigbee device objects
The ZDO (endpoint 0) supports the discovery and management capabilities of the Zigbee device
profile. See the Zigbee specification for a complete listing of all ZDP services. Each service has an
associated cluster ID.
The XBee Zigbee firmware allows applications to easily send ZDO messages to devices in the network
using the API. For more information, see
Digi XBee® 3 Zigbee® RF Module
0x91.
ZDO
transmissions.
Zigbee application layers: in depth
Explicit
79
Need help?
Do you have a question about the XBee 3 ZigBee and is the answer not in the manual?