Unable to configure attribute reporting on custom cluster

RE: Unable to configure attribute reporting on custom cluster

Isaia F — Wed, 15 Dec 2021 07:35:29 GMT

That did it, thank you.

This should be added to the guide however as i don't think there is any reference to this in the documentation.

RE: Unable to configure attribute reporting on custom cluster

Marte Myrvold — Tue, 14 Dec 2021 10:50:56 GMT

Hi Isaia,

Sorry for the delay.

It seems like you have forgotten to add the reporting context to your shaker device. You need to declare the context with ZBOSS_DEVICE_DECLARE_REPORTING_CTX and add the number of reporting attributes on the device to the endpoint descriptor:

#define ZB_HA_DECLARE_SHAKER_EP(ep_name, ep_id, cluster_list)                                    \
  ZB_ZCL_DECLARE_SHAKER_SIMPLE_DESC(ep_name, ep_id,                                              \
      ZB_HA_SHAKER_IN_CLUSTER_NUM, ZB_HA_SHAKER_OUT_CLUSTER_NUM);                                \
      ZBOSS_DEVICE_DECLARE_REPORTING_CTX(reporting_info## device_ctx_name,                       \
                                     ZB_HA_SHAKER_REPORT_ATTR_COUNT);                            \
  ZB_AF_DECLARE_ENDPOINT_DESC(ep_name, ep_id, ZB_AF_HA_PROFILE_ID, 0, NULL,                      \
                          ZB_ZCL_ARRAY_SIZE(cluster_list, zb_zcl_cluster_desc_t), cluster_list,  \
                              (zb_af_simple_desc_1_1_t*)&simple_desc_##ep_name,                  \
                              ZB_HA_SHAKER_REPORT_ATTR_COUNT, reporting_info## device_ctx_name,  \
                              0, NULL) /* No CVC ctx */

Define ZB_HA_SHAKER_REPORT_ATTR_COUNT to be the number of attributes your device should report.

Best regards,

Marte

RE: Unable to configure attribute reporting on custom cluster

Marjeris Romero — Fri, 10 Dec 2021 13:19:16 GMT

Hi,

I am so sorry for the late reply. I have forwarded this case to one of our Zigbee experts who will take a closer look at this soon.

RE: Unable to configure attribute reporting on custom cluster

Isaia F — Mon, 06 Dec 2021 09:06:30 GMT

Addendum: the commands sent via CLI to subscribe to the reported attribute and relative responses, if they can be of any use

uart:~$ bdb role zc
Zigbee stack has been configured in the past.
Please use the same role or disable NVRAM to change the Zigbee role.
Coordinator set
Done
uart:~$ bdb start
Started coordinator
Done
[00:00:13.114,746] <inf> zigbee_app_utils: Production configuration is not present or invalid (status: -1)
[00:00:13.115,936] <inf> zigbee_app_utils: Zigbee stack initialized
[00:00:13.158,203] <inf> zigbee_app_utils: Joined network successfully on reboot signal (Extended PAN ID: f4ce36bc41dcdf74, PAN ID: 0x6012)
uart:~$ zdo mg
  mgmt_bind   mgmt_leave  mgmt_lqi
uart:~$ zdo mgmt_lqi 0000
[idx] ext_pan_id       ext_addr         short_addr flags permit_join depth lqi
[  0] f4ce36bc41dcdf74 f4ce364145c4c951 0x2541     0x15  0           1   172
ZDO request 1 complete
Done
uart:~$ zdo bind on f4ce364145c4c951 10 f4ce36bc41dcdf74 64 0xabcd
on: wrong parameter count
on - Create bind entry.
     Usage: on <h:source_eui64> <d:source_ep> <h:destination_addr>
     <d:destination_ep> <h:source_cluster_id> <h:request_dst_addr>
uart:~$ zdo bind on f4ce364145c4c951 10 f4ce36bc41dcdf74 64 0xabcd 0x2541
Done
uart:~$ zcl subscribe on 0x2541 
on: wrong parameter count
on - Subscribe to an attribute.
     Usage: on <h:addr> <d:ep> <h:cluster> <h:profile> <h:attr_id> <d:attr_type>
     [<d:min_interval (s)>] [<d:max_interval (s)>]
uart:~$ zcl subscribe on 0x2541 10 0xabcd 0x0104 0x0001 16
Error: Unable to configure attribute 1 reporting. Status: 1

Error: One or more attributes reporting were not configured successfully[00:01:59.041,778] <inf> zigbee.eprxzcl: Received ZCL command (0): src_addr=0x2541(short) src_ep=10 dst_ep=64 cluster_id=0xabcd profile_id=0x0104 cmd_dir=1 common_cmd=1 cmd_id=0x07 cmd_seq=0 disable_def_resp=1 manuf_code=void payload=[01000100] (0)