Currently we have Input Datetime, which is great for using it as automation trigger. For example in my home setup I have two Datetime inputs for opening covers/shutters in the morning - one for weekdays and another for weekends. And here comes the problem - what if I want to have a dedicated time for each day of the week. I need seven Datetime inputs and either a pretty complex automation trigger logic or seven different automation rules.
An “Input Schedule” (input_schedule) integration will solve this problem and could be used in lots of useful places, e.g. the most common scenario - weekly room thermostat schedules.
It’s really surprising such solution doesn’t exist right now. I see there were some 3rd party attempts, but nothing solid, mature or actually working.
tom_l
June 7, 2020, 2:54pm
2
Previous feature requests:
Really just a half-formed idea that… it could be a pretty powerful approach to scheduling… I just don’t know if it would be practical or possible within the constraints of how the interface would then have to write out the rules… I seem to feel the intuition that it wouldn’t be a super simple thing to accomplish. uTorrent is the only thing I have at hand that presents a UI exmaple to show what I have in mind…
for the purposes of brainstorming… imagine if this was for heating and cooling for a b…
Hi there,
Pretty a lot of people is surprised that there is no component in HA that allows user friendly setup of actions to be executed per week day. Basically some good looking and user friendly scheduler e.g. for thermostat control or other actions.
Someone proposed to use netatmo scheduler as an example: https://my.netatmo.com/app/energy?demomode=true
[image]
[image]
And I really like this design. I hope that one day we’ll get a new entity type in HA that will be represented with a GUI…
I’m looking for a simple GUI for quickly creating lighting automations with HA, something other than NodeRed, and more akin to the lighting/automation schedulers found in mainstream hub products like SmartThings, Lutron, Wink, Wemo, etc.
A GUI in which you can create a new automation, select your desired triggers, choose the devices to be controlled, duration, set some conditions or exceptions, etc. It wouldn’t have to be as flexible as NodeRed, but sufficiently flexible to meet most non-enthus…
etc… It is a populat request.
Plans for a core integration seem to have been put on hold:
PR:
home-assistant:dev
← bachya:scheduler
opened 11:03PM - 21 Nov 19 UTC
## Description:
This PR adds the base for the new `scheduler` integration (pe… r https://github.com/home-assistant/architecture/issues/148). This is just a first step: to limit the size of the PR, it does not include everything that would be needed for a full version (websocket commands, etc.) – all of that will come in future PRs.
**Related issue (if applicable):** fixes #<home-assistant issue number goes here>
**Pull request with documentation for [home-assistant.io](https://github.com/home-assistant/home-assistant.io) (if applicable):** home-assistant/home-assistant.io#<home-assistant.io PR number goes here>
## Example entry for `configuration.yaml` (if applicable):
```yaml
```
## Checklist:
- [ ] The code change is tested and works locally.
- [ ] Local tests pass with `tox`. **Your PR cannot be merged unless tests pass**
- [ ] There is no commented out code in this PR.
- [ ] I have followed the [development checklist][dev-checklist]
If user exposed functionality or configuration variables are added/changed:
- [ ] Documentation added/updated in [home-assistant.io](https://github.com/home-assistant/home-assistant.io)
If the code communicates with devices, web services, or third-party tools:
- [ ] [_The manifest file_][manifest-docs] has all fields filled out correctly. Update and include derived files by running `python3 -m script.hassfest`.
- [ ] New or updated dependencies have been added to `requirements_all.txt` by running `python3 -m script.gen_requirements_all`.
- [ ] Untested files have been added to `.coveragerc`.
If the code does not interact with devices:
- [ ] Tests have been added to verify that the new code works.
[dev-checklist]: https://developers.home-assistant.io/docs/en/development_checklist.html
[manifest-docs]: https://developers.home-assistant.io/docs/en/creating_integration_manifest.html
Discussion:
opened 05:16PM - 13 Feb 19 UTC
closed 01:33PM - 11 May 23 UTC
_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.
So, on to the simple addon solutions that are solid and working:
Hi everyone,
there is someone that wished to have a control panel to automate lights,switches and more?
Something where you can turn on/off a device at a specific time of day on specific days of the week?
I needed something like that, but I didn’t find anything around that was visual and easy to use.
So I’ve just created it on my own.
It calls “Simple Scheduler”
The idea is that it has to be simple, so that my wife could use it.
[logo]
It works with:
light
scene
switch
script
camera
c…
Hi All,
I have made a New addon to handle a simple week schedule to turn on or off the entities on Home Assistant.
You can set for every days of week a trigger based on time or sunset/sunrise + offset.
[main]
[edit]
I have taken the inspiration from SimpleScheduler Addon but for my necessity i have decided to write a new addon with more powerful features.
https://github.com/michelebossa/HA-Scheduler
Seend me a feedback.
Thanks.
Buy me a coffie
Changelog
0.16
FIX sun time fo…
Or the more complex non GIU Scheddy:
UPDATE: Schedy is of course stable and ready for use since December 2018, here are the docs .
Hi all,
For those not knowing what Heaty is: It’s a heating scheduler with quite a lot of powerful features developed by me. Here’s the link to a long thread about it that has grown over the last 10 months: Heaty - a flexible heating control, facilitating schedules and manual intervention
I’m just wanting to announce:
R.I.P. - Heaty is going to die.
No, seriously, I’ve decided not to develop Heaty an…
Thanks for the quick reply. Yes, I went thru these discussions and projects before I wrote this.
Unfortunately both projects you mention do not solve the problem. Simple Scheduler works with just ON/OFF values, so basically switches and lights. I’m out of luck with my covers/shutters automation. And it’s in PHP… Scheddy has no GUI whatsoever, which is the whole point here.
123
(Taras)
June 7, 2020, 4:17pm
4
If it’s “the whole point here” then you should probably describe the appearance of your proposed “input_schedule” integration.
Lau7
(Lau)
August 9, 2020, 7:57pm
5
Maybe this one posted today could be an option…
Scheduler integration for HA
Introduction
In my house I have quite some devices that I want to control based on the time and day. For a while I have been looking for an easy way to set up and manage the automations that control them. HA has lots of functionality, but some things (such as automations), are not as simple to use as I would like. So, I decided to create my own scheduler integration. With a mobile-friendly Lovelace card for managing it.
What is the scheduler integra…