Thermostat gets ACHTUNG: Sending OOM status (TZ-1438)

[damian-kurek-wizzdev]

Answers checklist.

• I have read the documentation ESP Zigbee SDK Programming Guide and tried the debugging tips, the issue is not addressed there.
• I have updated ESP Zigbee libs (esp-zboss-lib and esp-zigbee-lib) to the latest version, with corresponding IDF version, and checked that the issue is present there.
• I have searched the issue tracker for a similar issue and not found a similar issue.

IDF version.

5.1.5

esp-zigbee-lib version.

1.6

esp-zboss-lib version.

1.6

Espressif SoC revision.

esp32c6

What is the expected behavior?

It won't get oom

What is the actual behavior?

After sending raise/lower heat only 10 or -10 multiple times even when you get error that it is not possible to change temperature by 10 keep sending the message
ZBOSS: nwk/nwk_nlme.c:808 OOM state is detected. ACHTUNG: Out of memory!
ZBOSS: common/zb_bufpool_mult.c:1650 OOM! bufs allocated {21 i-o 38} max 80
ZBOSS: nwk/nwk_nlme.c:850 ACHTUNG: Sending OOM status
ZBOSS: nwk/nwk_nlme.c:850 ACHTUNG: Sending OOM status
ZBOSS: nwk/nwk_nlme.c:850 ACHTUNG: Sending OOM status
ZBOSS: nwk/nwk_nlme.c:850 ACHTUNG: Sending OOM status
ZBOSS: nwk/nwk_nlme.c:850 ACHTUNG: Sending OOM status
ZBOSS: nwk/nwk_nlme.c:850 ACHTUNG: Sending OOM status
ZBOSS: nwk/nwk_nlme.c:850 ACHTUNG: Sending OOM status
ZBOSS: nwk/nwk_nlme.c:850 ACHTUNG: Sending OOM status
ZBOSS: nwk/nwk_nlme.c:850 ACHTUNG: Sending OOM status
And zigbee stops responding. It is not possible to send anything to the device

Steps to reproduce.

1. Configure thermosta cluter
2. Send raise/lower command only one way e.g. raise by 10
3. When you get to the limit of what can be changed keep sending the command
4. You should get the error at some point
   ...

More Information.

No response

[damian-kurek-wizzdev]

It seems that I don't get a callback when raise lower is too low but callbacks get allocated. The same think happens when I increasethe temperature

[xieqinan]

Hi,

Some questions need to be clarified for this issue:

• How many raise/lower commands are being sent?
• What is the frequency of sending these commands?
• If the commands stop being sent, does the issue still occur?

If the commands are sent at a high frequency, you can call esp_zb_io_buffer_size_set() to improve the stack's throughput.

[damian-kurek-wizzdev]

On screenshot you can see when I get to 35 that is max temperature I stop getting callback, and deconz says invalid value, but I can keep clicking and sending the value after 32 it gets OOM
What is the frequency of sending these commands?
Frequency does not matter as long as you send it when the result value is outside of the max value ( or min value)
How many raise/lower commands are being sent? 32 I think happened 2 times after 32 out-of-range raises
If the commands stop being sent, does the issue still occur? No, when I send a command that raises/lower is in range

[xieqinan]

@damian-kurek-wizzdev,

I tried to reproduce your issue on my side, and everything seems to work fine. I might have missed something, so I’ve attached an example for you. Could you please modify it to create a reproducible example and share it with me?
test-thermostat.zip

[damian-kurek-wizzdev]

https://github.com/damian-kurek-wizzdev/zigbee