Simple Scheduler Addon

Share your Projects!
428

Hi Alessandro, your addon is very nice and a very useful tool for my automations, thanks a lot.
I have two questions/suggestions for this great addon :

  • The weeks days are shown with two first letters, but there are languages that all the week days start with the same two letters, could be any option to choose the number of letters to show ?
  • If one day I don’t need that one scheduled event runs because I will not be at home, there is any way to disable this event without disable all the schedule.

Thanks a lot for for your job.

429

Sorry for the late response. I was on vacation.

Using more than two letters will break all the appearance. I’ve done a lot of tests in the past and it was hard to fit two letters. I was also tempted to use just the first one :sweat_smile:

You can easily disable one scheduler by editing it and removing the check from “enabled”
image

You can also add a switch in the frontend by enabling MQTT feature.
image

The procedure is explained here:

1 Like
430

Hi Allesandro,
I am on :
Home Assistant 2023.10.5
Supervisor 2023.10.1
Frontend 20231005.0 - latest
When I try to install the Simple Scheduler, I get the following error message:

“Failed to install add-on
The command ‘/bin/bash -o pipefail -c apt-get update -y && apt upgrade -y’ returned a non-zero code: 100”

Any idea what could be the reason?

431

What platform (raspberry, x86, etc)?
What kind of installation (OS, container, supervised)?

432

Hi Alessandro,
I will suggest you very stupid but useful automation to enable/disable schedule based on holidays calendar

# Se oggi è un giorno di festa disattivo le automazioni
- id: D_8
  alias: "AUTOMAZIONE - Schedulazioni: Disattivo se giorno di festa"
  trigger:
    - platform: time
      at: "00:01"
  condition:
    - condition: numeric_state
      entity_id: calendar.calendario_feste
      below: 1
  action:
    - alias: "disattivo schedulatore"
      service: switch.turn_off
      entity_id:
        - switch.simplescheduler_apri_cancelli_al_mattino
# Alle 23:59 di notte, se è un giorno di festa riattivo le automazioni
- id: D_9
  alias: "AUTOMAZIONE - Schedulazioni: Riattivo a fine  giorno di festa"
  trigger:
    - platform: time
      at: "23:59"
  condition:
    - condition: numeric_state
      entity_id: calendar.calendario_feste
      below: 1
  action:
    - alias: "disattivo schedulatore"
      service: switch.turn_on
      entity_id:
        - switch.simplescheduler_apri_cancelli_al_mattino
1 Like
433

hi, I always have this window, even when I press start it actually always takes me back there…

Screenshot 2023-11-28 121854
Screenshot 2023-11-28 121854820×362 18.8 KB

434

Could be useful to see some logs…

435

[s6-init] making user provided files available at /var/run/s6/etc…exited 0.
[s6-init] ensuring user provided files have correct perms…exited 0.
[fix-attrs.d] applying ownership & permissions fixes…
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts…
[cont-init.d] 00-banner.sh: executing…

Add-on: Simple Scheduler
Simple timer on weekly base

Add-on version: 2.11
You are running the latest version of this add-on.
System: Home Assistant OS 11.1 (amd64 / generic-x86-64)
Home Assistant Core: 2023.11.3
Home Assistant Supervisor: 2023.11.3

Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.

[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing…
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[11:44:06] INFO: Starting service.d [Interface]
[11:44:06] INFO: Starting service.d [Scheduler]
[11:44:07] INFO: Running interface.sh
[11:44:07] INFO: Running scheduler.sh

436

From the log, everything seems fine. The addon is starting.

Try to take a look in
Settings > System > Log
and select “SimpleScheduler” in the top right corner
(you will see “Home Assistant Core” which is the default selection for logs)

437

with this update this morning Supervisor 2023.11.6 everything is fine now. thanks

1 Like
438

I think that the solution was the reboot of HA due to the update, not the update itself.
BTW, glad you solved it!

439

New version out!

  • New feature: add parameters for RGB/CT lights (#138)
  • New feature: support humidifiers (#135)

You can set the color of a RGB light:
Write 16:30>B30|FF0077 turn on the light at 30% and set the color to FF0077 (6 digits HEX)

You can set the temperature of a CCT light:
Write 16:30>B30|K4700 turn on the light at 30% and set it to 4700°K

You can set the humidity of a (de)humifier:
Write 16:30>H42 turn it on and set it to 42%

440

:sos: BETA TESTER NEEDED!!! :sos:
I need help to test a new feature in the next release.

Conditions

For each scheduler, you can add a condition that will be checked at the time of the execution.
If the condition is ‘true’ the action will be performed and (obviously) it won’t be executed if the condition is ‘false’.
The condition is a template expression that you can add in the “template” field.
If the field is empty, no check will be performed and the action will always be executed.
The template expression must return a boolean (‘True’ or ‘False’).
So be sure to “convert” switches, lights, and any other entity states to boolean. A few examples:

{{  states('switch.my_switch') | bool }}
{{  not states('light.my_light') | bool }}
{{  states('sensor.room_temperature') | float > 23.5   }}
{{  is_state('person.my_kid', 'not_home')  }}
{{  states('sensor.room_temperature') | float > 23.5 and is_state('sun.sun', 'above_horizon')  }}

If the template returns ‘on’, ‘open’, ‘home’, ‘armed’, ‘1’ and so on, it will all be treated as ‘False’.
If the template expression has syntax errors it will be considered ‘false’, and it will be reported in the addon log.
Use the template render utility in Developer Tools to test the condition before putting it into the scheduler.




If you are interested you have to add the beta repository with this URL:

You should remove the actual version and install the version from the beta repository.
All schedulers will not be deleted, but run a backup anyway just for the sake of prudence.

One last note… Beta testing is for advanced and confident users. :wink:
You should help me and not the opposite :sweat_smile:

441

I might be inclined to test more beta features - but first I have to get it up and running :frowning:
My installation: HA 2023.12.3 on Raspi , Simple Scheduler 2.2.1
continues in the addon log:
[2023-12-20 12:54:00] ERROR: Unable to obtain timezone from Home Assistant
[2023-12-20 12:55:00] ERROR: Unable to obtain entities names from Home Assistant
The input line for the entity has no function (no keyboard input, no copy&paste)
Any ideas for troubleshooting or even solving the problem?
Thanks in advance.

442

Those errors means that the addon is unable to communicate with home assistant, which is basically impossible in supervised installation. Are you using a different kind of setup? BTW, you can try the beta from scratch, if you need.

443

I took the plunge: uninstalled simplescheduler - installed simplescheduler-BETA; it seems to work - at least I can see the local sunset and sunrise times in the status bar below … but: the LOG still contains the historical error messages from the previous simplescheduler installation.

And NO, i’m using a standard setup: HA-installation package had been rolled out on native RaspberryPi

444

That’s normal. Uninstall do not remove data files, including logs.
You can delete the log file to flush the old logs. Be sure to stop the addon first.
It will be created again from the addon at the first restart

445

Thx for that quick support :+1:

446

Thank you for beta testing :wink:

447

not for :upside_down_face:

with the template
{{ states (‘sensor.my-temperature’) | float > 20 }}
it works - triggering only occurs if the condition is met

1 Like