I've been handling lighting controls procurement and project delivery for seven years. I've personally made — and documented — 11 significant mistakes, totaling roughly $47,000 in wasted budget. Now I maintain our team's checklist to prevent others from repeating my errors.
The most expensive one started with a decision I thought was straightforward.
It was 2019. We were doing a commercial office renovation in Los Angeles — about 42,000 square feet, six floors, existing base building systems. My job: source a lighting control package. 420 fixtures, 86 occupancy sensors, 14 zone controllers, and a gateway that needed to talk to the building management system.
I figured this was a procurement problem. Compare specs, negotiate pricing, place the order. Done.
What I Thought the Problem Was
I ran the process the way I'd been taught. Request quotes from four occupancy sensor manufacturers. Compare the spec sheets — voltage, dimming curve, coverage pattern, self-test capability, price. Go with Manufacturer A because their spec sheet looked the cleanest and their sales rep answered emails fastest.
The pricing? $52–68 per sensor. Reasonable. Lead time: 12 business days. Tight, but workable.
What I didn't ask: whether these sensors would actually communicate with the lighting control gateway we'd already specified.
The electrician on site called me about 40% through installation. "Some of these sensors aren't reporting status. Gateway can't see them."
Not all of them — just 19 units out of the same batch. Turns out, the "standard" Zigbee profile my supplier used wasn't quite the same Zigbee profile the gateway expected. The supplier's own gateway worked fine with them. That part was true. But cross-vendor integration was a different story.
$3,200 in sensors that couldn't be returned because they'd been opened and partially installed. Nine hours of electrician time to rewire and replace. Plus a two-week delay on the project timeline.
I said "standard Zigbee compatibility." They heard "standard" meaning "whatever ships in our default configuration." We were using the same word and meaning different things. I discovered this when the gateway logs showed 19 sensors simply not existing on the mesh network.
What's Actually Going On
That mistake taught me something deeper than "check compatibility." It taught me that the entire way we evaluate lighting control vendors is upside-down.
Here's the thing: you're not buying products. You're buying everything that happens after the products arrive.
Take a Lutron motion sensor switch. Simple, right? You see the spec sheet, you see "compatible with Lutron systems," and you assume you're covered. But what actually matters isn't printed on the spec sheet:
- Protocol nuances. "Zigbee," "Zigbee 3.0," and "Zigbee-based proprietary" can mean three very different things for compatibility. A Zigbee supplier saying "compatible" might mean "works with our own gateway."
- Firmware versioning. Your gateway's firmware version can change how it talks to sensors in one way or another.
- Wiring topology. The same sensor on a different circuit layout can behave differently.
At least, that's been my experience with commercial builds where multiple subsystems are involved.
And here's the second thing: you're not just evaluating products. You're evaluating whether the vendor understands their own boundaries.
I learned this the hard way in 2023 while sourcing ceiling light manufacturers for a retail project. One supplier claimed they could handle everything — fixtures, sensors, integration, the whole package. Great. Except their control layer was a mess, and when I asked a specific question about Zigbee channel allocation, the rep clearly didn't know.
A different supplier — smaller, less impressive website — told me flat out: "We don't do control systems. But here are three companies we've worked with that do."
I trust that second supplier with everything else now. The vendor who says "this isn't our strength — here's who does it better" earned my trust for the work they actually do well.
Look, I'm not saying generalists are always bad. I'm saying specialists who know their limits save you from the kind of expensive surprises I've lived through.
What It Actually Costs When You Get This Wrong
Let me put real numbers on this, because "it's expensive" doesn't mean anything until you see the invoice.
Direct cost of my 2019 mistake: $3,200 in unusable sensors. Plus $1,800 in expedited shipping to get replacements fast enough to stay on schedule.
Indirect cost: The project slipped 11 days. On a 42,000 sq ft commercial renovation in Los Angeles, every day of delay has a carrying cost. I want to say it was around $4,500 per day in extended general conditions and lost rental income for the owner, but don't quote me on the exact figure.
The cost nobody talks about: Trust. That owner never gave us another project. Can't prove the delay caused it, but the timing was suspicious.
And then there's the compliance side — which is its own category of expensive.
In Los Angeles and most of California, Title 24 energy code requirements for commercial lighting controls are strict. If your occupancy sensors or lighting system don't meet the requirements — and the spec documentation doesn't demonstrate compliance — you're looking at plan rejection and redesign. I once watched a project get kicked back because a ceiling light manufacturer provided photometric data that didn't match Title 24 requirements for the specific space type. The fixture itself was fine. The documentation wasn't. Cost of redo: $23,000 and three weeks.
The Checklist I Actually Use Now
After the third rejection in Q1 2024, I created our pre-check list. We've caught 47 potential errors using it in the past 18 months.
Speed, compatibility, quantity. Pick two — and document all three.
Five things I check before approving any occupancy sensor manufacturer or Zigbee supplier:
- Cross-vendor test results. Not "compatible with Zigbee." I need to see: "Tested with [specific gateway model] running firmware [version] in a [number]-node mesh." If they can't provide this, I move on.
- Ask the uncomfortable question. Not "does this work with the system?" But "has this exact combination been deployed? On how many projects? Can I talk to the integrator who did it?"
- Value the vendor who says no. If a supplier tells me "controls aren't our strength," that's a data point in their favor — not against. It means they'll be honest about other limitations too. I'd rather work with a specialist who knows their limits than a generalist who overpromises.
- Title 24 documentation up front. For any California project: compliance certificates, photometric files in the right format, and evidence that the same fixture/sensor combo has passed plan check before. Don't accept "we'll provide that later."
- Site visit or reference check. If the supplier can't connect me with someone who's using their product in a real project — not a showroom — I consider that a red flag.
There's something satisfying about watching a plan sail through review because you did the boring prep work three weeks earlier. After all the stress of project timelines and budget pressure, seeing "approved" on the first submission — that's the payoff.
What I Still Don't Know
I don't have a universal answer for "which lighting controls supplier is best." I don't think one exists. The variables — building type, local code interpretation, existing infrastructure — are too specific.
Part of me wants to find one vendor who handles everything so I can simplify my life. Another part knows that redundancy and specialization saved us during that supply chain mess in late 2021. I compromise by keeping a primary vendor plus a backup for critical components.
What I do know: the gap between \"looks compatible\" and \"actually works together\" is where $47,000 goes to die. The difference isn't knowledge. It's knowing the boundaries of what you — and your suppliers — don't know.
