SWRA615A June   2019 CC1352P , CC1352R , CC2530 , CC2531 , CC2538 , CC2652P , CC2652R , CC2652R7 , CC2652RB , CC2652RSIP

 

  1.   What's New in Zigbee 3.0
    1. 1 Overview
    2. 2 Zigbee PRO Specification
      1. 2.1 Child Device Management
      2. 2.2 Parent Announce Command
      3. 2.3 Trust Center (TC) Link Key Updates
      4. 2.4 Install Codes
      5. 2.5 Outgoing NWK Frame Counter
      6. 2.6 Changes to Network Joining
      7. 2.7 New Mandatory Command Support
      8. 2.8 Optional Distributed Networks
    3. 3 Base Device Behavior (BDB)
      1. 3.1 BDB Commissioning Modes
      2. 3.2 BDB Security
      3. 3.3 Reset Methods Available with BDB
    4. 4 Green Power Basic Proxy
    5. 5 Zigbee Cluster Library
    6. 6 Zigbee Application Architecture
      1. 6.1 Zigbee Node
      2. 6.2 Zigbee Cluster
      3. 6.3 Zigbee Device
    7. 7 Zigbee Lighting & Occupancy (ZLO) Device Specification
    8. 8 Zigbee 3.0 Certification
    9. 9 References
      1.      Trademarks

6.3 Zigbee Device

Each endpoint on a Zigbee node supports a Zigbee Device type. There are three device classes for Zigbee device types:

  • Node Class: Not to be confused with the previous definition of a Zigbee node, a node-class device defines an endpoint that represents the entire Zigbee node for some actions. An example of a node device endpoint would be the ZDO (Zigbee Device Object) endpoint, which is defined on endpoint 0 by the specification and is responsible for actions related to the logical Zigbee device type (ZC, ZR, ZED) like network commissioning, binding and discovery requests, and so on (all Zigbee networking-related actions). Another example of a node device endpoint would be the Green Power endpoint, which (if implemented) is defined on endpoint 242 and is another endpoint responsible for network actions. A Zigbee node can implement one or more node device endpoints and may or may not specify mandatory clusters.
  • Simple Class: The most common endpoints in typical Zigbee networks. Zigbee devices like sensors, actuators, lights, and switches, are all simple devices. A simple device specifies a set of mandatory application clusters within the ZCL specification. Simple device endpoints are only operational within a Zigbee network if a bind exists for that cluster on the corresponding endpoints, otherwise it is inactive.
  • Dynamic Class: This endpoint is typically found in gateway devices where there exists a higher level supervisory application above the simple device layer that can manage activities such as remote bindings, monitoring network statistics, and so on.