Thermostat weekly schedule (TZ-1517)

[kiw-github]

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

[ANARHIST1984]

Same, how I can read schedule from Zigbee SDK?

[xieqinan]

@kiw-github ,

The SDK has a function esp_zb_zcl_thermostat_weekly_schedule_start(), what schedule algorithm does it perform?

The esp_zb_zcl_thermostat_weekly_schedule_start() function enables the thermostat weekly scheduler to set the next temperature from the schedule table by comparing the transition times.

⁃ What cluster attributes does it change and use in its work?

It is only related to the ESP_ZB_ZCL_ATTR_THERMOSTAT_OCCUPIED_COOLING_SETPOINT_ID and ESP_ZB_ZCL_ATTR_THERMOSTAT_OCCUPIED_HEATING_SETPOINT_ID.

⁃ Where does it get the time from?

The time is from the UTC time of system.

When changing a cluster attribute according to the schedule, how can I get an event about its change?

The callback registered with esp_zb_core_action_handler_register() will be triggered by the ESP_ZB_CORE_THERMOSTAT_VALUE_CB_ID event.

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()?

The current SDK (v1.6.2) only supports singleton mode for thermostat cluster.

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.

The esp_zb_zcl_thermostat_set_weekly_schedule_cmd_req() function can be used to configure the schedule table.

When the ESP32 is overloaded, the specified schedule is not saved in NVS. How can I implement saving the schedule?

The thermostat schedule table is required to be saved in the application. If the NVS space is insufficient, you will need to increase its size.