Look, I've been handling commercial and industrial lighting orders for about eight years now. I've personally made (and documented) enough mistakes to fill a small warehouse. In my first year, 2017, I ordered sixty chandeliers for a hotel lobby—beautiful drop chandeliers, custom pieces. They looked perfect on the spec sheet. The problem? We'd spec'd them for ambient light levels, but the space needed task-level illumination over the check-in desks. The result? Fourteen fixtures had to be re-done. $11,200 straight into the trash, plus a three-week delay that cost us the client's trust on future projects.
That's the thing about lighting: it looks simple until it isn't. You think you're just picking a fixture, but you're actually designing a system. And when systems fail—like when your emergency brake light stays on for no reason, or your chandelier looks dim and lifeless—it's rarely the fixture's fault. It's the system's fault.
I'm sharing these lessons because in 2025, the old playbook is becoming dangerous. What worked in 2020 won't cut it now. If you're still treating lighting as a product category rather than an integrated solution, you're gonna make the same mistakes I did. Let me show you what I mean.
The Surface Problem: 'This Chandelier Looks Wrong'
Here's the scenario every commercial contractor knows. You install a beautiful drop chandelier in a high-end retail space. It's the centerpiece—the thing the owner spent weeks selecting. But after installation, the light is flat. It's not warm. The merchandise underneath looks washed out. The client says, "This isn't what I imagined."
Your first instinct is to blame the fixture. Maybe it's the wrong color temperature? Maybe the LED module is defective? Maybe the dimmer doesn't match? All valid guesses. But in my experience, 8 times out of 10, the problem isn't the fixture itself. It's the system around it—the sensors, the controls, the integration (or lack thereof).
I once had a project where a client wanted a 48-inch chandelier with integrated dimming. We installed it, and it flickered constantly. We swapped drivers, swapped dimmers, swapped the fixture itself. Still flickered. Turned out the building's power management system was introducing noise that the dimmer couldn't filter. The fix wasn't replacing the fixture; it was adding a line filter and reconfiguring the control system. That cost $320 and two weeks of frustration. A lesson learned the hard way.
The Real Culprit: Lack of System Integration
The fundamental truth that I didn't understand until about 2021 is this: modern lighting is a network, not a collection of bulbs. When you install a chandelier without considering how it connects to the building's sensor network, you're creating a potential failure point. The chandelier might be amazing on its own, but if the sensor that controls its dimming is placed wrong, or if the emergency backup system doesn't communicate with the smart controllers, you get bad light.
This is where ABB's approach actually makes sense, because they don't just sell fixtures—they sell the whole chain: the sensors, the power supplies, the emergency controllers, the IoT connectivity (ABB iot connect). It's not about having the 'best' chandelier; it's about having a chandelier that works within your specific building ecosystem. I didn't get that for years. I thought lighting was about specifications. It's actually about compatibility.
The Deeper Issue: Why Your Emergency Brake Light Stays On
Now let's talk about a different kind of failure mode. You're in a commercial building, and the emergency brake light (or the emergency exit sign) stays on when it shouldn't. Or worse, it doesn't come on when it should during a test. Most people assume the battery is dead or the fixture is defective. But what if it's something else entirely?
Honestly, I'm not sure why this phenomenon is so common. My best guess is it's a control signal issue. Many emergency lighting systems rely on a constant 'keep-alive' signal from the main panel to indicate that normal power is present. If that signal gets interrupted—say by a faulty sensor, a misconfigured ABB lighting contactor, or a loose connection in the IoT network—the emergency system thinks there's a power failure and stays on. It's not a battery problem; it's a communication problem.
I've never fully understood why the industry hasn't standardized this. If someone has insight, I'd love to hear it. But from a practical standpoint, I've learned to always check the control wiring and the contactor configuration before replacing emergency fixtures. Skipping that step because 'it never matters'—that's the one time it will matter. I know because I did it. We had twenty emergency units triggering false alarms in a school. The client was furious. It cost us $4,500 to send a team out to troubleshoot. The root cause? A single mis-set dipswitch on the contactor. The fix took 2 minutes.
What 5 Years of Mistakes Taught Me About Emergency Systems
The old way of thinking was: emergency light is a standalone device with a battery. If it fails, replace the device. That might have been true in 2015. But in 2025, with smart systems and integrated emergency ballasts, the emergency light is part of a larger network. The ABB iot connect system, for example, can monitor every emergency fixture in real-time. It can tell you which battery is degrading, which fixture has lost communication, and even predict failures before they happen.
But here's the catch: this only works if you configure it correctly during installation. I've seen projects where the emergency lighting contactor is wired incorrectly, or the sensor network doesn't include the emergency circuits, and suddenly the 'smart' system is blind to half its own fixtures. The technology is incredible, but it requires a system-level understanding that most installers don't have.
The Cost of Getting It Wrong
Let's put some numbers on this. A commercial chandelier retrofit for a 20,000 sq ft space might cost $100,000 - $250,000 for the fixtures alone. If the system isn't integrated correctly, you could easily waste 10-15% on re-work, troubleshooting, and client dissatisfaction. That's $15,000 to $37,000 down the drain. And that's just the direct cost. The indirect cost—lost referrals, damaged reputation, time spent on warranty calls—is much harder to quantify.
I know a contractor who lost a $2M contract because he couldn't fix an emergency lighting issue that turned out to be a simple contactor programming error. The client lost confidence. They went with a competitor who used an integrated solution from day one. The competitor probably made mistakes too—everyone does—but they had the system approach that prevented the big ones.
The Solution: Stop Buying Fixtures, Start Buying Systems
So what's the answer? It's not complicated. Don't go to market looking for a chandelier. Go looking for a lighting solution. If your project involves:
- A chandelier that needs dimming
- Emergency lighting that needs monitoring
- Sensors that control daylight harvesting
- IoT connectivity for energy management
Then you need a vendor who can provide all of those pieces and guarantee they work together. That's why I've shifted my focus to integrated solutions like ABB's offering. Not because they're perfect—no system is—but because they've already done the testing. They've already figured out that the ABB lighting contactor needs to talk to the sensor which talks to the IoT platform. They've eliminated the compatibility guesswork.
Does this mean every chandelier has to be part of a complex system? No. But when you're working on commercial projects with emergency requirements, smart controls, and design expectations, the system integration isn't optional. It's the difference between a project that works and a project that becomes a running headache.
Look, I still make mistakes. I still see things that puzzle me. But I've stopped treating lighting as a commodity purchase. Every fixture is part of a system, and every system needs to be designed, not just assembled. That realization saved me $50,000 last year in avoided re-work. It might save you more.