Lights that switch themselves on in the middle of the night are genuinely unnerving, and the internet will happily tell you that you have been hacked. You almost certainly have not. Smart lighting systems accumulate automations, schedules and defaults from several different places, and the most likely explanation is that something you set up months ago, or something that was enabled by default, is doing exactly what it was told.
The short answer
Work through the list of things that can command a light: routines in the app, schedules on the bulb itself, voice assistant routines, geofencing, away or holiday modes, third-party integrations, and power restoration defaults. Check the activity log first if your system has one, because it usually names the culprit outright and saves you an hour of guessing.
Check the activity log first
Most smart home platforms keep a history showing what changed, when, and what triggered it. It is often buried in a device’s settings rather than displayed prominently, but it is by far the fastest route to an answer. Entries typically distinguish between a manual action, a routine, a voice command and a schedule.
If the log says a routine turned the light on, you have your answer. If it says the light simply reported itself as on with no command, that points at power restoration rather than an automation.
The usual suspects
- Power restoration default. Most smart bulbs turn on at full brightness when mains power returns, because that is how a normal bulb behaves. A brief power cut at 3am, too short to notice, switches on every smart bulb in the house. This is the single most common cause of the classic middle-of-the-night event.
- A forgotten routine. Sunrise and sunset triggers drift through the year, so a routine set in summer fires at a very different time in winter.
- Voice assistant routines. Separate from the light app’s own schedules, and easy to forget about entirely.
- Away or holiday mode. Designed to switch lights on and off randomly to look occupied. If someone enabled it and never turned it off, this is exactly what it does.
- Geofencing. A phone’s location reading drifts when it loses GPS, and a home arrival trigger fires while you are asleep upstairs.
- Motion sensors. Pets, curtains moving over a radiator, and warm air currents all trigger passive infrared sensors.
- Shared accounts. Anyone with access to the app can control the lights from anywhere, including accidentally.
- A wall switch. Cutting and restoring power at the switch turns most smart bulbs on. Some systems use rapid switch flicks as a deliberate reset command.
Read the device activity log
Find the history for the light that misbehaved and look at the entry for the exact time. It usually names the trigger directly. Everything else on this list is guesswork by comparison.
Change the power-on behaviour
In the bulb settings, look for a power restore or power-on behaviour option and set it to remember the last state, or to stay off. This alone eliminates the brief-power-cut scenario, which is the most common cause.
Audit every routine and schedule
Go through the automations list in the lighting app and read each one properly. Pay attention to sunrise and sunset triggers, which move by hours across the year, and to any routine with a location condition.
Check your voice assistant separately
Routines live in the assistant app as well as the light app, and they are entirely separate lists. Check both, and check any routines created by other household members.
Turn off away or vacation mode
Look for anything described as away, holiday, simulated occupancy or randomise. These are designed to turn lights on unpredictably and they do the job well.
Disable geofencing temporarily
If the events correlate loosely with people coming and going, turn off location-based triggers for a week and see whether it stops. Phone location readings are less reliable indoors than people assume.
Review third-party integrations
Anything linked to your lighting account can control it: security systems, other smart home platforms, automation services, doorbells. Remove any integration you no longer use.
Change your account password and check active sessions
If the log shows commands you cannot account for, change the password, enable two-factor authentication if it is offered, and revoke any sessions or devices you do not recognise. This is the right response to genuinely unexplained activity, but it should come after the checks above rather than before them.
If several lights across different rooms all switch on at once at an odd hour, that is the signature of a momentary power interruption rather than an automation. Automations usually affect a specific group. A whole-house event points at the mains.
The brief power cut explained
Very short interruptions, lasting a fraction of a second, happen more often than most people realise. They are too brief to reset a clock or interrupt a fridge, but they are more than enough to reboot a smart bulb. The bulb comes back, applies its default power-on behaviour, and switches itself on at full brightness.
Changing that default to remember the last state is the fix, and it is worth doing on every bulb in the house rather than just the one that woke you.
If you conclude your account really has been accessed, do not just change the password. Check for routines and integrations that were added, because those persist and will keep running after a password change.
Keeping it predictable
- Name every automation clearly, including what it does and when. Unnamed routines are how this happens.
- Review your automations twice a year, particularly around the clock changes.
- Set power-on behaviour deliberately on every bulb rather than leaving the default.
- Avoid having the same light controlled from two different platforms, which produces conflicts that are very hard to trace.
- Use two-factor authentication on the account if it is offered.
Can smart lights be hacked?
It is possible but rare, and it is far down the list of likely explanations. Forgotten automations and power restoration defaults account for the overwhelming majority of unexplained events. Check those first.
Why do all my lights come on at once at night?
Almost certainly a brief power interruption. Smart bulbs default to switching on when mains power returns. Change the power-on behaviour to remember the previous state.
Do sunset routines change through the year?
Yes, substantially. A routine set for sunset in June fires several hours earlier in December. This catches people out every autumn.
Can my neighbour control my lights?
Not without access to your account. Older systems using radio remotes on shared frequencies could occasionally be affected by a neighbour, but account-based systems are not.
Should I remove the app if I cannot find the cause?
Removing the app does not stop cloud-based routines, which run on the server rather than on your phone. Delete the routines themselves, or unlink the integration responsible.
The bottom line
Read the activity log, because it usually names the trigger and everything else is guesswork. Then change the power-on behaviour on every bulb, since a momentary power cut is the most common cause of a whole house lighting up at 3am. Audit your routines in both the light app and your voice assistant, and only treat it as a security question if the log shows commands nothing accounts for.
