Zigbee string attribute not being reported

[Fernando Fontes]

Hello,

I'm having an issue with attribute reports on change for the string data type.

I have my custom cluster created like the following:

typedef struct
{
    zb_uint8_t    machine_status; 
    zb_uint16_t   display_error;
    zb_char_t     machine_type[20];
} zb_zcl_common_measurement_attrs_t;

For the string attribute:

#define ZB_SET_ATTR_DESCR_WITH_ZB_ZCL_ATTR_MACHINE_TYPE_MEASUREMENT_VALUE_ID(data_ptr) \
{                                                                                           \
    ZB_ZCL_ATTR_MACHINE_TYPE_MEASUREMENT_VALUE_ID,                                     \
    ZB_ZCL_ATTR_TYPE_CHAR_STRING,                                                           \
    ZB_ZCL_ATTR_ACCESS_READ_ONLY | ZB_ZCL_ATTR_ACCESS_REPORTING,                            \
    (zb_voidp_t) data_ptr                                                                   \
}

All the other attributes are reporting fine, but the string attribute is only reported the first time, and not as soon as the value is updated. 

I'm also checking with Wireshark, that indeed the attribute is not reported.

Thanks for the support,

Regards,

Fernando Fontes

[Marjeris Romero]

Hi Fernando,

I am sorry for the late reply.

All the other attributes are reporting fine, but the string attribute is only reported the first time, and not as soon as the value is updated. 

 So the string character is not being reported at all? Can you send the sniffer trace file so I can see how does it look like when the string attribute is reported the first time?

Do you have problems when reading the attribute as well or is it just reporting? Can you show a sniffer trace when trying to read this attribute?

Best regards,

Marjeris

[Fernando Fontes]

Hi Marjeris,

It's just when reporting. I can read it without any issue.

I did some experiments and I find out that only string members up to 7 bytes + 1 byte of length can be reported. I don't understand why. Actually, I have also discovered this topic that relates to the same issue.

It seems to be an old issue....

Best regards,

Fernando Fontes

[Marjeris Romero]

Hi Fernando,

This could possible be a bug. I am investigating this.

[Marjeris Romero]

Just FYI, this bug has been fixed in Zigbee NCS v1.7.0. It will also be fix on a future release of nRF5 SDK for Zigbee updated with new ZBOSS version.

[Fernando Fontes]

Hi Marjeris,

Thank you for letting me know. How much time it will take for the next release of the nRF5 SDK for Zigbee?

Best regards,

Fernando