Simple Scheduler Addon

[ascanio]

[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

[ArthurDent1975 (Alessandro A.)]

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)

[ascanio]

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

[ArthurDent1975 (Alessandro A.)]

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

[ArthurDent1975 (Alessandro A.)]

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%

[ArthurDent1975 (Alessandro A.)]

BETA TESTER NEEDED!!!
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:

GitHub - arthurdent75/SimpleScheduler-BETA

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.
You should help me and not the opposite

[wobeco]

I might be inclined to test more beta features - but first I have to get it up and running
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.

[ArthurDent1975 (Alessandro A.)]

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.

[wobeco]

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

[ArthurDent1975 (Alessandro A.)]

@wobeco

the LOG still contains the historical error messages from the previous simplescheduler installation

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

[wobeco]

Thx for that quick support

[ArthurDent1975 (Alessandro A.)]

Thank you for beta testing

[wobeco]

not for

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

[clipse (Marco)]

Hey great work!
I will test the beta right away and report, mega that you have now also built in conditions!

[wobeco]

hey, it came as it had to come: if dawn starts earlier than the defined switch-off time, then switch-on and switch-off are set incorrectly and the entity is not switched off

Here is my log from this morning:

[2024-03-10 07:24:00] SCHED: Executing OFF actions for [light-hose-morning]

[2024-03-10 07:24:00] SCHED: Turning OFF [myDimmerBox (dimmerBox#brightness)]

[2024-03-10 07:24:05] SCHED: [myDimmerBox (dimmerBox#brightness)] is OFF as requested!

[2024-03-10 07:30:00] SCHED: Executing ON actions for [Lichterschlauch-morgens]

[2024-03-10 07:30:00] SCHED: Turning ON [myDimmerBox (dimmerBox#brightness)] to 68%

[2024-03-10 07:30:05] SCHED: [myDimmerBox (dimmerBox#brightness)] is ON as requested!

The same will also occur at dusk with increasingly longer days.

Is there already a solution for this problem?

[ArthurDent1975 (Alessandro A.)]

hi @wobeco,
Can you add a screenshot of the schedulers?

[wobeco]

sure …

local sunrise and sunset are

[ArthurDent1975 (Alessandro A.)]

This is not an issue. It’s a configuration tuning.
I dont’ understand why you are using a mixed solution with a fixed time (6:30) and a relative time (sunrise+30)
If this are morning light, you should bond them to sunrise in both ON and OFF actions…
Why aren’t you using SUNRISE (with or without offset) also in the ON action?

EDIT
on SATURDAY/SUNDAY you could use SUNRISE+15>B68 in the ON action

[wobeco]

It is the control (depending on the day of the week) for staircase lighting: ON in the morning at a defined time, then OFF according to sunrise and thus sufficient brightness in the staircase.

In the evening, vice versa: ON at dusk, when it gets dark in the stairwell, OFF at a set time.

[ArthurDent1975 (Alessandro A.)]

Oh, I get it.
They are internal light. I assume the were external.
Does it extends also on work days?