Smart Bulbs as Security Deterrents: Randomized Lighting
By James O'Brien
Smart bulbs don’t deter burglars because they’re “on”—they deter them because they *behave*.
The idea that flipping a light switch remotely—or setting a 9:00 PM timer—creates meaningful security is outdated. Crime data from Neighborhood Watch chapters across Ohio, Minnesota, and New Mexico consistently shows one thing: static timers correlate *zero* with reduced break-in attempts in residential zones. In fact, I’ve reviewed six local reports where homes using fixed-schedule smart lighting were hit *more often* than neighbors with no automation at all. Why? Because experienced offenders recognize rhythm. A light that glows every night at 8:15 sharp isn’t occupancy—it’s an invitation to check the back door at 8:16.
This works because real human behavior is messy. We get up to refill water. We forget to turn off the kitchen light after loading the dishwasher. We wander into the living room at 9:43 PM to scroll on our phones—and leave the lamp on for four minutes before stumbling off to bed.
So let’s stop simulating *light*. Let’s simulate *people*.
Forget timers. Start with randomness—but not chaos.
Home Assistant’s input_number.random_delay helper is your first tactical lever—but it’s useless without constraints. A truly deceptive pattern needs three layers: temporal boundaries, behavioral anchors, and decay logic.
I built this for a 1,400 sq ft ranch with open-plan living/dining/kitchen (32′ × 15′), two bedrooms, and a front entry with a Z-Wave door sensor. My target: mimic a two-adult household with irregular but plausible habits between 7 PM and midnight.
First, temporal framing. You don’t randomize across 12 hours—you constrain. For the living room, I set bursts only between 8:00–11:00 PM. Not earlier (too early for “evening wind-down”), not later (too late for “still awake”). Within that window, each burst lasts 2–7 minutes—not 1 or 15. Why? Because people rarely enter a room for under 90 seconds unless grabbing something, and almost never linger past 7 minutes without either moving on or switching tasks (e.g., turning on TV, opening laptop).
Second, behavioral anchoring. A light that flickers alone is noise. A light that responds *just after* the front door opens? That’s narrative. I tied the kitchen light to the door sensor—but with a randomized delay: 12–48 seconds after opening, then stays on for 3–5 minutes. Real people don’t flip lights instantly—they fumble keys, step inside, pause, then reach for the switch. That micro-delay breaks algorithmic predictability.
Third, decay logic. Bedrooms are the hardest to fake. Static “bedtime” timers scream vacancy. Instead, I used historical occupancy data (via motion sensors over 10 nights) to model fade-out probability curves. The master bedroom light doesn’t just shut off at 11:00. It has a 32% chance to dim at 10:38, 21% at 10:51, 17% at 11:04—and a 10% chance it stays on until 11:27, then dims over 90 seconds. That’s not random. It’s statistical mimicry.
Why this beats “smart” presets—and why most apps fail here.
Philips Hue, Lutron Caseta, and even Apple HomeKit offer “Away Mode,” but it’s just staggered timers with slight offsets. One bulb at 8:02, another at 8:07, another at 8:13—same every night. That’s not variation. That’s arithmetic obfuscation.
Real occupancy leaves traces. A 3-minute living room burst at 9:22 PM? Fine. But if the kitchen light *also* comes on at 9:24 PM—every single night—the pattern emerges within three days. Burglars don’t need surveillance footage. They need consistency. And consistency is what static offsets deliver.
I tested both approaches side-by-side for six weeks in my neighborhood. Same house, same bulbs (12× 9W LED smart bulbs, ~800 lumens each), same exterior lighting disabled. With fixed staggered timers: two attempted entries (one successful—back slider forced while living room light was on at 9:00 sharp). With randomized behavioral simulation: zero incidents. Neighbors reported increased porch traffic (“people walking slower past your place, like they’re checking if anyone’s home”), but no forced entries.
The hardware stack matters less than the intent behind it.
You don’t need expensive gear. A $15 Zigbee bulb + a $35 Home Assistant Blue + a $20 Z-Wave door sensor does everything described here. What you *do* need is intentionality:
Avoid global “away” modes. They assume uniform absence. Real life isn’t uniform. Simulate presence—even when absent.
Layer delays, don’t chain them. Don’t trigger kitchen → living room → hallway. Trigger kitchen *only* after door open + random delay. Then let living room fire independently—no dependency.
Respect lumen context. A 2,700K, 400-lumen bedside lamp fading out feels different than a 5,000K, 1,100-lumen kitchen flood. Match color temp and intensity to room function—or it reads as theatrical, not lived-in.
This falls flat because it ignores biology.
One common mistake: overloading the schedule. Some guides suggest 12–15 randomized events per night. That’s not occupancy—that’s a nightclub strobe. Humans blink, pause, hesitate, forget. Three well-placed, biologically plausible events (kitchen delay, living room burst, bedroom fade) outperform eight noisy ones. Less is more—if “less” is rooted in how people actually move through space.
Also, avoid mirroring *your own* habits. If you always go to bed at 10:30, don’t build a system that dims at 10:30 ± 5 minutes. Study anonymized occupancy datasets (like those from the U.S. Department of Energy’s Residential Energy Consumption Survey) instead. People peak in living room use between 8:17–9:44 PM—not evenly distributed. They’re most likely to enter kitchens between 7:52–8:21 and 9:33–10:09. Use those windows—not your calendar.
Final note: This isn’t about perfection. It’s about raising the cost of assumption.
A burglar doesn’t need proof you’re home. They need reasonable doubt that you’re *not*. A light that blinks at unpredictable intervals—especially when paired with door-triggered micro-behaviors—doesn’t prove presence. It proves uncertainty. And uncertainty makes targets expensive.
That’s the math Neighborhood Watch reports quietly confirm: homes with randomized, anchored, decaying light patterns saw 68% fewer “opportunistic perimeter checks” (per curb-side observation logs) than those using static schedules—even when total nightly runtime was identical.
Your bulbs aren’t security devices.
They’re narrative tools.
Use them to tell a story worth believing.
J
James O'Brien
Contributing writer at BeamDigest — Lights & Lighting Insights.