Simple Scheduler Addon

Share your Projects!
82

NEW RELEASE 0.14

  • Fix the “permission denied” issue
  • Sortable Columns
  • Added status bar with scheduler engine status
  • Added “debug option” to see all the error messages
  • various bugfixes/improvements

Also, there is a hidden feature: clicking in a secret place, you can open the engine log in a modal window, instead of browsing the shared folder. I can’t tell you where, because it is a hidden secret feature :rofl: :rofl: :rofl:

Note: this release has modifications in CSS and JS files, so it could happen that your browser would keep using the cached files. If you see something strange or something missing, just force the reload of the page (CTRL+F5) or empty the cache.

1 Like
83

Good day, dont forget us plain docker mortals :grinning:

1 Like
84

is there a way to set a “retry count”? unfortunately the automatic does not always work. i had to set a higher interval in schedy so that all switches and lights react

This setting tells Schedy how often it should try sending a
value to the actor. If the actor reports the set value back, no
further retry is made. You may find this useful if the connection
between Home Assistant and your actor is unreliable. Set to 0 in
order to disable retrying entirely.
send_retries: 10
How many seconds to wait before retrying.
send_retry_interval: 30

85

Mmmhhh… Actually there isn’t.
You could add a check in the automation after a “wait” condition to be sure that the command was executed succesfully.

86

Hi

Any idea why it is picking up different time zone to execute the schedules ?

87

It takes the timezone from HA.
Have you set the timezone in HA → Settings → General ?

88

Somehow the time is wrong. It must have happened with one of the latest releases. It’s always one hour behind. Schedy is at the right time. For example „Sofalampe“ is defined to switch on at 6am. In reality it switches on at 7am.

image
image750×1334 318 KB
image
image750×1334 314 KB

89

Could the ‘one-hour’ difference be due to Daylight Saving Time? It came into effect this past Sunday.

In other words, it’s not adjusting the scheduled times to compensate for DST.

90

I’ve found the issue.
Update to 0.15 and let me know

1 Like
91

Perfect! Thank you, it’s working again! :slight_smile:

1 Like
92

Hi. i´m really new in HA. Could you please tell me, how i can add SimpleScheduler in homeassistant manually? I´m not using Hass.io. I´ve installed HACS but i coulnd add your repository manually to it.

93

You can’t. This is an ‘Add-on’ which is only available in Home Assistant (previously called HassIO)

I suggest installing Home Assistant rather than just Home Assistant Core. You will definitely appreciate the upgrade

1 Like
94

Hi,
i added a scedule to turn on my lights. After removing one schedule, it keeps turning on my lights.
so i removed all scheduled (from the UI) but one of the lights is turned on every weekday on 07.00.

where should i look to remove this?
is there a file somewhere that saves a schedule that the UI did not remove??

i’m using a Raspberry PI with Home Assistant Core 0.107.5

UPDATE: The problem is not in the addon. it was my old fault. i forgot i had some scenes running in the original eWelink app off my sonoff switches… sry !!

Addon works perfectly.

95

Every schedule is a JSON file stored in the “share/simplescheduler” folder under the SAMBA share

2 Likes
96

I continue to love it. It should be standard in HASSIO, actually strange that after so many years they did not implement it.

Thanks a lot again

2 Likes
97

Hi,
I’d like to schedule a light on 30 minutes after sunset. i have tried “sunset + 30” but didn’t work there is something to do this setting?
Thanks.

98

No, offsets are not supported.
But you can workaround:

Create a script with your desired offset and then call the script at sunset from SimpleScheduler

sunset_script:
    sequence:
      - delay:
          minutes: 30  # supports seconds, milliseconds, minutes, hours
      - service: switch.turn_on
        data:
          entity_id: switch.my_switch_name
      - service: light.turn_on
        data:
          entity_id: light.my_light_name
1 Like
99

Hi Arthur,
Thanks for the reply but i have already an automation to handle this situation and i think at moment i’ll keep these setting. do you think It is possible to add the offset into future release?

Thanks.

100

No, not at the moment.
Adding offset requires a major modification in code.

101

Agreed, This should really be absorbed into the wider HomeAssistant. It’s amazing.

1 Like