Most Commercial Lighting Jobs Don't Need Zigbee Controllers. Here's When They Actually Do.

I'm a project manager at an electrical distribution company. Over the past 11 years I've handled somewhere around 800 emergency orders, most of them calls that come in 72 hours before a deadline with a variation of: "the high bays won't switch on," or "the inspector is hung up on the sensor logic."

If you take one thing from this article: Zigbee lighting controllers are the most overspecified piece of hardware in commercial lighting right now, and the majority of jobs that include them don't actually need them.

I'm not anti-technology. I've sold more Cooper Lighting Zigbee systems than I can count. They work. The problem is that contractors confuse works well with fits this job. In a rush order, that confusion costs you about five hours.

Let me rephrase that: Zigbee is a good answer to a very specific question. It's a bad default.

Commissioning time eats your entire buffer

Last November, I was working a 60,000 square foot warehouse retrofit with a contractor who needed to clear inspection by 10 a.m. Friday. The order shipped with factory-mounted Zigbee modules, a gateway, and a commissioning coordinator.

Commissioning took four hours. That's on a network that actually came up on the first try. We had metal racking blocking signal in two zones; we had to drop in a repeater mid-project. Another 90 minutes gone.

The job was doing exactly one thing: someone walks by, the lights come on. That's it. A basic occupancy sensor with a dimming driver would have been a 45-minute job for a single electrician.

When I'm triaging a rush lighting order, I ask three questions, in order: how many hours until inspection, can this configuration pass on the first try, and what's the worst case if it doesn't. Zigbee is the wrong answer on question two more often than people want to admit.

More failure points, and most of them don't show up until commissioning day

Every Zigbee node has to sit on a compatible driver, inside gateway range, on a firmware version that speaks the same language as the coordinator. Sounds simple until you're standing in front of a pallet of fixtures that got shipped with a driver generation the gateway can't see.

I got burned on this in 2022. A batch of Halo fixtures shipped with factory-installed control modules but the batch of gateways had a firmware status that was — let's call it stale. Not visible on inspection. It blew up on commissioning day.

We ate an $800 rush charge to bring in a replacement gateway by Monday, but the real damage was time. The customer was standing there waiting for sign-off. They were decent about it, but I lost credibility that I should not have needed to spend.

That was the day I changed our internal rule: any order with control accessories gets a compatibility matrix check before the PO goes out. Not because I'm cautious — because I got tired of explaining firmware versions to a facility manager at 7 a.m.

Where Halo and Prevail actually fit into this

Cooper Lighting's portfolio covers a wide spread of lighting controls. Prevail is their area and high-bay line; if the project doesn't need complex zoning or scene programming, Prevail with a standard sensor gets you there more reliably than a stack of Zigbee controllers. That's not a knock on the Zigbee line — it's a match between the tool and the job.

Halo is a similar story. Lots of practical, low-friction options — occupancy sensors, straightforward dimming — that don't require a network to function. For a light-commercial space with basic on/off and daylight response, those are the right call in about nine out of ten cases.

If I'm being honest, the classic mistake I made in my first years in this role was selling whatever looked most advanced on the spec sheet instead of what would survive an installation. I sold a fully networked lighting controls package to a small retail buildout when a simple wall-box sensor plus a photocell would have done the job. The controller itself worked fine. The commissioning caught a driver mismatch and we lost two days. The client didn't say anything, but they didn't call me for the next two projects either.

When Zigbee is genuinely the right call

Here's my rule of thumb. If the space won't be re-zoned at least twice a year, Zigbee is probably a cost you don't need to pay.

The jobs where it earns its place: a multi-booth exhibition hall with moving partitions, a leased office floor where tenants subdivide their suite every time a lease renews, a facility that has to tie lighting into a broader building management system. Those are real problems that a dumb sensor can't solve.

But a hundred-thousand-square-foot warehouse running 20 hours a day? A retail floor with fixed aisles? A manufacturing bay where the workstations haven't moved since 2019? You don't need a mesh network to turn lights on when someone walks past.

One more thing — outdoor sensor placement, since people keep asking

I got a call this morning asking where to install motion sensor lights outdoor. My answer never changes: mount eight to ten feet in front of the fixture panel, facing the direction of approach. Not aimed at a wall that reflects light back into the lens. Not behind a tree. And keep the sensor out of direct afternoon sun if you can — you'll get false triggers and fighting with the dimming logic, and neither of those is a Zigbee issue or a Halo issue, it's a placement issue.

I've seen fixtures mounted at 20 feet expecting the sensor to pick up foot traffic from below. It doesn't. That's not a controller problem. That's someone skipping a page in the install guide.

But you sell these things — aren't you talking against your own revenue?

I get this question. Fair question.

My answer: I sell what gets the job through inspection, not what looks best on a quote. Cooper Lighting makes sense of that — they publish a full range from simple wall-box sensors up through Zigbee networks, because the market has both kinds of jobs. My job is figuring out which one is sitting in front of me. If I push Zigbee onto a warehouse that only needed a wall sensor, I don't gain a customer. I gain a callback.

Last quarter I talked three contractors out of Zigbee configurations they had already quoted. Two of them came back with new projects in the following month. That's the trade I'll take.

Zigbee controllers aren't the problem. Treating them as the starting point is. For a contractor trying to hit a deadline with a fixed budget, the only question that matters is whether the space will actually get re-configured in the next two years. If the answer is no — and it usually is — a basic sensor setup will get you to inspection faster, with fewer gateway calls, and fewer conversations about firmware.

That's not a knock on the hardware. That's just what holds up when the clock is running.