Scenes & moods

Loxone schedule or timer not running

A schedule, timer, or automatic scene that used to run on its own has stopped firing, is firing at the wrong time, or never seems to trigger anymore.

Updated July 15, 2026~1 min read

Quick answer

Check whether holiday or vacation mode is active first, it silently overrides normal schedules, then confirm the Miniserver's time and timezone are correct.

A schedule that suddenly stops firing is rarely a hardware failure, it is almost always a setting like holiday mode, a timezone mismatch, or a repeat pattern that does not include today. Work through the checks below before assuming anything needs to be rebuilt.

Step by step

Holiday or vacation mode is silently active
  1. 1

    In the app, check the main dashboard or settings for a holiday, vacation, or away mode toggle.

  2. 2

    Holiday mode is designed to override normal schedules, often intentionally suppressing lighting or climate automation while you are away.

  3. 3

    If it was left on after a trip, turn it off and confirm the schedule resumes on its next scheduled run.

Grixx can check whether holiday mode is currently active on your system in seconds, this is one of the most common reasons a schedule appears to have just stopped working.

Ask Grixx →
Miniserver time or timezone is wrong
  1. 1

    Access the Miniserver's web interface and check the current date, time, and timezone setting under general configuration.

  2. 2

    A Miniserver that lost power for an extended period can sometimes reset its clock or lose sync, especially if it also lost internet access.

  3. 3

    Confirm the timezone is set to your actual location, a wrong timezone shifts every scheduled event by the offset difference.

Grixx can pull the Miniserver's reported time right now and compare it to actual local time, so a clock drift or wrong timezone gets caught immediately instead of you comparing manually.

Ask Grixx →
Sunrise or sunset offset is throwing off an astro schedule
  1. 1

    If the schedule is tied to sunrise or sunset rather than a fixed clock time, check whether an offset (for example, 30 minutes before sunset) is configured.

  2. 2

    Confirm the Miniserver's location or coordinates are set correctly, an incorrect location shifts calculated sunrise and sunset times.

  3. 3

    Compare the schedule's actual trigger time over a few days against the real local sunset time to see if there is a consistent gap.

Grixx can calculate what your actual local sunrise or sunset should be and compare it against when the schedule is firing, to confirm whether the location setting is the issue.

Ask Grixx →
The schedule or logic block was disabled
  1. 1

    In the app, look for the schedule or timer control and check if it has an enable or disable toggle visible to you.

  2. 2

    Some schedules are only editable in Config and won't show a toggle in the app at all, in that case the disable state is not something you can flip yourself.

  3. 3

    If you have a favorites or scenes section, confirm the automatic scene tied to the schedule was not manually turned off there.

Grixx can check whether the schedule and its linked scene are both enabled, since a schedule can be active while the scene it triggers is switched off, which looks identical from the outside.

Ask Grixx →
Schedule ran once correctly then stopped repeating
  1. 1

    Check whether the schedule is set to repeat daily, weekly, or as a one-time event, a one-time schedule will not fire again by design.

  2. 2

    Confirm the days of the week configured for the schedule actually include today, a schedule set for weekdays only will not run on a weekend.

  3. 3

    If the schedule is tied to a specific date range, check whether that range has expired.

Grixx can read back the schedule's exact repeat pattern and date range, which clears up a lot of confusion between a schedule that is broken and one that simply was not set to run today.

Ask Grixx →

When to call a licensed pro

If the schedule's time, days, and holiday mode all check out correctly and it still is not running, the underlying logic block may need to be reviewed in Loxone Config. That is a programming-level fix, bring in a certified Loxone integrator rather than trying to rebuild the schedule from scratch yourself.

Why LoxPilot

Grixx can check whether holiday mode is on, the Miniserver's current time, and the schedule's actual configuration in one message, so you are not manually opening four different menus to find the cause.

Frequently asked questions

Does holiday mode override my regular schedules automatically?

Yes, that is its intended purpose, to suppress or modify normal automation while you are away. If it is left on by mistake, your regular schedules will appear to have stopped working.

Why would a schedule run at the wrong time?

The most common causes are an incorrect Miniserver timezone, a clock that drifted after a power loss, or a sunrise or sunset offset calculated from the wrong location.

Can I enable or disable a schedule myself in the app?

If your installer exposed the schedule as a homeowner-editable control, yes. Some schedules are only visible and editable in Loxone Config, in which case you will not see a toggle for it in the app.

My schedule worked once and never ran again, what happened?

Check whether it was configured as a one-time event rather than a repeating one. A one-time schedule fires exactly once by design and needs to be reconfigured to run again.

Ask Grixx, one free question, no signup

Grixx, LoxPilot's AI assistant, can walk you through this step by step or diagnose your system directly.

Ask Grixx for free →

Related guides

See LoxPilot pricing →