Zigbee device constantly sends "Report Attribute"

[Surendra Amina]

Hi

We are encountering an issue with our Zigbee EVSE device where it continuously sends "Report Attribute" messages from the Manufacturing cluster. This behavior was observed after we updated the firmware to trim the Manufacturing cluster attributes from {A, B, C, D, E}  say to {C, D, E} say.
Attachments:

    Network-joining PCAP file. Log Inclusion in EVA network node id 58b0.pcapng

    Zigbee message exchange log during the issue. Constant Reporting after attribute is removed node id 58b0.pcapng

[Amanda Hsieh]

Hi, 

The Zigbee coordinator might send a "Configure Reporting" command to set up the conditions under which it should report its attributes to the Zigbee coordinator. This is part of the Zigbee attribute reporting feature, which allows a device to automatically report changes in its attributes to another device.  The "Configure Reporting" command is used to set up the conditions under which the device should report its attributes. This command is typically sent once to configure and enable the reporting. After it is configured, the device should automatically start sending the attribute report periodically. Therefore, you should investigate the coordinator and figure out why it sends a configure reporting command to the EVSE. 

-Amanda H.

[Surendra Amina]

Let me elaborate the situation
1. Firmware version X having Manufacturing cluster attributes from {A, B, C, D, E} is flashed to EVSE device (nrf5340) using JLINK. The entire flash area is erased out before flashing the firmware.
2. The device joins a coordinator
3. The new version Y (say) Manufacturing cluster attributes from {C, D, E} is updated using OTA.
4. When the device is rebooted with the new firmware it continuously sends "Report Attribute" . Kindly check the log shared earlier.

There is no change in these attributes. I suspect the issue might be because of ZBOSS NVRAM. if I erase the ZBOSS NVRAM using zb_nvram_erase() and re-include the device. I do not see continuous transmission of the messages.

[Amanda Hsieh]

Hi,

Surendra Amina said:

if I erase the ZBOSS NVRAM using zb_nvram_erase() and re-include the device. I do not see continuous transmission of the messages.

Please provide a sniffer log regarding this part. 

Regardless of what changes you have made to your EVSE, the attribute reporting happens as a result of the coordinator sending a configure reporting command to the EVSE, not because of anything the EVSE is doing. I don't know what causes the coordinator to send the configure reporting command, as this is related to how the coordinator is implemented, and not anything to do with the EVSE.

Here's from the "Configure Reporting Command" in the Zigbee spec:

So it's sent from a device (in this case the coordinator) because it wants the receiving device (EVSE) to automatically report attribute values. Since the EVSE was told by the coordinator to configure automatic attribute reports, that's exactly what it will do. Then you have the "Report Attributes Command"

Again, since the EVSE was told to configure reporting, it will send attribute reports.

Here are some of the relevant packets in their sniffer log:
Packet 325: Coordinator sends Configure Reporting command to EVSE for cluster 0xfee7 and attribute 0x0002

Packet 327: EVSE responds with Configure Reporting Response with status success. This means that attribute reporting has been configured and the EVSE will start sending attribute reports.

If you look at the other Configure Reporting commands, you will see that the coordinator also asks the EVSE to configure reporting for attribute 0x0003.

-Amanda H.

[Surendra Amina]

Sorry for the late reply. I got pulled in other stuff.
Please find the attached log. The joining starts at seq 7252.

We understand that the coordinator is configuring some of the reporting. However in this example the report doesn't have  attribute field 0x0002.

"Report Attribute" shall have Attribute field. It is missing in above example, I think. Please correct me if I am wrong.


Log Inclusion in EVA network node id 58b0 after zboss NVRAM reset.pcapng

[Amanda Hsieh]

Hi, 

You are correct that the report attribute command shall have the attribute field

You said that this happened after you removed some attributes from your manufacturing-specific cluster. It could be that there is something incorrect with the implementation of the manufacturer-specific cluster after the change.

Is it possible to share your code? What NCS version are you using?

I can make this case private to only share with us if it is needed.

-Amanda H.