Dear Jim Lin
For reporting we have met the issue as below.
Refer to "ZigBee Cluster Library Specification" with "22.214.171.124 Report Attributes Command Frame Format"
You can see message as format: |ZCL header||Attribute report 1||Attribute report 2|....|Attribute report n|
Normally, we only meet only one attribute report format "|ZCL header||Attribute report 1|"
And Z3GatewayHost will parse reporting message and pulish to "zclresponse" mqtt message as BOTH of COMMAND and ATTRIBUTE process.
However, for multi of Attribute report, MAYBE Z3GatewayHost can parse this reporting message to COMMAND process only,
DON'T have ATTRIBUTE process, it mean that attribute update is missing :(
For clearly, please see the attachment.
So, could you please show me to fix this issue, or we can parse this reporting message mannually?
Note: simplicity sniffer CAN parse this reporting message correctly.
I just take a testing.
With Report Attributes Command Frame Format, I have do a testing and result as:
+ Reporting with "Destination Endpoint: 0x01" => "emberAfReportAttributesCallback" is Called
+ Reporting with "Destination Endpoint: 0xFF" => "emberAfReportAttributesCallback" is NOT Called
Can you tell me why? As I know, enpoint 0xff mean that "broadcast endpoint"
I check reporting message of 3rd party device.
I don't know why they report with destination endpoint is 0xff