TapHome

Scheduler

The Scheduler smart rule automates your devices on a recurring time schedule. You define a list of actions — each with a specific time — and the smart rule executes them within the chosen time period: every day, every week, on workdays versus weekends, every month, or every year.

Think of it as a timeline that repeats: you place actions at specific points, and each time the period restarts, those actions execute again in the same order. Between scheduled times, devices stay in the state set by the most recent action.

Getting started

Setting up a Scheduler takes three steps:

  1. Add devices — select the devices you want to control.
  2. Choose a time period — how often the schedule repeats.
  3. Add actions — define what happens and when.

Basic example

You want your porch light to turn on every evening at 20:00 and turn off at 23:00.

  1. Create a new Scheduler smart rule.
  2. Your current device is pre-selected in the Devices section. If needed, tap Add Device to add the porch light.
  3. The time period defaults to Day. Leave it as is.
  4. In the Actions section, tap Add New Action.
  5. On the action configuration page, set the time to 20:00 and tap Set action to choose the porch light action — set it to On.
  6. Go back, then tap Add New Action again.
  7. Set the time to 23:00 and set the action to Off.
  8. Tap Save.

The porch light now turns on at 20:00 and off at 23:00, every day. If the system restarts at 21:00, the smart rule determines that the 20:00 action was the most recent and turns the light on — keeping your schedule in sync.

Devices

Tap Add Device to select one or more devices. All scheduled actions apply to every device in the list — you cannot assign individual actions to individual devices within a single Scheduler smart rule.

All selected devices must be of the same type (e.g., all switches, all thermostats). The device picker only allows compatible devices.

If you need different schedules for different devices, create separate Scheduler smart rules — one per group of devices that share the same schedule.

Scheduled actions

The Actions section shows all actions in your schedule, sorted by their execution time.

Tap Add New Action to add a new action. Tap an existing action to edit it. To remove an action, use the Remove button at the bottom of its configuration page.

Each action includes a device action — what your devices should do when the time arrives. Tap Set action to choose the command (turn on, turn off, set to a value, etc.). The available commands depend on the type of devices selected: switches offer on/off, dimmers offer a brightness percentage, thermostats offer a temperature setpoint.

Time period

The time period determines how often your schedule repeats. Select it using the radio buttons on the configuration page.

Time periodMeaning
DayRepeats every day
WeekRepeats every week — each action specifies which day of the week
Workday/WeekendRepeats every week — each action specifies workday or weekend
MonthRepeats every month — each action specifies which day of the month
YearRepeats every year — each action specifies the month and day

Time

Every action has a time setting with three modes:

ModeDescription
TimeAbsolute clock time — pick a specific hour and minute
From sunriseRelative to sunrise at your location
From sunsetRelative to sunset at your location

Absolute time

Select Time and use the time picker to set the exact hour and minute.

Sunrise and sunset offsets

Select From sunrise or From sunset to schedule actions relative to the sun. A slider appears with preset offsets ranging from −6 hours to +6 hours.

The slider label shows Offset Relative to Sunrise or Offset Relative to Sunset depending on the selected mode. A description below the slider shows the next actual sunrise or sunset time at your installation’s location.

Sunrise and sunset times are calculated from your installation’s GPS location. The times adjust automatically throughout the year — you do not need to change the schedule seasonally.

Day selector

Depending on the selected time period, each action also includes a day selector. The Day time period has no day selector — actions simply repeat every day at specific times.

Week

A Day of week section appears with seven radio buttons — Monday through Sunday. Select which day of the week this action should execute.

Workday/Weekend

A Day of week section appears with two options:

OptionMeaning
workdayAction executes on Monday through Friday
weekendAction executes on Saturday and Sunday

Month

A Day of month section appears with two controls:

Direction: Choose whether to count from the start or end of the month.

OptionMeaning
From start of monthCount forward — day 1, day 2, … up to day 28
From end of monthCount backward — last day, day 2 from end, … up to day 28 from end

Day slider: Select the specific day. The label updates to show the selected day — for example, first day, last day, or “day 15.”

Use From end of month with last day for actions that should run on the last day of every month, regardless of whether the month has 28, 29, 30, or 31 days.

If you schedule an action for a day that does not exist in a given month (for example, day 31 in February), the action executes on the last available day of that month instead.

Year

A Day of year section appears with a date picker. Select the month and day — the year is not shown, since only the date within the year matters.

If you schedule an action for February 29, it will only execute in leap years. In non-leap years, the action is skipped entirely — the scheduler waits for the next leap year.

Examples and scenarios

Outdoor lights: on at sunset, off at bedtime

Goal: Turn on all outdoor lights at sunset and turn them off at 23:00 every day.

Configuration:

  • Devices: front porch light, garden lights, driveway light
  • Time period: Day

Actions:

  1. Turn on — at sunset (offset 0)
  2. Turn off — at 23:00

Behavior: Every evening at sunset, all three lights turn on simultaneously. At 23:00, they all turn off. In summer, sunset might be at 21:00, giving 2 hours of light. In winter, sunset might be at 16:30, giving over 6 hours. The sunset time adjusts automatically throughout the year. If the system restarts at 22:00, the smart rule recognizes that the sunset action was the most recent one and turns the lights back on.

Irrigation: water on specific days

Goal: Water the garden at 06:00 for 30 minutes on Monday, Wednesday, and Friday.

Configuration:

  • Device: irrigation valve
  • Time period: Week

Actions:

  1. Turn on — Monday at 06:00
  2. Turn off — Monday at 06:30
  3. Turn on — Wednesday at 06:00
  4. Turn off — Wednesday at 06:30
  5. Turn on — Friday at 06:00
  6. Turn off — Friday at 06:30

Behavior: On Monday at 06:00, the valve opens. At 06:30, it closes. The same happens on Wednesday and Friday. On all other days, the valve stays closed — the most recent action is always a “turn off” from the previous watering day. For example, on a Thursday afternoon, the most recently executed action is Wednesday’s 06:30 turn-off.

Morning heating: workdays vs weekends

Goal: Warm up the living room before waking — earlier on workdays, later on weekends. Reduce the temperature after the morning routine.

Configuration:

  • Device: living room thermostat
  • Time period: Workday/Weekend

Actions:

  1. Set to 22 °C — workday at 05:30
  2. Set to 19 °C — workday at 08:00
  3. Set to 22 °C — weekend at 07:30
  4. Set to 19 °C — weekend at 10:00

Behavior: On a workday, the thermostat rises to 22 °C at 05:30 so the room is warm by the time you get up. At 08:00, after everyone has left, it drops back to 19 °C. On weekends, the boost starts later at 07:30 and lasts until 10:00. Between the last action of one day and the first action of the next, the thermostat stays at 19 °C — set by the most recent “reduce” action.

Monthly maintenance: last day of the month

Goal: Run the server room ventilation fans at full power on the last day of every month from 08:00 to 18:00.

Configuration:

  • Device: server room ventilation fan
  • Time period: Month

Actions:

  1. Turn on — last day (From end of month) at 08:00
  2. Turn off — last day (From end of month) at 18:00

Behavior: On January 31, the fan turns on at 08:00 and off at 18:00. On February 28 (or 29 in a leap year), the same happens. The last day setting automatically adapts to the actual last day of each month — you do not need separate smart rules for months of different lengths.

When building a complex schedule, start with the Day time period and a few basic actions. Once you are happy with the timing, switch to Workday/Weekend or Week to add day-specific variations. Your actions are cached when you switch time periods, so you can always switch back without losing them.

How the Scheduler works

Continuous state

The Scheduler maintains continuous state — at any moment, one action is “current.” That is the action whose scheduled time most recently passed. Devices stay in the state set by that action until the next scheduled time arrives.

This means the schedule has no gaps. Your devices are always controlled by whichever action last executed.

System restart

When the system restarts, the Scheduler determines which action should currently be active by replaying the schedule backward. It finds the action whose time most recently occurred and applies it to all devices, ensuring they return to the correct state automatically.

Execution order

Your actions form a repeating cycle. The scheduler fires them in chronological order within each period, and after the last action fires, the cycle starts over with the first action of the next period.

There is no reset or special event at the boundary between periods. In a daily schedule with actions at 06:00, 14:00, and 20:00 — after the 20:00 action fires, devices stay in that state through midnight until the 06:00 action fires the next morning. Midnight is invisible to the scheduler.

When sunrise or sunset shifts the order

When you combine fixed-time actions with sunrise or sunset actions, the actual firing order can change with the seasons. The scheduler detects this and handles it automatically.

Consider a daily schedule with three actions:

  1. Set to 20 °C — at sunrise
  2. Set to 18 °C — at 08:00
  3. Set to 21 °C — at sunset

In summer (sunrise at 05:30, sunset at 21:00), actions fire in their natural order:

TimeWhat happensThermostat
00:00–05:29Sunset action continues from previous evening21 °C
05:30Sunrise action fires20 °C
08:00Fixed-time action fires18 °C
21:00Sunset action fires21 °C

In winter (sunrise at 08:15, sunset at 16:30), sunrise shifts past the 08:00 action. The scheduler adapts:

TimeWhat happensThermostat
00:00–07:59Sunset action continues from previous evening21 °C
08:00Fixed-time action fires — sunrise was expected first but hasn’t arrived, so it is passed over18 °C
08:15Sunrise action arrives late — already passed over, ignored18 °C
16:30Sunset action fires normally21 °C

At 08:00, the scheduler expected the sunrise action to come first. Since it hasn’t arrived, the scheduler marks it as passed over and fires the 08:00 action. When the sunrise action arrives 15 minutes later, the scheduler sees it was already passed over and ignores it — devices stay at 18 °C. The sunset action then fires normally at 16:30.

Each day, the scheduler evaluates the order independently. If sunrise continues to arrive after 08:00 throughout winter, the sunrise action continues to be passed over each day. When sunrise eventually arrives before 08:00 again — as days grow longer in spring — the full three-action cycle resumes automatically.

If you need a sunrise or sunset action to fire reliably year-round, make sure nearby fixed-time actions leave enough gap that the order cannot reverse. For example, if the latest sunrise at your location is around 08:00 in winter, place your next fixed-time action at 09:00 or later.

When sunrise or sunset cannot occur

At extreme latitudes, there are periods when the sun does not rise or set at all. During these periods, sunrise and sunset actions do not fire — only fixed-time actions continue as normal. When the sun eventually returns, the sunrise and sunset actions resume automatically.