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
The SDK has a function esp_zb_zcl_thermostat_weekly_schedule_start(), what schedule algorithm does it perform?
⁃ What cluster attributes does it change and use in its work?
⁃ Where does it get the time from?
When changing a cluster attribute according to the schedule, how can I get an event about its change?
If the device has several endpoints from thermostat clusters, how can I specify which endpoint to work with when starting esp_zb_zcl_thermostat_weekly_schedule_start()?
According to the SDK, there is a schedule reading function esp_zb_zcl_thermostat_weekly_schedule_get_next_record(), but there is no function that sets this schedule from a program and not via ZigBee.
When the ESP32 is overloaded, the specified schedule is not saved in NVS. How can I implement saving the schedule?
Additional context.
No response
The text was updated successfully, but these errors were encountered:
Question
The SDK has a function esp_zb_zcl_thermostat_weekly_schedule_start(), what schedule algorithm does it perform?
⁃ What cluster attributes does it change and use in its work?
⁃ Where does it get the time from?
When changing a cluster attribute according to the schedule, how can I get an event about its change?
If the device has several endpoints from thermostat clusters, how can I specify which endpoint to work with when starting esp_zb_zcl_thermostat_weekly_schedule_start()?
According to the SDK, there is a schedule reading function esp_zb_zcl_thermostat_weekly_schedule_get_next_record(), but there is no function that sets this schedule from a program and not via ZigBee.
When the ESP32 is overloaded, the specified schedule is not saved in NVS. How can I implement saving the schedule?
Additional context.
No response
The text was updated successfully, but these errors were encountered: