Luma LightsTroubleshooting
Most "lights didn't come on" reports trace back to one of a few causes — here's the fast path.
🔎 Start with Diagnose Controllers
On the Autopilot deploy card, tap Diagnose Controllers. It checks each controller for: reachability, whether its clock is set, whether the schedule is loaded, and what's supposed to play tonight — usually pinpointing the issue immediately.
🔄 Re-sync first
Changed a holiday, team, or look? Nothing updates on the controller until you tap Sync schedule to controllers again. This is the single most common fix.
⏰ Lost Wi-Fi or clock
Most "lights didn't come on" issues are a controller that lost Wi-Fi or its clock drifted, or one that simply needs a re-Sync. Set your time zone on the Autopilot screen — it's what keeps the on/off timing and wind-down accurate.
🌐 Can't connect at all?
Check you're on the same Wi-Fi network as the controller, and that the app was opened over http://, not https:// (see Connect Your Lights — this is the browser's mixed-content rule, not a connectivity bug). Also confirm you can open http://<controller-ip> directly in a browser tab; if that fails too, the issue is network-level, not app-level.