Simple Scheduler Addon

[broken.pipe]

what might be interesting would be to define sunrise and sunset as time. but i don’t know if this is possible with static json files.

[tom_l]

Nicely done!

@ArthurDent1975

it lists all entities that starts with switch. * and light. *

I’d like to respectfully request if this could be expanded to include input_booleans and automatons as well?

[ArthurDent1975 (Alessandro A.)]

Simple Scheduler Addon

thanks a lot for this app! your next beer is paid … i just automated all the switches on the road and removed the previous automation. really good would be thermostats. from when to when to heat, in which mode (heat, auto, off). so just the basics. i tried schedy, but it really lacks a graphical user interface. i really like your user interface for the switches … clean and well arranged.

Thank you so much!!!

Simple Scheduler Addon

what might be interesting would be to define sunrise and sunset as time. but i don’t know if this is possible with static json files.

You hit the point!
I put the word simple in the name for a reason…
By the way… you can never say…

[ArthurDent1975 (Alessandro A.)]

Simple Scheduler Addon

I tried the addon. For the first, it is working fine. i got a few ideas for improvements for you. At first, as i said, conditions and supporting climate entitites. Then it would be nice if i can turn on or off the schedule with the slider on the left. Not going into edit to disable it. It also would be nice to select more than one entity. So if I may have a group of lights, I dont need a seperate schedule for each of them. Then you can change the checkboxes in the edit view to the same circ…

Oh my, there’s a lot of stuff in here…
Ok, let’s see…

Disable slider: well, you problably didn’t consider the mobile version. My wife only use the android app. It would be easy to tap on that by mistake. I even remove the icon in mobile view (the row become dimmed, so it is clear to understand).

Checkbox: Yes, that was my first idea. But it requires some javascript and a little effort to achieve that. It was easier this way. I primarly focused on the functionality. But it is in my mind.

More entities: I’m not sure it would be cozy. It would also make the editing more tricky and give user more chance to make a mess.

Condition: That’s far away from the pourpose of this addon. I never stop repeating that it has to be simple. Conditions are greatly implemented in HA, and they are mented for advanced user. You set the rule, you (mostly) never touch it again. This addon want to add something that was missing in HA, for (almost) everyday use. Last but not the least, Implement a condition engine in the addon would be very very very very complicated. (Did I say very?). I hope you will get my point

Simple Scheduler Addon

Great work… Any future plans to add cover.XXXX_level or cover.XXXXX_switch?

I call service.turn_on and service.turn_off which works for both switches and lights.
Covers have different services (service.open_cover, service.close_cover, and so on)
This would require a major change in code…

Simple Scheduler Addon

Nicely done! I’d like to respectfully request if this could be expanded to include input_booleans and automatons as well?

Thanks for the respect!
You can find your answers as for the above quote

[123 (Taras)]

Thank you for sharing this useful addition to Home Assistant. I don’t want to discourage further development but feel you should know that there is work underway to develop a scheduling integration.

To be clear, discussion started a year ago and it’s unknown how much more time is needed before it is ready to be released. In addition, it is the engine and not the accompanying UI that must also be developed to allow user’s to interact with the engine. Therefore it may be some time before we see anything that looks like the add-on you’ve created (but it will be released eventually).

[AhmadK (akasma74)]

@tom_l

I’d like to respectfully request if this could be expanded to include input_booleans and automatons as well?

You need to be careful with your wishes because if you simply call homeassistant.turn_on/turn_off service it might end up like this

tl;dr for automations it should be automation.trigger service rather than homeassistant.turn_on/off

[ArthurDent1975 (Alessandro A.)]

Simple Scheduler Addon

Thank you for sharing this useful addition to Home Assistant. I don’t want to discourage further development but feel you should know that there is work underway to develop a scheduling integration. To be clear, discussion started a year ago and it’s unknown how much more time is needed before it is ready to be released. In addition, it is the engine and not the accompanying UI that must also be developed to allow user’s to interact with the engine. Therefore it may be some time before we see a…

Thank you for your advice.
I needed the scheduling right now, so I created it by myself.
It tooks me a week of work and it gave me the chance to understand a lot of things under the hood about HA, starting from docker.
When the scheduler integration will be ready, this addon will become useless.
In the meanwhile, I hope it helps the community!

Thanks again!

[Se7enair]

Just a few things which come in mind when I tested.

You are right, the name says “simple”. So if you want to keep it simple, its already perfect.

More entities or conditions got the potential to make it a “difficult Scheduler”. But if you want to expand the capabilities of your addon, just put my notes to a future feature list and think about it
Or you can make a second addon. A simple scheduler and a universal scheduler.

[Sabuto (Robert Dunne)]

I really like this, and it’s written in php so bonus. Would you be willing to accept pr’s?

[ArthurDent1975 (Alessandro A.)]

Hi @Sabuto
I’m kinda new to all this git world. (It took me 5 minutes to understand your question )
I have to learn it because of this project.
I’m not a corporate programmer (maybe I’m not a programmer at all), so I’m not familiar with team working.
Please, don’t get me wrong, I’m still not prepared to this.

What would be your idea of improvement?

[Sabuto (Robert Dunne)]

So looking through the code you use jquery but only on the tooltip. I would probably change out the rest to use jquery (just for readability). I would also be happy to implement some of the ideas other have had with the different things like climate etc

Also just out of interest why do you pull the python image?

[ArthurDent1975 (Alessandro A.)]

Simple Scheduler Addon

So looking through the code you use jquery but only on the tooltip. I would probably change out the rest to use jquery (just for readability). I would also be happy to implement some of the ideas other have had with the different things like climate etc Also just out of interest why do you pull the python image?

JQuery is there not just for tooltip. I planned to use Datatable to sort columns and to use rounded toggle buttons instead of checkboxes. Being this just esthetics, I postponed.

The python image is a mistake due to laziness . The first version of the scheduler engine was in python and I didn’t want to rewrite it. But I was having trouble running it in docker along with PHP. So I convert it to PHP. I forgot to remove python image from Dockerfile. Thank you for the tip.

[tom_l]

@AhmadK

tl;dr for automations it should be automation.trigger service rather than homeassistant.turn_on/off

Not for my use case. I have automations that control my house climate. I want them enabled or disabled for certain periods. They may then be triggered by temperature during those periods.

[AhmadK (akasma74)]

Fair enough. Just wanted to point out the difference as sometimes it does matter.
Your heating control is HUGE…

[Sabuto (Robert Dunne)]

Np lol, also whenever you do getelementby[name,I’d etc] you could use jquery

[sparkydave (🇦🇺 Dave)]

@tom_l

I’d like to respectfully request if this could be expanded to include input_booleans and automatons as well?

+1 for this. That would make it far more powerful.

That said, it is awesome already

[tom_l]

@AhmadK

Your heating control is HUGE

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.

[ArthurDent1975 (Alessandro A.)]

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.

[Klagio]

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

[Klagio]

@Se7enair

Its not visual like Simple Scheduler

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)