Why Is Control4 Scheduled Lighting Scene Skipping Some Days?
- schedule condition overlap
- time source drift
- scene dependency unavailable at trigger time
Problem Description
A Control4 scheduled lighting scene fires on some days but skips others — the lights come on at sunset on weekdays but not weekends, or the scene randomly misses days. The Scheduler's day selection, recurrence type, sunrise/sunset location coordinates, conditional programming logic, or Director uptime may be causing the inconsistency.
Why This Happens in Real Homes
A scheduled scene that skips certain days is a day-selection or recurrence setting, or a sunrise/sunset offset, not a broken scene. In real homes weekend days get missed by a weekday-only rule. Check the Scheduler's day selection and recurrence and any condition gating the scene before assuming a fault.
Symptoms
- Missed schedule days
- works manually
- no obvious error popup
Recognize these? Here's what usually causes it.
Common Causes
- schedule condition overlap
- time source drift
- scene dependency unavailable at trigger time
Most fixes happen in the first 3 steps.
Do not ignore timezone/DST drift when diagnosing periodic skip patterns.
Tools & Requirements
Step-by-Step Solution
Check the schedule's day-of-week selection
In Composer Pro: go to Agents > Scheduler and find the lighting scene schedule. Check which days are selected. If set to 'Weekdays' (Mon-Fri): the scene does not fire on Saturday or Sunday. If set to specific days and one is unchecked: that day is skipped. Select all seven days if you want the scene to fire daily. A common mistake: selecting 'Mon, Tue, Wed, Thu, Fri' and forgetting to add weekend days, then noticing the scene 'randomly' skips some days.
Verify the schedule recurrence type
In the Scheduler agent: check the recurrence setting. 'Once' fires one time only. 'Daily' fires every day at the set time. 'Weekly' fires on selected days each week. 'Monthly' fires on a specific date each month. If set to 'Once': the schedule fired once and became inactive. Change to 'Daily' for a lighting scene you want every day. If the schedule shows 'Every 2 days' or 'Every 3 days': it intentionally skips days — change to 'Every 1 day' for daily execution.
Check sunrise/sunset offset calculations
If the schedule uses sunrise or sunset as the trigger: the firing time changes daily. On some days, the calculated time may fall into a 'quiet period' or conflict with another schedule. Verify the location coordinates: Composer Pro > System Design > Project > Properties > Location. Wrong coordinates shift sunrise/sunset times by minutes to hours. Also check the offset: 'Sunset - 30 minutes' fires 30 minutes before sunset, which varies by season. In winter, this could be 4:30 PM; in summer, 8:00 PM. The scene fires but at different times each day.
Check for conditional logic that blocks certain days
In Composer Pro: open the schedule's programming. If the action has conditions like 'If vacation mode is off' or 'If alarm is disarmed': the scene fires on schedule but the condition prevents execution on some days. Check all If/Else conditions. Also check for 'mode' variables: if the system mode is 'Away' on weekends and the condition requires 'Home' mode: the scene skips weekend days. Adjust conditions or remove them to allow the scene to fire regardless of system state.
Review Director logs for skipped execution
If the schedule appears correct but still skips days: check the Director log around the expected firing time on a skipped day. SSH into the controller or use Composer Pro > Tools > Lua Output. Look for entries related to the Scheduler agent at the expected time. If the log shows the schedule fired but the scene action failed: the issue is the scene, not the schedule. If no log entry exists for the schedule: Director may have been restarting at that time, or the controller's clock jumped (NTP sync issue) and missed the scheduled window.
Quick Solutions
Still having issues? This is usually the deeper cause below.
Schedules that skip randomly are usually a daylight-saving holdover — delete and recreate the schedule to clear the corrupted entry.
Recurring schedules need dependency checks, not just trigger-time definitions.
Thermostat issues that keep returning are often caused by stale backup-battery memory holding old settings across power cycles without the user realising.
- schedule condition overlap
- time source drift
- scene dependency unavailable at trigger time
Before you go — try one of these (they fix most cases).
Official Manufacturer Manual
Control4 provides official product documentation through their online manual rather than downloadable PDF. Access setup guides, troubleshooting steps, and product specifications for your Control4 Schedule Skips.
Source: help.control4.com
Need More Help? Control4 Support
Note: The contact information below connects you directly to Control4's official customer support team, not Trunetto. They can help with warranty claims, device replacements, and advanced technical issues.
Accessories owners commonly pair with Control4 Schedule Skips.
Amazon Smart Plug, Works with Alexa, Simple Setup, Endles...
TP-Link WiFi Extender with Ethernet Port, Dual Band 5GHz/...
Kasa Smart Plug, Matter Compatible, Energy Monitoring, Co...
As an Amazon Associate we earn from qualifying purchases.