ZigBee "Read Attributes" bug

[Alex_T]

Hello,

I recognized a wrong answer is sent by the ZigBee stack of nRF Connect 1.5.1 and 1.7.0 (and others).

Eg. the application provides a color control cluster as a server.

Whenever a device reads attributes from this server with unsupported attributes included first in the read-attribute-command, then the answer will be wrong.

The first unsupported attributes are reported correctly as unsupported but the next supported attribute will be reported twice. First correctly as supported but additionally in the same packet as unsupported. Screenshot is provided.

In "zb_zcl_general_commands.c" in "zb_zcl_read_attr_handler_continue" the "status = ZB_ZCL_STATUS_SUCCESS;" should be set at the beginning of the loop - not before the loop.

Best regards,

Alex

[Marte Myrvold]

Hi Alex,

Thank you for reporting this. I have forwarded it to the developers.

Best regards,

Marte

[Marte Myrvold]

Hi Alex,

I just want to inform you that our developers have reported the bug to DSR, who are responsible for the stack.

Best regards,

Marte

[Marte Myrvold]

Hi Alex,

DSR has created a fix for this. I do not have information on when a version of the stack with this fix will be released, but hopefully in not too long.

Best regards,

Marte

[Alex_T]

Hi Marte,

Thank you for the feedback. I am now in contact with our local sales about the release-timeline.

Best regards,

Alex