It's 4:47 on a Thursday afternoon. You've just wrapped up a retail fit-out, and the client sends a video of the ceiling lights cycling on and off. Six Legrand sensor light switches, all brand new. The store opens in 48 hours. The landlord walkthrough is tomorrow at 9 AM. And the client's question lands in your search bar: 'legrand occupancy sensor programming — what did I do wrong?'
I know that hour. In my role coordinating lighting controls for commercial jobs, I've been on the receiving end of that text more times than I can count. Emergency callbacks, same-day turnarounds, sensors that seem to have a mind of their own. Over the years it's been maybe 200 sensor-related service calls — okay, 180, I'd have to check our system — but the pattern is so consistent that I can tell you right now what's usually going on.
The sensor is almost never mis-programmed. The problem is almost always in the wiring, the load, or the network. And until you look there, you can press those buttons for another hour and nothing changes.
What You Think Is Wrong: Programming
Start with what's easy to blame. The manual for a Legrand sensor light switch gives you a service mode, sensitivity levels, and a timeout adjustment, so it's natural to assume you hit the wrong sequence. The usual guesses look like this:
- PIR sensitivity is set too low, so the sensor doesn't see anyone.
- Timeout is too short, so the lights cut off mid-task.
- The switch is left in vacancy mode when you wanted occupancy mode, or the other way around.
All three are real, and I've seen all three. But here's what I tell electricians who call me mid-panic: those account for maybe one in five callbacks. The other four come from things no amount of programming can fix.
What's Actually Going On
The Neutral Wire Problem
First suspect: the neutral. Many Legrand sensor light switches — especially the smart ones in the radiant and adorne lines that talk to the IoT gateway — need a neutral to keep their electronics awake. Some basic occupancy-switch models can run without one, but only if the LED driver cooperates, and a lot of them don't. When the load is an LED flood light or a driver with low standby draw, the sensor can't scavenge enough current to think. It forgets settings, wakes up dead, or cycles randomly. That's not a programming issue. That's a power-starved issue.
Also annoyingly common: the neutral is physically there but not connected. A previous electrician tucked it into the back of the box and never joined it. You get the exact same symptoms. I found one in March 2024, 36 hours before a retail reopening, after two hours of 'programming.' We opened three boxes before we found it.
The Wattage Question: Your LED Flood Light May Be Too Big — or Too Small
This is where the search 'what wattage led flood light' comes in, and honestly it's the right question to ask before you pair any fixture with a sensor. People pick flood lights like they pick speakers: bigger number means better. So they bolt a 200W LED flood light onto a sensor rated for a maximum LED load of 150W. It works for a while. Then it dies a slow, confusing death.
Here's the part people don't see: LED drivers pull inrush current at startup. The capacitors charge and draw several times the steady-state current for a few milliseconds. Every time the sensor switches that on, the contacts inside take a hit. Do it a thousand times with an oversized load and the sensor gets flaky. It doesn't fail clean — it just gets unreliable. And the client assumes you programmed it wrong.
The reverse is also true. If the fixture draws less than the sensor's minimum, the sensor can't tell that a load is connected. Lights flicker, stay on, or refuse to come on. That's not a bug. That's a mismatch between the datasheet and the fixture.
The Zigbee PIR Difference
The third place I look is the least intuitive: the network. A Zigbee PIR sensor is not a wired sensor with a radio bolted on. It's a small computer that sends messages through a mesh to a coordinator, which then talks to the rest of your zigbee devices, the gateway, or the building system.
Zigbee runs on the same 2.4 GHz band as Wi-Fi. A Zigbee PIR sensor has a tiny antenna, so if the band is crowded near the sensor, the coordinator can miss its messages. Lights start ignoring commands or responding late. The app shows the sensor as 'offline,' but the sensor is fine — it just can't be heard.
Then there's the mesh misunderstanding that bites almost everyone once: a battery-powered Zigbee PIR can't act as a router. It sleeps to save power. Only mains-powered zigbee devices can relay messages. So if a battery sensor is too far from the coordinator, it won't hop through another battery sensor. It needs a mains-powered router nearby.
I made this exact mistake on a two-story office retrofit. I assumed a Zigbee PIR would pair as easily as the one two meters away. It didn't, because the first one was close enough to a mains-powered repeater, and the second had two walls and a glass partition in the way. Repeaters fixed it, but it cost me a day and part of a night.
What This Really Costs
When a sensor misbehaves, you don't just lose a sensor. You lose a truck roll, part of your margin, and a little hard-won trust.
Here's the math. A Legrand radiant occupancy sensor runs about $30 to $50 at distribution. A Zigbee PIR sensor is more like $50 to $90 — based on our supplier's price sheet from January 2025. But a service call, with the diagnostics and the return trip, runs $150 to $250 in most markets. So a 'cheap' sensor that gets misdiagnosed costs three or four times its own price before anyone finds the real issue.
Then there's the emergency version. In March 2024, a retail client called at 3 PM with the store opening in 36 hours. Every sensor light switch in the back hallway was misbehaving. Missing that deadline would have triggered a $15,000 penalty clause. We found a neutral that was never tied into the first junction box, plus an oversized LED flood light in a service corridor. Total fix time: about four hours. But it was an emergency only because the basic checks happened after the drywall went up, not before.
Don't ignore the quiet costs either. A faulty sensor on an outdoor flood light can leave a 150W LED burning eight extra hours a night — roughly 440 kWh a year, which at typical commercial rates is $60 to $90 per fixture, every year, for one light. And if you're in California, Title 24 requires occupancy or vacancy sensors in a lot of commercial spaces. A sensor that doesn't sense is a compliance problem, not just an annoyance.
The Fix: Power, Load, Network — in That Order
Here's the short version. Run these three checks before you touch programming mode.
- Verify the neutral. Open the box and confirm it's terminated, not coiled in the back. If the circuit is two-wire and the switch needs a neutral, swap in a model designed for no-neutral installs or run a new conductor. You can't program around physics.
- Verify the load. Get the datasheet for the sensor and find the minimum and maximum LED wattage. Ask the 'what wattage led flood light' question now, before mounting: what's the fixture's real draw, and does it sit inside the sensor's range? If it doesn't, change one of the two before you energize.
- Verify the network. For Zigbee devices, walk the coverage area. Make sure the coordinator is Zigbee 3.0 compliant, the firmware is current, and there are mains-powered repeaters within range of every battery-powered PIR. The app won't tell you that a wall is blocking the signal. Your feet will.
Only after those three do the programming sequence: service mode, sensitivity, timeout, walk test. Programming is the last step, not the first.
One more thing, and it's the part most installers skip: know when to hand it off. I'm not a network engineer, so I can't help you design a large-scale Zigbee mesh for a factory floor with 400 sensors, metal racks, and heavy Wi-Fi. I can tell you when to call one. The specialist who says 'this part is outside my scope — here's who does it better' earns trust for everything else. I'd rather work with someone who knows their limits than a generalist who overpromises and leaves the client with a flickering light.
Stop Looking at the Wrong End
So the next time a sensor light switch misbehaves, pause before you run that 'legrand occupancy sensor programming' search for the third time. Check the power. Check the load. Check the network. The fix is hiding in one of those three places. It's almost never the buttons.