You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have updated my IDF branch (master or release) and ESP Zigbee libs (esp-zboss-lib and esp-zigbee-lib) to the latest 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.
ESP-IDF v5.1.2
esp-zigbee-lib version.
1.0.7
esp-zboss-lib version.
1.0.7
Espressif SoC revision.
ESP32-C6
What is the expected behavior?
No crashes
What is the actual behavior?
After updating both zigbee libraries to version 1.0.7 and adding a call to esp_zb_zcl_command_send_status_handler_register the application crashes every time after about 21-22 read attribute requests have been sent with the backtrace shown below. It seems to happen when the transaction sequence number reaches ~21, and can be triggered by other types of requests as well such as esp_zb_zcl_on_off_cmd_req.
If I comment the esp_zb_zcl_command_send_status_handler_register line the crash will not occur. My command_send_status callback function is empty.
Example code for how I'm registering the callback and the mostly empty callback handler.
github-actionsbot
changed the title
Crash after registering esp_zb_zcl_command_send_status_handler
Crash after registering esp_zb_zcl_command_send_status_handler (TZ-511)
Dec 26, 2023
Answers checklist.
IDF version.
ESP-IDF v5.1.2
esp-zigbee-lib version.
1.0.7
esp-zboss-lib version.
1.0.7
Espressif SoC revision.
ESP32-C6
What is the expected behavior?
No crashes
What is the actual behavior?
After updating both zigbee libraries to version 1.0.7 and adding a call to
esp_zb_zcl_command_send_status_handler_register
the application crashes every time after about 21-22 read attribute requests have been sent with the backtrace shown below. It seems to happen when the transaction sequence number reaches ~21, and can be triggered by other types of requests as well such asesp_zb_zcl_on_off_cmd_req
.If I comment the
esp_zb_zcl_command_send_status_handler_register
line the crash will not occur. My command_send_status callback function is empty.Example code for how I'm registering the callback and the mostly empty callback handler.
Steps to reproduce.
esp_zb_zcl_command_send_status_handler_register
.esp_zb_zcl_read_attr_cmd_req
an additional time the application will crash.More Information.
No response
The text was updated successfully, but these errors were encountered: