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 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.
v5.3
esp-zigbee-lib version.
1.5.0
esp-zboss-lib version.
1.5.0
Espressif SoC revision.
ESP32-H2
What is the expected behavior?
When receiving move-to type commands for level or color type changes, the stack sends
ESP_ZB_CORE_SET_ATTR_VALUE_CB_ID messages updating the relevant remaining time attribute, and
when the move has been completed, the stack should issue a final attribute update with the remaining
time set to zero.
What is the actual behavior?
When receiving move-to type commands, the stack sends ESP_ZB_CORE_SET_ATTR_VALUE_CB_ID messages
updating the relevant remaining time attribute, but when the move has been completed, it never calls back
with the remaining time set to zero so the application has no idea that the command has been completed
and what the final (level/color) value is.
Steps to reproduce.
Step
Step
Step
...
More Information.
No response
The text was updated successfully, but these errors were encountered:
github-actionsbot
changed the title
No attribute set callback(s) when remaining time attribute reaches zero
No attribute set callback(s) when remaining time attribute reaches zero (TZ-1170)
Sep 25, 2024
Answers checklist.
IDF version.
v5.3
esp-zigbee-lib version.
1.5.0
esp-zboss-lib version.
1.5.0
Espressif SoC revision.
ESP32-H2
What is the expected behavior?
When receiving move-to type commands for level or color type changes, the stack sends
ESP_ZB_CORE_SET_ATTR_VALUE_CB_ID messages updating the relevant remaining time attribute, and
when the move has been completed, the stack should issue a final attribute update with the remaining
time set to zero.
What is the actual behavior?
When receiving move-to type commands, the stack sends ESP_ZB_CORE_SET_ATTR_VALUE_CB_ID messages
updating the relevant remaining time attribute, but when the move has been completed, it never calls back
with the remaining time set to zero so the application has no idea that the command has been completed
and what the final (level/color) value is.
Steps to reproduce.
...
More Information.
No response
The text was updated successfully, but these errors were encountered: