You're standing in the dark, waving your arms. The fixture above you stays off. The immediate thought: 'the sensor is dead.' Not so fast.
In my role as a lighting service coordinator for commercial facilities, I've handled 200+ emergency sensor callouts. In most of them, the sensor was fine. The thing it was controlling? That's where the story gets complicated.
The Problem You Think You Have
From the outside, it looks like a broken sensor. The reality is often a mismatch between the motion sensor and the load it's switching.
Here's the thing: modern LED drivers are not light bulbs. They're electronics with minimum load requirements, inrush currents, and behavior quirks that old motion sensors were never designed for. A sensor rated for 500 W incandescent may click, flicker, or refuse to turn off when connected to a few LED modules.
People assume the sensor is the weakest link. What they don't see is the driver board and thermal path hiding inside the fixture.
The Deep Causes Nobody Tells You About
1. The real load is the driver, not the LED
Take something like an Osram 1W high power LED. It's a tiny component that produces a lot of light for its size. But it doesn't run on mains voltage. It runs on a constant-current driver. That driver decides how the LED turns on, dims, and shuts off.
If the LED driver draws less current than the sensor's minimum load rating, you get the classic symptom: the light turns on and then immediately flickers or stays on forever. The sensor isn't dumb. The driver isn't broken. They simply don't speak the same electrical language.
I've also seen the opposite: a 'bad' motion sensor that was actually a damaged capacitor in the driver causing enough noise to confuse the sensor's electronics. Replacing the sensor costs money. Understanding the driver saves money.
2. Zigbee dimming is not what most people think
If your motion sensor is part of a smart system, the problem may be in the wireless stack, not the sensor.
Zigbee dimming is a set of command clusters—not a magic 'it works with every Zigbee device' list. A motion sensor sends an ON command. After the timeout, it sends an OFF command. But if the LED driver's Zigbee dimming implementation doesn't handle that OFF command properly, the light may:
- stay at 10% forever
- ignore the OFF and keep running
- turn on with a 5-second delay
Wait, BLE Zigbee confusion is everywhere. Many smart lighting systems use Bluetooth Low Energy for commissioning—the phone-to-fixture handshake—and Zigbee for the actual mesh network. So the app says 'connected' over BLE, the sensor says 'ON' through the Zigbee mesh, and somewhere in that bridge the message gets dropped. That's not a knock on systems like Osram Lightify—Zigbee is a solid foundation. It just means you need to respect the stack.
I watched a facility call me three times for the same motion sensor issue. New sensor, new bulb, new driver. Still wrong. Then a network guy looked at it and saw the Zigbee coordinator had rolled back its firmware after a cloud outage. The sensor was fine all along.
3. Look close enough and you might see the real issue
I use the same principle as when I'm inspecting an Osram Night Breaker 200 H7 bulb close up. The glass dome is what you notice, but the real story is the filament, the gas fill, and the tolerance of the base. With LED fixtures, the lens is the glass dome. The driver, thermal interface, and radio module are the real anatomy.
In March 2024, a client called at 3 p.m. because a loading dock light was dead. They had a replacement sensor in hand and wanted me to install it. A close-up look at the fixture showed the LED module was fine, the sensor was fine, but the neutral wire had backed out of the wire nut. Thirty minutes later, the light worked. No parts needed.
Sometimes the answer is that boring.
The Hidden Cost of Assuming It's the Sensor
I have mixed feelings about smart motion sensors. On one hand, they solve real problems—like a security light that follows a schedule or alerts your phone. On the other, they add a BLE/Zigbee dependency that can turn a simple lighting issue into a debugging project.
That hidden cost adds up. Replacing a good sensor, paying a second trip, losing a night of security lighting—these are real expenses. Based on our internal data from 200+ lighting emergency callouts, around 40% of sensors replaced in the last two years could have been left in place if someone had checked the load type and the wireless network first.
Take it from someone who has paid the price: a 'quick fix' without diagnosis is rarely the cheapest solution.
The delay also has consequences you can't invoice. A retail loading dock with no lights means a trailer sits unloaded, schedules slip, and the mistake gets talked about in a way that no one's service fee covers.
What I'd Check First (Keep This Simple)
This isn't a complete smart-home integration guide. That's not my lane. If you need help with network architecture, find someone who specializes in Zigbee/Bluetooth commissioning. A good specialist will tell you when they're outside their lane.
But for the lighting side, do these before touching the sensor:
- Swap in a known-good load. If the light works with a basic incandescent or a compatible LED driver, the sensor is alive.
- Check the minimum and maximum load rating on the sensor. LED loads often fall below the minimum.
- Check the neutral and ground connections. Loose neutrals are the cause in more than a few 'motion sensor' callouts.
- Check the Zigbee network health. Look for firmware mismatches, coordinator issues, and signal interference from other 2.4 GHz devices.
- Use a dimmable driver that explicitly supports Zigbee dimming. 'Dimmable' alone is not a compatibility promise. Per FTC guidelines (ftc.gov), compatibility claims should be substantiated—if a product doesn't say which standard it supports, assume it's not supported.
When you find a supplier or manufacturer who says 'this isn't our focus—here's who does it better,' listen. The vendor who admitted that to me earned my trust for everything else. I'd rather work with a specialist who knows their limits than a generalist who overpromises.
'The vendor who told me this isn't our strength—here's who does it better—earned my trust for everything else.'
Real talk: fixing a motion sensor light isn't about throwing a new sensor at the wall and hoping. It's about looking past the glass dome, checking the driver, and asking whether the wireless layer is doing its job. That's the field-tested version. Simple.