Let me start with a confession: I messed up my first smart lighting retrofit. Badly.
It was a 50,000-square-foot warehouse in Q3 of 2023. We installed brand-new LED fixtures with IoT connectivity—sensors, controls, the whole works. Looked great on paper. Looked great on installation day. But three weeks later, half the system wouldn't talk to the other half. Lights flickered. Sensors dropped offline. The facility manager was (rightfully) furious.
The culprit? Zigbee channel interference. I'd overlooked a simple thing. A lesson learned the hard way, costing roughly $3,200 in extra commissioning and a two-week delay.
After that, I started documenting every mistake, and I've made plenty more since. This article covers the questions I wish someone had answered before I started. The real cons of smart lighting, the Zigbee channel gotchas, and why “IoT platform connect” isn't just a marketing phrase—it's the difference between a system that works and one that doesn't.
1. What are the actual cons of smart lighting? (Besides the obvious)
Honestly, the biggest con isn't the upfront cost. That's the easy one to spot. The real pain points are:
Integration complexity. I don't mean just wiring. I mean getting a lighting system to talk to an existing BMS (Building Management System). If you're retrofitting into an older building—think pre-2018 construction—you're often dealing with proprietary bus systems, odd voltage requirements, and limited space in ceiling plenums. We once spent a full day just figuring out how to run a control cable next to a high-voltage line without picking up interference. Not ideal. Workable, but not ideal.
Dependency on network reliability. Smart lighting is only as smart as the network it lives on. If your Wi-Fi or mesh network has a hiccup, the lights might default to full brightness, or worse, stay off. For emergency lighting, that's a liability.
Vendor lock-in is a thing. Once you build your control ecosystem around a specific IoT platform—ABB Ability, for instance—migrating to another platform later is painful. It's not impossible, but it's way more than swapping a hub. You're re-commissioning hundreds, sometimes thousands, of endpoints.
Per ABB's retrofit guidelines (and honestly, my own experience), the most underestimated con is the training curve. Facility staff need to understand the system. If the electricians who installed it don't know how to troubleshoot a sensor that's gone blind, you're making service calls that cost more than the fixture itself.
2. What the heck are Zigbee channels, and why should I care?
I'll keep this simple. Zigbee is a wireless protocol—basically a language that smart devices use to talk to each other. It operates in the 2.4 GHz frequency band.
Here's the problem: so does Wi-Fi. So do Bluetooth devices. So do microwaves.
Zigbee divides the 2.4 GHz band into 16 channels (numbered 11 through 26). Wi-Fi channels typically overlap with Zigbee channels 11, 15, 20, 25, and 26. If your Wi-Fi network is blasting on channel 6 (which overlaps with Zigbee channels 11-13), and your Zigbee network is set to channel 12, you get interference. Lights flicker. Commands get lost. Sensors report false readings.
This isn't a theoretical problem. In September 2022, I helped a client whose conference room lights kept turning off during presentations. Turned out the IT guy had set the company's guest Wi-Fi to channel 1 (overlapping with Zigbee channel 11). The lights were on Zigbee channel 11. Took us two hours to diagnose. A simple channel change—moving Zigbee to channel 15—fixed it instantly.
According to the Zigbee Alliance (now Connectivity Standards Alliance) white paper on coexistence, the best practice is to pick a Zigbee channel that doesn't overlap with your most-used Wi-Fi channels. For enterprise environments, channels 15, 20, or 25 are commonly recommended—if they're clear.
3. How do I avoid Zigbee channel conflicts during a retrofit?
Three things: survey, plan, and test.
Survey first. Before you install a single fixture, use a spectrum analyzer (or a free app like Wi-Fi Analyzer) to map out the 2.4 GHz activity in your space. Note where Wi-Fi routers are, where cordless phones live, where microwaves sit. Take it from someone who skipped this step on a 200-piece order once—you'll regret it. We caught it during commissioning, but the delay cost us a weekend and some bruised pride.
Plan the channel assignment. Once you know the Wi-Fi channels in use, pick a Zigbee channel that's as far away as possible. For example, if your Wi-Fi is on channel 1 and 6, set Zigbee to channel 15 or 20. Most modern IoT platforms (including ABB Ability) let you configure this in the commissioning software. Do it before you pair the devices.
Test in situ. This is the one I didn't do on my first project. After turning everything on, walk the space with a maintenance tablet. Check for offline devices. Test a few key commands (all lights on, scene changes, emergency test). If you see any device that's unresponsive or shows intermittent connectivity, that's a red flag that interference might be an issue.
I've caught 47 potential errors using this checklist in the past 18 months. Not kidding. I keep a printed copy in my tool bag.
4. What's the difference between "IoT platform connect" and just having smart bulbs?
Good question. And honestly, it's one I didn't appreciate until I'd seen both approaches fail in different ways.
Smart bulbs (like those consumer-grade Wi-Fi bulbs) are individual devices with their own brains. They connect directly to your Wi-Fi network. That's fine for a home—you have maybe 20 bulbs. For a commercial building with 500 fixtures, each one broadcasting its own Wi-Fi signal is a recipe for network congestion. Plus, if your Wi-Fi goes down, every bulb goes dumb.
An IoT platform—ABB Ability, for instance—uses a central gateway or controller. The fixtures communicate on their own dedicated network (often Zigbee or Thread). The gateway then interfaces with your building's network. This means:
- The lighting network is isolated from the IT network. No Wi-Fi congestion.
- Firmware updates are managed centrally, not per-bulb.
- The system can be tied into emergency lighting testing, energy monitoring, and analytics.
- If the network goes down, the gateway keeps the last-known state, so lights don't suddenly flip off.
Per ABB's own documentation on ABB Ability, the platform provides a single point of management for all connected devices—lighting, sensors, contactors, and even vibration sensors. That's way more like a building's nervous system than a collection of light bulbs.
5. What is ABB retrofit solutions? And are they actually worth it?
ABB retrofit solutions are basically a way to upgrade an existing lighting system (think old fluorescent or HID fixtures) to modern LED with IoT controls, without ripping out all the wiring. They offer several packages:
- Lighting retrofit kits. Replace the light engine and driver in existing housings. Keeps the physical fixture and wiring.
- Control retrofit modules. Add sensors and connectivity to existing fixtures.
- Emergency lighting retrofit. Upgrade emergency ballasts and batteries to code.
- Lighting contactor replacements. Upgrade old relays to smart contactors for zone control.
Are they worth it? That depends on your context. If you've got a building with good-quality housings and conduit runs, a retrofit is almost always cheaper than a full replacement. We're talking 30-50% less installation labor, plus minimal disruption to occupants.
But here's the nuance: not all fixtures are good candidates. If the existing housing is corroded, dated, or structurally compromised, a retrofit kit is just a band-aid. I've seen a facility manager opt for a full replacement after a partial retrofit failed because the old housing couldn't handle the thermal load of the new driver. That cost more than if they'd torn it all out from the start.
I can only speak to mid-size commercial retrofits. If you're dealing with a heritage building or a hazardous location (like a chemical plant), the calculus might be different. Involve an engineer early.
6. How do I even start planning a smart lighting retrofit?
If you've made it this far, you're probably serious about it. Here's my step-by-step, based on what I've learned (and screwed up along the way):
- Site assessment. Walk the entire space. Note fixture types, wiring conditions, ceiling heights, and any obstructions that might affect wireless signals.
- Network audit. Use a spectrum analyzer to map 2.4 GHz activity. Document Wi-Fi access points, Bluetooth devices, and anything else that lives in that band.
- Define requirements. What do you actually need the lights to do? Dimming? Scheduling? Occupancy-based control? Emergency testing? Be specific.
- Select the platform. Choose your IoT platform early. This dictates everything else—gateways, sensors, commissioning tools. ABB Ability is my go-to, but it's not the only option.
- Plan the commissioning schedule. Commissioning isn't a one-day thing. Expect to spend a few days on site, and budget for a follow-up visit after 30 days to catch any latent issues.
- Train the staff. Spend an afternoon with the facility team showing them the control software, how to change scenes, how to reset a sensor, and who to call if something fails.
Bonus tip: Keep a written record of your Zigbee channel choice and Wi-Fi settings. Trust me. A year from now, when the IT guy changes the Wi-Fi channel and your lights start flickering, you'll thank yourself.
Disclaimer: This content reflects my personal experience managing commercial lighting retrofits. It is not an official ABB publication. For project-specific technical specifications, consult an ABB authorized distributor or electrical engineer.