Doing the calibration is not forcing you to abandon your scheduler…
I’m using Schedy in AppDaemon for that. It just restores the correct state if necessary. And it even has retries in case commands (or their responses) get lost. Happens quite often in my setup.
Here’s my automation for recalibration:
- id: '1579029042197'
alias: Thermostat Recalibration
description: ''
trigger:
- at: 09:00:00
platform: time
condition: []
action:
- data:
entity_id:
- climate.spirit_buero_heat
- climate.spirit_bad_dg_heat
- climate.spirit_bad_og_heat
- climate.spirit_kinderzimmer_heat
preset_mode: boost
service: climate.set_preset_mode
- delay: 00:00:15
- data:
entity_id:
- climate.spirit_buero_heat
- climate.spirit_bad_dg_heat
- climate.spirit_bad_og_heat
- climate.spirit_kinderzimmer_heat
service: climate.turn_off
- delay: 00:00:10
- data:
entity_id:
- climate.spirit_buero_heat
- climate.spirit_bad_dg_heat
- climate.spirit_bad_og_heat
- climate.spirit_kinderzimmer_heat
service: climate.turn_off
- delay: 00:00:30
- data:
entity_id:
- climate.spirit_buero_heat
- climate.spirit_bad_dg_heat
- climate.spirit_bad_og_heat
- climate.spirit_kinderzimmer_heat
service: climate.turn_on
- delay: 00:00:10
- data:
entity_id:
- climate.spirit_buero_heat
- climate.spirit_bad_dg_heat
- climate.spirit_bad_og_heat
- climate.spirit_kinderzimmer_heat
service: climate.turn_on
I doubled some service calls due to shitty zwave command reliability. Without it sometimes some of the thermostat were hanging on “off” sometimes which is not that fortunate.