marcelveldt
commented
4 years ago Something like this perhaps ? https://github.com/marcelveldt/homeassistant-scheduler/tree/master/custom_components/schedules
- A schedule has a before and after property which can be filled with either time (e.g. 22:00:00) of a sun notation (sunrise + 01:00:00)
- A schedule also has a condition, which accepts templating. For example the state of the workday sensor must be true
- You can add/update/remove schedules through service calls.
- Schedules will be represented as binary sensor, so you can easily check for state in every script/automation etc.
- It would be pretty easy to add a frontend for this too.
- It would be pretty easy to create device automations based on the schedules so you'll have a generic solution for all hass components.
The good thing about it is that it would require zero core changes as this is done with building blocks that were already there.
Please have a look and test it if you like. If there's enough interest I can submit a PR to core.
nielsfaber
GamerClassN7
frenck
Triggered from: home-assistant/home-assistant/pull/21017
It would be useful to add a scheduler to the climate component, specially for the generic_thermostat platform. You can actually do this by using automations in HA, but this way the ui would be more user-friendly.
It should enable the user to set rules triggering temperature changes at certain hours and days of the week. It could also be useful to add a sort of timer to manual temperature changes (making them last 1h for example), but that should be optional and enabled in the component configuration.
This could be done as a standalone componenent (see PR at the beggining) or integrate the functionality into the climate component. The standalone component approach would make sharing a single schedule between different climate entities easier.