This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
SDK:simplelink_lowpower_f3_sdk_8_40_02_01
I am currently working on a Zigbee door lock project using the CC2340R5, where the Zigbee module acts as a node, and the gateway is provided by the customer. In the .syscfg file, I have set the poll period to 3000 ms. After successfully joining the network through the gateway, I used packet capture (sniffer) to observe that the Data Request frames were initially sent every 3 seconds. However, after some time, the device started sending Data Request frames more frequently — multiple times within 3 seconds, which causes the current consumption to increase.
In contrast, when I use my own configured CC2652 coordinator, the Data Request frames are sent evenly every 3 seconds.
I would like to know whether this issue is related to the coordinator, and how can I prove whether it's caused by the coordinator or not?
The attachments are the packages caught by me using 2652 as the coordinator and by the client's coordinator respectively
Hello ,
Did the customer follow step 6. from: Zigbee Fundamental Project Development?
"Once the bind is successfully confirmed using bind_device_cb, we can use ZB_ZCL_GENERAL APIs to configure reporting on the light. LIGHT_REPORTING_MIN_INTERVAL represents the minimum time delay before the on/off attribute is reported, whereas LIGHT_REPORTING_MAX_INTERVAL is the maximum allowed time."
Can you check that the following two lines of code are present and used?