On Device Schedules

Only where the portal has On Device Schedules.

An on-device schedule runs on the controller itself. Once the controller has it, it keeps running whether or not the site can reach Cloud — through a broken connection, a router swap, or a weekend of no internet at all.

That is the difference from Scheduling, where a Task Scheduler runs in the cloud and fires tasks at the site. If the site is offline, a Task Scheduler cannot reach it; an on-device schedule does not care.

Use	When
Scheduling	You want to run a task, across devices, and you can rely on the connection
On Device Schedules	The behaviour must survive the site losing its connection

Changes are not instant, and that is by design
Cloud does not push a schedule at a controller. It records what you asked for and waits for the controller to collect it, which usually happens within a few minutes. Until it does, the schedule shows as Pending. That is normal, not a fault.

The schedule list

Schedules lists everything scheduled on the site's devices. Each row carries a coloured dot, the action it performs, the devices it runs on, and its status on each of them. Expanding a row shows the per-device breakdown.

Filter the list with:

the search box, Search by name or action;
the source filter — All sources, Cloud for schedules created here, Device for ones the controller published itself.

Each row has an Enabled toggle, so a schedule can be turned off without being deleted, and an options menu offering Edit and Delete.

Creating a schedule

Create schedule opens a New schedule window with three sections.

Action

Pick what the schedule does. The choices are the ones the selected devices actually support, read from the devices themselves:

Action	Does
Activate scene	Starts a scene
Activate tag	Triggers a tag
Turn off	Turns output off

Name the schedule here too. Leaving the name blank is fine — it is Auto-generated if left blank, from the action you chose, giving names like "Activate scene: Old Pink".

Devices

Choose which devices run it. One schedule fans out across every device you select, so the same behaviour does not have to be built several times over. An action only offered by some of your devices restricts the choice accordingly.

Timing

When the schedule is active. An on-device schedule is a span — it has a beginning and an end, rather than being a single moment.

Start. Either a clock time, or an astronomical anchor:

Anchor
Nautical dawn	Earliest light
Civil dawn
Sunrise
Sunset
Civil dusk
Nautical dusk	Last light

Each anchor takes an offset in minutes, before or after, up to a full day. The controller works the actual time out for itself from the site's location, so an anchored schedule tracks the seasons without being edited.

End. Either a duration after the start, or a specific time.

Repeat. Daily, weekly, monthly on a chosen weekday, or monthly on a chosen date. A repeating schedule can run forever, until a date, or for a fixed number of occurrences. Add date ranges as exceptions to skip holidays or shutdowns.

Seeing what is scheduled

Beside Schedules there are two calendar views:

Daily — one day as a timeline from midnight to midnight, each schedule drawn as a band across the hours it is active, with a marker for the current time.
Weekly — the same, a week at a time.

These are the views for questions the list cannot answer — whether two schedules overlap, whether anything covers a particular evening, what the site is actually doing at 3am.

Status

Because a controller has to collect a change before it takes effect, every schedule carries a status per device. Expanding a row shows all of them.

Status	Means	What to do
Accepted	The device has it and is running it	Nothing
Pending	Waiting for the device to collect it	Wait. If it stays pending, check the device is online
Rejected	The device refused it, and says why	Read the reason on the row, fix it, and save again
Drifted	The schedule was changed on the device itself, so your change can never land	Reapply, or accept what the device has

Reapply

Reapply sends a change again. It is the answer to both Rejected and Drifted. Where several devices need it, Reapply all does the row at once.

Reapplying overwrites the device's local edit
A drifted schedule means somebody changed it on the controller, outside Cloud. Reapplying replaces their version with yours. If their change was the deliberate one, edit the schedule here to match it instead.

Schedules the device already had

A controller may hold schedules that were never created here — set up before the site was connected, or written by another tool. Those still appear in the list, marked as coming from the device, and are drawn in grey in the calendar views.

Some of them the controller publishes as read-only: Published read-only by the device and cannot be changed from the cloud. They are shown so that the list is a true picture of what the site is doing, but they cannot be edited or deleted from here. Change them where they were made.