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.
- 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).
Device Type | Server Cluster ID | Server Clusters | Client Cluster ID | Client Clusters |
---|---|---|---|---|
Combined interface | 0x0000 | Basic | 0x0000 | Basic |
0x0003 | Identify | 0x0003 | Identify | |
0x0004 | Groups | 0x0004 | Groups | |
0x000A | Time | 0x0005 | Scenes | |
0x0501 | IAS ACE | 0x0006 | On/Off | |
0x0008 | Level control | 0x0009 | Alarms | |
0x0300 | Color control | 0x0201 | Thermostat | |
— | — | 0x0202 | Fan control | |
— | — | 0x0406 | Occupancy sensing | |
— | — | 0x0400 | Illuminance measurement | |
— | — | 0x0402 | Temperature measurement | |
— | — | 0x0204 | Thermostat UI | |
— | — | 0x0405 | Water content measurement | |
— | — | 0x0500 | IAS 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.