Fair enough. Just wanted to point out the difference as sometimes it does matter.
Your heating control is HUGE…
2 Likes
Np lol, also whenever you do getelementby[name,I’d etc] you could use jquery
1 Like
+1 for this. That would make it far more powerful.
That said, it is awesome already
1 Like
The Automation bit is normally hidden in a folded row.
Having said that… all the time entities would disappear with access to automations by this addon.
Version 0.08 released!
Now the addon supports this components:
- light
- switch
- script
- camera
- climate
- automation
- media_player
- scene (experimental)
You can disable some of those components from configuration if you don’t need them and you prefer to reduce the length of the dropdown list. Just set the component you don’t need to to false.
Probably you will have to rewrite the translations in the configuration… sorry about that… I thought that items should be re-arranged with the new parameters.
5 Likes
fantastic, great addon, will try now.
Ok, installed so far so good.
A couple of requests:
Maybe split the selection in light, switch, and so on, for those who have a long list of devices (this is minor)
Put the sunrise and sunset options, instead of the time
1 Like
for non sophisticated people, like me, this addon is way way way simpler then Shedy, which I try toi install but was far from easy to understand (for me at least)
3 Likes
Hi, climate should be more of temperature rather then ON-OFF. Nevertheless I started to bring lots of automation to your scheduler. Big thanks
2 Likes
where is it? I couldn’t find anything (0.08) just down the add-on page.
One improvement request: I really like the way input_datetime handles input (hours and minutes separately) and I believe it would be great to implement.
p.s added a new issue on Github 
After reading what is planned for the official addon (scene control only) I don’t think your addon will become useless at all.
1 Like
This was already in my mind. I think that the dropbox is really messy, but the HTML dropbox is limited. I have to replace with a javascript one, maybe with icons and column.
By the way, starting from 0.08 they are sorted by components. Better than nothing… 
Yes sorting is good, overall is ittle messy, but enough for a start.
In addition to time would be great sunrise and sunset options (with offset)
Hi,
Any chance to be able to install this as a separate container in docker for those who are not using hassio?
The dockerfile doesnt specifically relate to hassio so you could build based on that dockerfile
Version 0.10
-
Added support for input_boolean
-
Grouped entities in the dropdown
2 Likes
That seems really sad.
With the new updates this add-on is now killer and any official integraton / add-on should have these same abilities
2 Likes
The scheduler uses a scene as a container for other entities.
- The scene defines what must be turned on/off, temperature/volume increased/decreased, etc.
- The scheduler activates the scene at the appointed time.
It’s a clear separation of responsibilities plus the scene remains accessible (for activation) by other automations (for activation outside of its regular schedule).
2 Likes
I tend to use scripts anyway, but I thought there was a general move away from scenes towards scripts regardless.
What about people who use scripts, I’d be sad about that. 
I hope you mean that the engine uses scenes internally to achieve the result rather than requiring us to only control scene entities. Otherwise we would need to create a scene to turn on a light… I can see the benefit of a scene for complex things (ie: lots of lights, switches etc all being controlled at once) but for something simple we would want direct control of the entity, not via a scene
1 Like
I saw something like “let’s make scenes first-class citizens” from balloob in one of the PRs not long ago.
My bigger worry is the move from trigger automations to device automations but I haven’t looked into it yet.
1 Like