User`s manual

44
ZCL Reporting and Device Activity
If ZCL attribute reporting is configured on the gateway to expect reports from an active
remote device, and that device has not sent a report within the configuration’s timeout
setting, the reporting configuration will be resent to the remote device. The remote
device may have had a power loss or other fatal error and so lost its reporting
configuration.
ZCL attribute reports will not be sent to a device which is inactive.
The gateway also supports a simulated reporting mode called “pseudo reporting”.
Pseudo reporting acts like normal ZCL reporting, but instead of sending a Reporting
Configuration to the remote device, the gateway will send periodic reads instead. The
gateway keeps track of previous read values and will send an attribute_report RPC
response (see “attribute_report” on page 83) using the min/max reporting interval and
delta change, as if the remote device had been configured with reporting. This allows
you to use the reporting interface on devices that do not support reporting. The gateway
sends a read to the remote device every Min Reporting Interval. Pseudo reporting is
enabled by setting the pseudo_reporting tag to TRUE in the start_receiving_reports RPC
request (see “start_receiving_reports” on page 82).