ESP32-H2 reading or writing consumption is too high (TZ-306)

[diazmanuel]

Hello,

I am analyzing the consumption of the ESP32H2 when reading from an external device and I encounter the following consumption problem as seen in the image

So in this image you can see two problems: on the one hand, the type of replica that is observed and on the other hand, the excessive consumption that is maintained for a long time in 20ma. If we zoom in we see the following

In the zoom, 3 peaks are observed and then an almost constant consumption of approximately 20ma, but the response to the reading ends with those first 3 peaks. That is to say, the response to the data query is carried out with those 3 peaks and for some reason after that it remains at that high consumption for a long time.

Also perform a reading of several attributes with the same command, resulting in the following image.

In this image you can clearly see the 2 queries and you can also see the replica, but this replica is not a replica as was believed, because in this supposed replica you do not see the 2 data consumptions as in the other case.

Also here there is another case in which the chip generates 7 reports and after a moment this 20ma step signal appears as in the rest of the cases

The biggest drawback is not the replicas but the high consumption in each interaction with the zigbee layer, whether reading or writing (the operation of the reports with the low consumption methodology still needs to be verified), in addition, as I mentioned before, the response is received with the initial peaks that are seen in the image, and then it remains stuck at 20ma for some other reason, this for low consumption applications represents a serious problem, I would like to know how to solve it, or if they were able to replicate this problem in their tests

thanks

[kelin6]

@diazmanuel May I inquire about the environment in which you are running the Zigbee sleep example, such as the ESP-IDF commit and ESP-Zigbee-SDK version?

We are currently making modifications to the light sleep code internally, based on our latest internal code, our test results are as follows:

• Regarding what you mentioned about the type of replica, it pertains to sending a read attribute command, receiving a response, and sending APS ack/ack packets, which align with a transmit current of 110mA.

• The excessive power consumption issue within 20mA for long-term maintenance has now been resolved. Next, we will update ESP-IDF and ESP-Zigbee-SDK.

[diazmanuel]

Hello!
Thanks for the response, I'm glad to know the problem was found.

I leave you the data of the environment
ESP-IDF: release v5.1
ESP-ZIGBEE-SDK: 0.9.5

May I know when they estimate that these updates will be uploaded to solve the problem and be able to continue testing?

[kelin6]

@diazmanuel The fixed code has already been internally reviewed and merged. It should be visible on GitHub in about 1 to 2 weeks.

[kelin6]

@diazmanuel
Please update the ESP-IDF and ESP-Zigbee-SDK using the following environment:

• ESP-IDF branch: release/v5.1 (commit: 6b1f40b)
• ESP-Zigbee-SDK branch: main(commit: 41c7f14)

Hope this helps you.

[chshu]

@diazmanuel Please reopen if any follow up questions.