Legrand Request Project Review

Why ‘How Many Watts’ Is the Wrong Question for LED Bulbs (and What a Quality Inspector Actually Checks for Legrand Dimmers & Zigbee)

The question that gets it backwards

A few months ago, a project manager emailed me with a simple request: “We need 2,400 LED bulbs for the new office tower – what’s the wattage on the Legrand dimmer spec?” He’d already sourced a bulk deal at $1.20 per bulb. He wasn’t asking if they’d work with our dimmers, or whether they were Zigbee-compatible. He just wanted to confirm wattage.

That email is the exact reason I spend my days reviewing deliveries instead of doing procurement. Because if you ask “how many watts is an LED bulb” as your first question, you're already looking at the wrong number. In our Q1 2024 quality audit, I rejected 18% of first deliveries – and half of those rejections came from spec-misalignment that started with a wattage-only mindset.

What most people miss about LED wattage

Let me clarify something I see all the time. People think wattage equals brightness. That was true when incandescent bulbs were the norm – a 60W bulb gave roughly 800 lumens, regardless of brand. But LEDs shattered that relationship. Today you can buy a 9W LED that outputs 800 lumens and a 12W LED that outputs only 600. The wattage number tells you almost nothing about the light output unless you also know the efficacy (lumens per watt).

Still, this is the easier misconception to fix. The harder one is what happens when you plug that bulb into a Legrand dimmer or a Zigbee lighting system. I'm not an electrical engineer (I don’t design the circuits), but from a quality inspection perspective, I’ve seen the consequences of ignoring compatibility more times than I can count.

The real problem: dimmer load compatibility

Legrand dimmers – especially our Radiant and Adorne lines – have minimum and maximum load requirements. An LED bulb that draws 10W might be fine on a dimmer rated for 100W, but if the dimmer has a 25W minimum load, a single bulb on a circuit won't even turn on properly. This isn't a defect – it's physics. The dimmer needs enough current to maintain its internal electronics. Put too few LED bulbs or ones with low parasitic load, and you get flicker, premature dimmer failure, or bulbs that never fully turn off.

I ran a blind test with our field team in 2023: same Legrand dimmer, same 5-bulb fixture, but Bulb A was a “compatible” generic brand and Bulb B was a certified ENERGY STAR model with load specs matching the dimmer. 83% of the team identified Bulb A as “annoyingly flickering” and Bulb B as “smooth and professional.” The cost difference? About $0.35 per bulb. On a 2,400-unit order, that's $840 extra for measurable performance improvement.

The Zigbee layer – where things really break

Now add Zigbee connectivity. Many of our customers integrate Legrand smart switches with third-party Zigbee lightbulbs (Philips Hue, IKEA, etc.) or enterprise gateways like the Aruba Zigbee access points for hotel or office automation. The assumption is “Zigbee is Zigbee, so they’ll talk.” That’s like assuming two people who both speak English will agree on a business contract – the words are the same, but the implementation details differ.

We’ve seen reports where a Zigbee bulb would join the network but then randomly drop out because its reporting interval clashed with the gateway’s expectations. Another case: the bulb’s level control profile didn’t match the Legrand dimmer’s command set, resulting in on/off-only functionality (no smooth dimming). These issues don’t show up in a wattage measurement. They show up when the building manager gets complaints at 2 AM because the hallway lights are strobing.

The price of ignoring depth

I mentioned we rejected 18% of first deliveries in Q1 2024. One of those was a $22,000 redo. The project spec said “LED bulbs, 1800 lumens, dimmable.” The vendor sent bulbs that met the lumen spec but had a power factor of 0.5 and a dimming curve that only worked with their own dimmer. When we installed them on Legrand wireless dimmers, half the bulbs would not dim below 80% – they just turned off. The client was furious because they’d paid for “architectural-grade dimming.” We had to tear out 8,000 units and start over. The vendor blamed us for not specifying “Zigbee profile type.” But guess whose contract pays for the reinstall? (Hint: not the vendor.)

That $200 savings per thousand bulbs turned into a $22,000 problem.

So what should you check instead?

I’ve seen this pattern enough times to offer a shortlist (I'm not a lighting designer, but I have reviewed over 500+ bulb SKUs in three years):

  • Check the dimmer’s min/max load curve – Legrand publishes compatibility lists for every dimmer model. Use them. If you’re using occupancy sensors, note that sensors add their own minimum load.
  • Verify the Zigbee device ID and profile – Not all Zigbee bulbs implement the same clusters. Look for “Zigbee 3.0 certified” and, preferably, bulbs that list explicit Legrand compatibility.
  • Look at the total cost of ownership, not the bulb price – A $1.20 bulb that causes a $22,000 rework is not a $1.20 bulb. I keep a spreadsheet of every rejection and the downstream cost. On average, each rejected bullet point costs 14× the unit price in labor and lost time.
  • Don’t ignore power factor and THD – Low power factor bulbs can overload neutral conductors in large installations (per NEC 2023, derating may be required). That’s an electrical code issue, not just a quality preference.

If you’re specifying for a project that integrates Legrand lighting controls, ask your supplier for an engineering sample first. Test three bulbs with your exact dimmer and gateway. It takes an afternoon and saves you the headache of a rejected batch.

And the next time someone asks you “how many watts is an LED bulb,” maybe reply: “What’s your dimmer’s minimum load, and do you have a Zigbee compatibility matrix?” They’ll think you’ve been in the industry for years (and if you’re using Legrand products, you probably have the resources to back it up).

Why this matters

Use this note to clarify specification logic before compatibility questions spread across too many conversations.