RE: How to declare client poll control cluster in a Zigbee coordinator for an IAS zone device

Marte Myrvold — Thu, 15 Jul 2021 13:09:16 GMT

Hi Anusha,

If the callback ias_sensor_zcl_cmd_cb is not called, then it means that the device does not receive any ZCL commands, as when you register a callback with ZB_ZCL_REGISTER_DEVICE_CB, you set a callback to be used when the device receives ZCL commands, and you want the application to handle the commands in specific way. Does it enter the callback if you try to send other ZCL commands to the device? Do you have a specific case for ZB_ZCL_POLL_CONTROL_CHECK_IN_CLI_CB_ID in your callback function?

I see that you are using both ias_sensor_window_device_ctx_t and ias_sensor_device_ctx_t, and that only the latter is used later on, at least in the code you have shared here. Are these two different device contexts, and the sensor window device context is used somewhere else, or are they supposed to be the same? Besides this the code you have shared looks correct, and your clusters are declared correctly as far as I can see.

You can try to test if you are able to interact with the poll control cluster at all, if you have other devices you can use for this. This might not solve the problem, as you might be able to interact with it even if there is something wrong causing the other device to not find it, but you will at least be able to tell if other devices can find the cluster or not. If you have another DK or dongle, you can for example use the Zigbee CLI Agent example on the other device and send commands to the coordinator. After setting up the CLI agent, you can send commands such as a simple descriptor request, simple_desc_req, to get the simple descriptor of the device, which contains a list of in and out clusters. Then you will see whether the poll control cluster appears in the cluster lists or not. You can also try to read attributes of that cluster with zcl attr read.

Best regards,

Marte