6.2.4 Reporting

As a client, the device is capable of making device discovery, service discovery, binding or network management requests. As a server, the device services these requests and responds to them. The client and server roles are non-exclusive, and a given device can act as both client and server.

The device profile describes devices in one of two configurations:
  • Client – Issues requests to the server via device profile messages
  • Server – Issues responses to the client that initiated the device profile message

The following table provides details about the client/server clusters available for the combined interface device type in the Microchip Zigbee stack. For more details, refer to the ZigBee Alliance Cluster Library Specification Revision 8 (075123). For more details regarding mandatory or optional clusters for a specific device type, refer to the Matter Device Library Specification (1.0).

Note: The combined interface device type is only supported in the Microchip Zigbee stack.
Table 6-1. Supported Clusters – Combined Interface
Device TypeServer Cluster IDServer ClustersClient Cluster IDClient Clusters
Combined interface0x0000Basic0x0000Basic
0x0003Identify0x0003Identify
0x0004Groups0x0004Groups
0x000ATime0x0005Scenes
0x0501IAS ACE0x0006On/Off
0x0008Level control0x0009Alarms
0x0300Color control0x0201Thermostat
0x0202Fan control
0x0406Occupancy sensing
0x0400Illuminance measurement
0x0402Temperature measurement
0x0204Thermostat UI
0x0405Water content measurement
0x0500IAS zone

In this scenario, the coordinator/combined interface is configured as a target endpoint; therefore, the coordinator device does not report any attributes. It monitors the attributes reported by routers/end devices.