Technology

Why Do Smart Lights Sometimes Turn Themselves On, Flicker, or Stop Responding?

A smart bulb is a tiny computer wrapped around an LED. When it flickers, glows when it's off, or lights up at 2 a.m., the cause is often electrical or a configuration choice, not Wi-Fi.

Or: Why Your Light Bulb Sometimes Has a Mind of Its Own, and Why the Problem Might Not Be Wi-Fi

It's two o'clock in the morning, and a glow from the hallway wakes you. The smart lights have turned themselves on.

You open the app, turn them off, and go back to bed. A few nights later, it happens again.

Or maybe your version is different. One bulb flickers while its neighbors behave. One ignores commands while the other two in the same fixture respond perfectly. Another works through the app until someone flips the wall switch, and then it vanishes from your smart-home system entirely.

The reflex is to blame Wi-Fi, a software bug, or a defective bulb. Sometimes one of those is right. But a smart light is a stack of different systems, and several of them can produce nearly identical symptoms. In the last post we looked at why devices disconnect when the Wi-Fi looks healthy. This one covers the other half of the story: the power and electronics inside the bulb.

A Smart Bulb Is a Small Computer With an LED Attached

An incandescent bulb is about as simple as electronics gets. Current heats a filament until it glows. No processor, no network, no memory.

A smart bulb has a very different anatomy. There are LEDs for light, and a driver that converts mains AC power into something those LEDs can use. A microcontroller decides what the bulb is doing, and a radio (Wi-Fi, Zigbee, Bluetooth or Thread) receives commands. There's usually some nonvolatile memory too, holding the last brightness and color or a configured startup behavior.

Think of it as several connected systems: incoming mains power feeds the bulb's power-conversion circuitry, which supplies the controller, radio and LED driver. The controller determines the requested brightness and color, while the driver regulates the electrical power delivered to the LEDs. A problem with the incoming supply can therefore affect the light output, the controller or both. A problem at any stage shows up downstream. A power glitch at the front can look like a "network problem" at the back, because a bulb that loses power also loses its radio.

So when a smart light misbehaves, the useful question is rarely "Is my Wi-Fi bad?" It's "Which part of this stack is producing the behavior?"

Why LEDs Need a Driver, and Why Flicker Isn't Always Wireless

An LED is a semiconductor, and it doesn't behave like a heating element. A small change in voltage can produce a large change in current, which is why LEDs are normally run from controlled current rather than plugged straight into a supply.

The driver does that regulating, and a smart bulb adds low-voltage regulation for its processor and radio, so several electronic functions depend on one steady incoming supply. If that supply gets irregular, the driver might flicker while the controller carries on unaware, or the controller might reset altogether. That's why some smart lights merely shimmer while others briefly disappear from the app.

Here's a useful fact. Once a bulb is on and has its instructions, it doesn't need an active wireless link to keep the LEDs steady. If the network drops, the bulb generally stays at its last brightness and color. A lost connection doesn't, by itself, cause flicker.

So when a bulb visibly flickers, suspect the electrical side: unstable power, driver behavior, an incompatible dimmer, or a developing hardware fault. The other possibility is that something is deliberately changing the brightness, such as an automation firing repeatedly, which can mimic flicker from across the room. Is the electronics' output unstable, or is the controller faithfully carrying out a request you've forgotten about? The fixes are completely different.

The Old Dimmer Problem

Many homes have wall dimmers installed back when everything was incandescent. A common design, the phase-cut dimmer, doesn't lower the voltage smoothly. It chops out a slice of each AC half-cycle, so the lamp receives less energy per cycle. A glowing filament shrugs this off, because its temperature changes slowly. An electronic driver has to tolerate that chopped waveform while keeping its own circuits fed, and not every driver is designed to.

Lutron's support documentation on flickering lights with its LED dimmers lists several familiar causes: the bulb isn't dimmable at all (including some smart or connected bulbs), two dimmers control the same lights, or the dimmer is pushing below the range the LED can dim to, causing flicker, buzzing or dropout at low levels. Its fixes include choosing bulbs listed as compatible, removing the second dimmer, and adjusting the dimmer's low-end trim so its lowest setting stays within what the lamp can handle.

Smart bulbs make this worse because they have their own internal dimming. When you set a bulb to 30% in the app, its controller changes how the LEDs are driven, and the wall circuit may keep delivering full power. Put that bulb behind a wall dimmer and two systems are trying to control one light. At lower dimmer settings, the bulb's processor and radio may not get the reliable power they need.

The recognizable story: the bulb works perfectly with the dimmer at maximum, then someone drops it to 50%, the bulb flickers, and a few seconds later it vanishes from the app. That doesn't prove the bulb is defective. The dimmer's output may simply not be what the bulb was built to accept. For most smart bulbs, the intended arrangement is continuous power with brightness controlled through the bulb's own interface.

Minimum Loads and the Glowing "Off" Bulb

Some electronic dimmers and smart switches need a minimum load to behave properly, which became a problem as homes swapped incandescents for efficient LEDs. These controls draw a trickle of current through the lighting circuit to power themselves, and when the load is too small they can flicker, buzz, or fail to shut off completely. The control and the load have to be matched.

That same trickle explains a stranger phenomenon. You flip the switch off, and the LED keeps glowing faintly, or flashes briefly every few seconds. This is often called LED ghosting.

Leviton's support page describes ghosting as a faint glow from a switched-off light caused by leakage of current. In an incandescent bulb, that amount would never heat the filament enough to see. An LED, though, can produce visible light from remarkably little energy. Leviton notes ghosting is a common problem with neon-lit switches, and that LED-lit switches are designed to avoid it with LED bulbs. Electronic dimmers and smart switches can leak small currents too, because they need a little for their own electronics.

A periodic flash is plausibly a capacitor in the driver slowly charging from that leakage until it crosses a threshold, lighting the LEDs briefly before discharging, though the details depend on the design. A faint glow isn't automatically a dangerous wiring fault, but any fix involving wiring should follow the manufacturer's instructions and local electrical codes.

When a Wall Switch Takes the Bulb Offline

Now a much more common scenario. A few smart bulbs work beautifully from the app. Then someone flips the ordinary wall switch, and every bulb disappears from the system.

That isn't a mystery. The switch removed power, so the processors and radios shut down. When the switch goes back on, the bulbs reboot and reconnect. They didn't disconnect because of weak coverage. Someone turned off their little computers.

This gets more interesting on a Zigbee mesh. Many mains-powered Zigbee bulbs act as routers, forwarding messages for other devices. A hallway bulb may be the relay that lets the hub reach a sensor farther away. Flip that bulb's wall switch and the relay vanishes. Devices that relied on it must find another path, and some may drop out temporarily. Switching one light off at the wall can disturb devices elsewhere in the house, not because of brightness settings but because a node in the network lost power.

The cure is to separate cutting power from sending a command. Wireless wall controls send commands to the bulbs while leaving their electrical supply available, and suitable in-wall modules can adapt existing switches for smart lighting. Philips Hue's battery-powered Wall Switch Module, for example, works with a conventional wall switch while keeping compatible Hue lights powered and reachable. It requires a Hue Bridge but does not require a neutral wire to power the module itself. Hue also offers separate mains-powered in-wall controls with different wiring requirements, including models that require a neutral. The principle matters more than the brand: a control intended for smart bulbs should tell them to turn off through the lighting system rather than disconnecting the power that keeps their processors and radios running. Any modification to mains wiring should follow the product's instructions and applicable electrical codes.

Why Lights Turn On by Themselves

Back to the hallway at three in the morning, with nothing scheduled, no motion events, and nobody at a switch. One strong suspect is a brief interruption in power. When electricity comes back, a smart bulb has to decide what to do, and that decision is made in software. A manufacturer might default to turning on, a reasonable choice for a bulb controlled by a wall switch, because flipping that switch should produce light. But after a short blip in the house's power, the same default can light several bulbs at once with no wireless command sent at all.

Products differ in how they respond when power returns. Some turn on at a default brightness, some restore their previous color or brightness, and others can remain off after an interruption. Philips Hue introduced configurable power-on behavior in late 2018, allowing supported lights to restore their previous state instead of always illuminating after a power outage. Its options have included a default warm-white startup and power-loss recovery, which can preserve an off state when the electricity returns. Exact behavior and available settings depend on the bulb model, firmware and controller. It's worth testing the configuration, because a very brief interruption or repeated power cycling may not produce the same result as a longer outage.

Brief interruptions are easy to miss, because different power supplies have different tolerances: a television may ride through a blip that resets a bulb. Still, if several fixtures or unrelated appliances show odd electrical behavior, the circuit or supply deserves professional attention.

When the Lights Are Obeying, Just Not You

Not every surprise is electrical. Sometimes the lights are following orders you've forgotten, or orders that conflict.

Picture one light with several rules: a motion sensor turns it on, a nighttime routine dims it to 20%, a schedule turns it off at bedtime, and a voice routine fires a different scene. Overlap those, and one rule turns the bulb off while a sensor turns it back on and another changes the brightness. To you, the light seems haunted. To the system, every rule is executing exactly as written. They just weren't designed to coexist.

Multiple platforms complicate this. A bulb might be controlled from its manufacturer's app, Apple Home, Google Home or Alexa, and disabling a routine in one app doesn't disable its twin in another. When a light changes state unexpectedly, check every platform with permission to control it.

Motion sensors and schedules add wrinkles. A passive infrared sensor reacts to movement, not presence, so someone sitting still may see the light time out and snap back on. And a wrong timezone or duplicate schedule can fire a light at a strange hour. When a light turns on at the same time every day, start with the automation configuration, not electrical noise.

One Bulb Fails While Its Neighbors Behave

Consider a ceiling fixture holding three identical smart bulbs. Two behave. The third intermittently drops out of the app. All three share similar wireless coverage and the same electrical supply, which points at the individual device: a hardware defect, a firmware issue, a thermal problem, or a poor socket contact.

The clean test is to swap. If the same bulb fails in another suitable fixture, the bulb is suspect. If a different bulb fails in the original socket, look at the fixture, with power safely disconnected and an electrician where appropriate.

Heat is a quiet culprit. A smart bulb packs a driver, processor and radio into a small shell, and in an enclosed fixture internal temperatures climb, shortening component life. Some bulbs aren't rated for enclosed fixtures, and many have thermal protection that dims or shuts them down when hot, then lets them resume, creating a cycle of dimming and restarting. A bulb that turns unreliable only after running a while may have a thermal issue, though that symptom alone doesn't prove it.

Flicker You Can't See, and the Camera That Can

Some flicker is too fast for your eyes. LED lighting can exhibit temporal light modulation, meaning its output varies over time. Many dimmable LEDs adjust brightness using pulse-width modulation (PWM): the LEDs switch fully on and off rapidly, and the proportion of time spent on sets the average brightness. A U.S. Department of Energy review of flicker research describes this and notes some products modulate at roughly 400 to 2,000 Hz. Direct flicker visible with a steady gaze is typically around 3 to 90 Hz, so a fast PWM lamp usually looks steady, though the review describes other effects, such as the stroboscopic effect around moving objects, at higher frequencies. LED systems vary widely.

What about the dark bands that appear when you film an LED light with your phone? Many cameras use a rolling shutter, meaning different rows of the image sensor are exposed or read at slightly different times. If the light's output changes during that process, some rows may capture more illumination than others, producing horizontal bands or uneven brightness. The interaction depends on the light's modulation frequency, the camera's exposure time and its sensor readout behavior. A lamp that looks perfectly steady to your eyes can therefore appear to flicker dramatically on video. Camera banding alone doesn't prove the bulb is defective, but visible flicker during ordinary use deserves investigation.

Failing Parts, Compatibility and Safety

Smart bulbs are electronics, and electronics wear out. If a bulb fails consistently in multiple compatible fixtures, replace it rather than rebuilding your network around it. Firmware updates can also change startup or reconnection behavior, though a sudden change isn't automatically the update's fault.

Smart switches and dimmers have requirements of their own, such as a neutral wire and supported load ranges. Choose the fixture, bulbs, switch and control method as one system.

Most smart-lighting problems are just irritating. A few symptoms aren't. Repeated breaker trips, visible sparking, a burning smell, unusually hot electrical parts, or persistent abnormal buzzing can indicate an electrical problem needing a professional. Loose connections create heat and intermittent operation, and improper wiring can present a shock or fire hazard. Working on mains wiring is nothing like changing a setting in an app. When in doubt, call an electrician.

How to Tell Which Problem You Have

Start with the symptom.

If the light changes brightness repeatedly but stays visible in the app, look at scenes, schedules and other automation. If it flickers rapidly with no automation running, dimmer compatibility or driver trouble moves to the top. If it turns on right after a brief outage, check its power-restoration setting, and test it, because devices can treat rapid power cycling differently from a longer outage and the same setting name may not behave identically across brands. If it stops responding after someone uses the wall switch, ask whether the switch cut power. And if the bulb works fine as a light but intermittently disappears from the app, turn to the network and controller side.

For mystery turn-ons, review schedules and scenes in the manufacturer's app, then every connected platform. Where logs exist, see whether a command lines up with the event, and remember that not every platform logs everything. If the light keeps changing with no apparent command, look at power restoration and electrical behavior.

The Bard's Take

A traditional bulb had one job. Apply electricity and it made light; remove it and it stopped. A smart bulb still does that, but it also converts power, talks wirelessly, stores settings, obeys automations, and sometimes juggles several channels of colored LEDs. That complexity buys things that would have seemed remarkable not long ago. It also buys new ways to be surprised.

A flickering light may be sitting behind an incompatible dimmer. A bulb that glows when switched off may be catching a tiny leakage current. A light that comes on after an outage may be following its startup behavior. A bulb that vanishes at the wall switch has lost the power that keeps its radio alive. And a light that changes brightness for no reason may be obeying valid commands from automations that never agreed on anything.

From the outside these look alike. Their causes aren't. So look at the whole system rather than blaming the bulb or the network by reflex. Is the load compatible with the wall control? Does the bulb get continuous power? What happens after an interruption? Which controllers can issue commands?

Because when your hallway lights come on at three in the morning, the explanation probably isn't that your house has become self-aware. Your smart bulb isn't necessarily doing something wrong. It may be doing exactly what its electronics, wiring or software told it to do, even when that's the last thing you expected.

Sources