Highlights
Schedule times can now come from input_datetime helpers or other time entities, so you can adjust a schedule from the UI or automations without editing YAML. The scheduler follows changes to these entities right away, and an offset lets you change the climate before or after an entity's time.
schedule:
# Heat 30 minutes before waking up
- time: input_datetime.wake_up
offset: "-00:30:00"
min_temp: 21
# Lower temperature at bedtime
- time: input_datetime.bedtime
min_temp: 17.5See Adjusting Schedule Times via UI in the README for details.
⚠️ Breaking changes
- Home Assistant 2026.1.0 or newer is now required.
Existing configurations, entity IDs and profile selectors keep working as they are, including selectors you renamed.
New
timein a schedule entry accepts aninput_datetimeortimeentity ID.input_datetimehelpers with both a date and a time are supported; only their time is used.- New optional
offseton schedule entries (for example"-00:30:00"). - If a time entity becomes unavailable, its schedule entry keeps using the entity's last known time.
- Changing a time entity only updates your climate entities when it changes which schedule entry is active, so manual changes aren't overridden for nothing.
- Log messages are prefixed with the scheduler they come from.
Fixes
- A scheduler that was off when Home Assistant restarted failed to load and disappeared until the next restart.
- Profile selectors no longer trigger the "sets an invalid entity ID" warning in recent Home Assistant versions, which would have stopped working in 2027.2.0.
- Schedulers without
climate_entitiesfailed on every update, even though the setting is documented as optional. - Schedulers now clean up their listeners when removed.