Zigbee Reporting Attribute size bug?

[Glenn Ivar Klausen]

I have an application where I have configured a reporting attribute which reports on update. It works as expected - until the amount of data you want to send exceeds 8 bytes. 

The is ZB_ZCL_ATTR_TYPE_CHAR_STRING. In this type the first byte is a length character, and a \0 (zero termination) has to be included. That leaves a payload of 6 chars. In my case I need to send a variable sized sting between 11 and 25 char long. 

Due to the limitation I have run into, it has to be sent in chunks of 6 chars, but what is the reason for this limitation? I can't find anything about it in the ZBOSS doc or ZB spec. 

Is it a bug?

How can I fix this?

[Glenn Ivar Klausen]

Any updates on this one?

It is straight forward to test, so there is not need for sniffer logs. Anyone can reproduce this.

Is it possible to get an intermediate update with a fix?

[Marjeris Romero]

Hi Glenn,

I am sorry for the late reply, but this bug has now been resolved in NCS v.1.7.0. We have also a plan to have a new official release of nRF5 SDK with a new ZBOSS version, in the first quarter of next year. I know it's quite far from now, but if you are not able to migrate to NCS, the best option is to wait for this fix.