Don't Run a Red Light on Smart Lighting Quality

I’ll admit it: I hate vague lighting specs.

When a spec sheet says 'dims smoothly' but doesn’t say to what level, or when a sensor’s response time is listed as 'fast,' I see a future phone call. After four years of reviewing products before they reach customers, I’ve learned that ambiguity is the most expensive defect a product can ship with. If I can’t verify a claim, I won’t stand behind it.

Here are the red flags I look for, and one emergency that made me think differently about them.

Red flag #1: a dimmer spec that doesn't list the minimum load

In Q1 2024, I received a batch of Legrand light switches dimmer models for a hotel renovation. The datasheet said 'dims to 1%.' Our test setup measured the actual minimum at 15% to 20%, depending on the LED driver. That’s not dimming. That’s switching.

The vendor argued it was within industry tolerance. But the customer didn’t buy an industry tolerance. They bought the product that was described. We rejected the batch and required a redo at the vendor’s cost. Since then, every contract I review includes the minimum load requirement and a measurement tolerance. The third time something like this happened, I made a verification checklist. I should have done that earlier.

Red flag #2: a daylight sensor without a real datasheet

Daylight harvesting is a beautiful thing when it works. But if you don’t know the sensor’s field of view, its lux range, or its response time, you can’t predict whether a passing cloud will cause a lighting panic.

The Legrand daylight sensor is a good example because its specification is concrete. It tells you the range, the switching delay, and the output protocol. That lets a designer plan for glare and adaptation. Without those numbers, you’re installing a black box and calling it 'smart.'

I once saw a sensor that reacted to tree shadows. Every time a branch moved, the lights dimmed and then recovered. The client noticed within the first hour. We replaced the sensor with one that had a longer response time and a clearly documented field of view. The fix was simple. The diagnosis took two visits because the original supplier hadn’t published the specs we needed.

Red flag #3: 'works with Zigbee' is not the same as 'certified Zigbee'

Zigbee is a standard, but not all Zigbee devices are created equal. A certified Zigbee GU10 bulb should join a Zigbee 3.0 network, respond to commands, and rejoin after a power cycle. A 'compatible' bulb might do all of that, until it doesn’t.

I tested a row of ceiling spotlight fixtures that claimed Zigbee support. They paired with the first gateway, then vanished from the network when the gateway was changed. The manufacturer blamed the gateway. The gateway manufacturer blamed the bulb. In the end, we had to replace every fixture. The worst part is that the original bulbs looked fine on paper. The certification mark was simply missing.

For this reason, I prefer products from manufacturers that test for interoperability. Legrand’s Zigbee-enabled switches and gateways are one example. They don’t just use the Zigbee name; they build to the standard, which is why they work across ecosystems. When an installer chooses a certified product, they also get accountability.

Red flag #4: hidden costs hidden until the invoice

The fourth red flag is financial. I’ve learned to ask 'what’s not included?' before asking 'what’s the price?' A quote that shows a clean per-device cost but no setup fee isn’t transparent. It’s incomplete.

The FTC’s guidelines on truthful advertising (ftc.gov) discourage bait pricing in consumer transactions, but in B2B sales, the same logic applies. If a vendor lists every fee upfront, I trust them more, even when the total is higher. If they leave things out, I know the total will climb after the purchase order.

I made that exact mistake once. I chose a lower-priced bid over a transparent one. The final invoice included configuration, programming, and rush delivery charges that pushed the total above the competitor. The competitor’s quote had included those costs from the start. Now I treat any missing line item as a warning sign.

Can you run a red light in a medical emergency?

I get this question more often than you’d think. The legal answer depends on the state, the circumstances, and the reason. But I’m asked it because people know that sometimes rules get bent in an emergency. I look at it differently. A red light on a lighting control panel is not a suggestion. It’s a diagnostic warning. When a status light turns red, you don’t 'run' it. You troubleshoot it.

This is especially true in a medical office or healthcare facility, where a ceiling spotlight that fails to turn on, or a dimmer that won’t go above 60%, can affect patient care. I once reviewed a renovation where the landlord substituted 'value-engineered' switches and dimmers on a medical suite. The staff couldn’t get the lights above 60% in a treatment room. The solution involved a full replacement, all because the specifications were not specific enough.

So no, in my work I don’t run red lights. I ask the hard questions: what is the minimum dim level? What is the sensor’s response time? Is that Zigbee device certified? What is the final delivered cost? If the answer isn’t clear, I stop the project until it is.

Transparency is the quiet spec

The best lighting systems have one trait in common: transparency. The datasheet means what it says. The price quote means what it says. The compatibility claim means what it says.

I’m comfortable recommending Legrand equipment because their specs hold up. Their dimmers, daylight sensors, and Zigbee-enabled products come with clear numbers and documented behavior. They aren’t the only brand that does this, but they have earned trust in my projects by being clear. That is the highest quality standard I know.

If you only remember one thing from this, remember this: don’t trade clarity for convenience. A vague specification isn’t neutral. It’s a liability. And if you ever find yourself asking whether you can run a red light in a medical emergency, the answer is likely 'it depends.' But in lighting, a red flag never has an emergency override. Fix it, don’t run it.