Minimum and Maximum Attribute Reporting Time.

RE: Minimum and Maximum Attribute Reporting Time.

Edvin — Thu, 14 Nov 2019 07:54:08 GMT

Hello Darren,

This should be fixed since SDK3.0.0 (so yes, it is fixed in SDK3.2.0)

Best regards,

Edvin

RE: Minimum and Maximum Attribute Reporting Time.

WestCoastDaz — Thu, 14 Nov 2019 03:52:31 GMT

Section 2.5.7.1.5 of the ZCL specification states that 0x0000 is valid. It says

If this value is set to 0x0000, then there is no minimum limit, unless one is imposed by the specification of the

cluster using this reporting mechanism or by the application.

Do you know if this was fixed in SDK 3.2?

RE: Minimum and Maximum Attribute Reporting Time.

IanAber — Tue, 26 Mar 2019 13:58:19 GMT

The coordinator I am using is a Samsung SmartThings hub. It is possible to set the reporting interval to a custom value by creating a custom device handler but the default values that the hub sends are minimum = 0 and maximum = 600. I searched through all the device handlers in thir library and could not find any that set the minimum to 1 suggesting that the majority of devices use 0.

I have now written a handler for the hub setting the reporting interval from 1 to 600 and it is now reporting correctly but it seems odd that 1 would be the default minimum for the ZBOSS stack.

RE: Minimum and Maximum Attribute Reporting Time.

Edvin — Tue, 26 Mar 2019 11:53:44 GMT

Hello,

ZB_ZCL_MIN_REPORTING_INTERVAL is used by the Zigbee Stack. I am not sure whether it is possible to set this any lower than 1. I have to check with our Zigbee Team. It your coordinator a 3rd party device? And this uses reporting interval of 0 by default?