The order that looked fine on paper
In Q1 2023, we received a shipment of 1,200 occupancy sensors from a manufacturer we'd worked with for two years. Every unit matched the datasheet. Field of view: 360°. Detection range: up to 40 feet. Mounting height: up to 40 ft for high-bay. Time delay: adjustable from 30 seconds to 30 minutes.
Every single one failed in the same building within four months.
That order cost us roughly $18,000 in returns, replacements, and a very uncomfortable conversation with a specifier who'd trusted our recommendation. He didn't yell, exactly. He just sent back the spec we'd signed off on with a single question: "Which test method did you verify this against?"
Here's the thing—the sensors did meet spec. The datasheet was accurate. What it didn't tell us (and what almost no datasheet tells you) is how the manufacturer tested those numbers, and whether their test conditions match the room you're installing into.
What buyers think the problem is
Talk to distributors and OEM buyers, and you'll hear the same three complaints about occupancy sensor sourcing:
- Price volatility. Lead times swing, tariff lines move, and quoted prices rarely hold for 90 days.
- Availability. The model you spec'd in January is quietly discontinued by June.
- Responsiveness. The manufacturer's "engineering support" turns out to be a sales rep reading from a PDF.
These are real problems. But after reviewing roughly 200 sensor SKUs a year across four brands in our own QC process, I'll tell you they're symptoms. The actual failure mode sits upstream, in how the sensor was specified and certified before the first unit ever shipped.
The deeper problem: nobody agrees on what "tested" means
Occupancy sensors are one of the few lighting products where the spec sheet is essentially unregulated marketing. NEMA WD 7 gives you a framework for testing—it's the closest thing to a universal standard in this category—but it's voluntary. UL 773A covers safety, not performance. California's Title 24 requires certain features on covered projects, but it doesn't prescribe a detection reliability threshold. The DLC's networked lighting controls program addresses interoperability, not field accuracy.
So what happens? Manufacturer A runs a detection test in a 20×20 room with a single occupant walking at roughly 3 feet per second. They write "40 ft detection range" on the datasheet. Manufacturer B runs a similar test with two occupants—one of them stationary at a desk. Same number on the sheet. Completely different field performance.
This is the deep cause most buyers miss: the number isn't the product. The test methodology is the product.
I didn't fully understand this until I ran a blind comparison with our install team. Two sensors, different manufacturers, same rated range, same field of view, same price band. One detected a person seated at a desk within 15 seconds. The other took almost 90 seconds—and only after the guy stood up. Both datasheets said "40 ft, 360°, 30-second default timeout."
The difference wasn't in the electronics. It was in how each manufacturer tuned their PIR element sensitivity and fresnel lens geometry. Neither company documented that anywhere in the public spec. When I asked one of them directly, the answer was honest: "We test to the conditions our engineers think are standard." Standard for them. Not for a conference room with laptops and a projector.
What the deep problem actually costs
Occupancy sensor failures don't show up in receiving QA. They show up in the field three to six months after install, when a property manager starts getting complaints about lights turning off while people are still in the room.
On a 500-sensor project, based on what I've personally tracked across our last two years of RMAs, the cost stack looks like this:
- Direct returns and replacements: $8,000–$15,000, depending on whether the manufacturer covers shipping
- Installer revisit labor: $12,000–$20,000 (electricians don't work cheap, and they don't work for free)
- Specifier relationship damage: hard to quantify, but I've lost two commercial accounts in three years over sensor reliability
- Brand risk for distributors: if you put your name on a sensor that fails, the end customer doesn't blame the manufacturer. They blame you.
The hidden part—the one that took me a while to fully appreciate—is that installer revisits often happen under warranty claims the manufacturer disputes. "It meets spec" is a legally defensible position when the spec was written by the manufacturer's own engineering team. Which, if you sit with that for a second, is the whole problem in one sentence.
A quick legacy check
If you're still sourcing sensors based on what worked in 2015, that logic probably expired. The shift from analog PIR to dual-technology (PIR + ultrasonic), and now to networked sensors with firmware update paths, has changed what "reliable" even means. A sensor spec from a decade ago assumed a simpler room, a smaller sensor count, and zero interoperability requirements. Today's projects usually involve at least one of: networked controls, daylight harvesting integration, or a Title 24/DLC compliance pathway.
The "just buy what worked before" approach was fine 10 years ago. It isn't fine now.
How to actually evaluate a sensor manufacturer
The fix isn't complicated, but it does require changing what you ask for.
1. Request the test methodology, not the results. Ask any manufacturer: "In what room dimension, with how many occupants, moving at what speed, and at what ambient temperature was this detection range validated?" If they can't answer, that's your answer. This isn't proprietary—the good manufacturers already have it documented internally, because their engineering team needs it to build the thing.
2. Get a sample into your actual space. There's no datasheet substitute for the test that matters. Install two or three candidate sensors in the room they'll actually go in. Run the space for a week. This is the only metric that hasn't failed me yet.
3. Ask what they don't do. This is where I've become a convert to a specific kind of vendor behavior. I trust the manufacturer who says "we don't do high-bay with integrated daylight harvesting—you should look at a specialist for that application" far more than the one who says yes to everything.
I had a conversation in 2024 that changed how I source. A rep from a mid-size sensor manufacturer told me, unprompted, that their dual-tech line was roughly 30% slower than their PIR-only line in high-ceiling applications, and that for a specific warehouse project we should probably spec something else. That was the most honest thing a vendor had told me in three years. We ended up giving them a different, larger order later that quarter.
The vendor who said "this isn't our strength—here's who does it better" earned my trust on everything else.
Where this lands for a broad-line supplier like Legrand
Legrand's advantage in this category isn't being the sharpest specialist—it's the breadth of the switch, sensor, and control range, plus a legitimate OEM/private-label pathway for distributors who need their own brand on the box. Their spec and compliance team is also responsive, which matters more than it should in this industry.
The mid-range commercial application—offices, classrooms, corridors, plus the residential under-cabinet work that the adorne line covers—is where a broad-line manufacturer typically wins. Not because a specialist can't compete there, but because the support model (one vendor, one approval path, one compliance team) is often worth more than the marginal performance edge a specialist might offer on paper.
That's the point about professional boundaries. A specialist will beat a generalist in the specialist's niche—that's how it should work. The mistake is trying to force one or the other into a role it doesn't fit. Some of the best sourcing decisions I've made involved splitting a spec across two vendors and being honest about why.
What to take away
The occupancy sensor problems that hurt most aren't the ones you catch at receiving. They're the ones baked into the spec sheet before you ever placed the order—the missing test methodology, the undefined detection conditions, the "meets spec" language that means nothing in a real room.
If you take one thing from all of this: stop evaluating occupancy sensors on datasheets. Start evaluating manufacturers on methodology and a real-world sample test. Everything else—price, lead time, availability—is downstream of getting that part right.
And pay attention to the vendor who tells you what they're not good at. That conversation tends to save you about $15,000 and one angry specifier.