I Wasted $3,200 on a Lighting Retrofit — Here’s How Not to (Chandelier Height, Motion Sensors & IoT)

Why I Created a 12‑Point Checklist After My Third Burn

I’ve been handling commercial lighting orders for a bit over six years. In my first year alone I personally made (and documented) three significant mistakes, totaling roughly $3,200 in wasted budget. That’s not counting the timeline delays and embarrassed phone calls to clients. Now I maintain our team’s pre‑project checklist — the one that’s saved us an estimated $8,000 in potential rework over the last 18 months.

The problem is, most buyers jump straight to “what’s your price per fixture?” without realizing the real cost lives in installation, compatibility, and code compliance. There’s no one‑size‑fits‑all answer because your situation — retrofit vs. new build, decorative chandelier vs. functional strip, manual vs. IoT — dictates completely different checks. So let me walk you through the four scenarios I see most often, based on the questions I get from facility managers and business owners.

Scenario A: You’re Planning a Retrofit (ABB Retrofit Solutions)

If you’re swapping out old fluorescent or HID fixtures for LEDs, you’re already on the right track. But here’s the rookie mistake I made: I assumed any LED tube would work with the existing ballast. Turns out, many “direct wire” LEDs require you to bypass the ballast entirely, and if your building has an older emergency lighting system, things get messy fast.

I once quoted a 200‑piece warehouse retrofit with a $7,000 budget. We installed the first 20 fixtures, powered them up, and half the lights flickered. Why? The existing 0‑10V dimming system wasn’t compatible with the LED drivers we picked. Cost to fix: $890 in new drivers plus a 1‑week delay. That’s when I learned to always audit the existing control infrastructure first.

What I do now: Before any ABB retrofit solution order, I run a simple checklist:

• Existing ballast type? (T8 magnetic vs. electronic vs. instant start)
• Dimming system presence? (0‑10V, DALI, or none)
• Emergency backup wiring? (separate circuit or integrated battery)
• Sensor compatibility? (motion, daylight harvesting)

If you’re retrofitting, never assume compatibility. I’d recommend using ABB’s pre‑bundled retrofit packages — they come with matched drivers, sensors, and bypass instructions. It’s the no‑brainer way to avoid a $500+ mistake.

Scenario B: You’re Installing a Chandelier (Especially the Lunaria Chandelier)

Everyone focuses on the style and the finish. The question I always get is: “Can I hang it lower for drama?” Well, that depends on where it’s going. The biggest blind spot I see is safety clearance and light distribution — not just aesthetics.

I had a client who fell in love with the Lunaria chandelier and insisted on hanging it 5 feet above a dining table in a room with an 8‑foot ceiling. The fixture’s bottom was at 5'6” from the floor. Looked great in the catalog. In reality, anyone standing up could bump their head, and the light pool was so narrow the table edges were in shadow. We had to shorten the chain and re‑order longer stems — $350 extra and a 2‑day delay.

Industry standards (per NEC Section 410.10 and general practice):

• Over a dining table: bottom of chandelier 30–36 inches above the tabletop
• In a hallway or foyer: minimum 7 feet clearance from floor (8 feet is safer)
• Over a bathtub: at least 3 feet above the rim (NEC 410.16)

People think “more height = more drama.” Actually, the right height gives you both drama and usability. For the Lunaria chandelier specifically — its diffuser tends to scatter light upward, so mounting it too high kills the ambient effect. I’d say 30–33 inches above the table is the sweet spot. I’m not 100% sure about every room, but in my experience, that’s where you get the best blend of sparkle and illumination.

Scenario C: Your Motion Sensor Light Isn’t Working (How to Fix)

This is the #1 support call we get. Someone installs a nice LED fixture with an integrated motion sensor (or we supply a separate sensor via ABB’s product line), and a week later the light stays on all night or never turns on. The assumption is always “the sensor is defective.” But from the mistakes I’ve documented, about 70% of the time it’s an installation or environment issue.

I remember a $1,200 order for 20 emergency exit lights with motion sensors. The client reported half of them wouldn’t detect movement in the corridor. I flew out (cost me $400 in travel) and found the sensors were pointed directly at heat vents — the false triggers had overridden the detector logic. Relocating the sensor heads solved everything. Total cost of my ignorance: $400 + a weekend.

My quick troubleshooting checklist (before calling support):

1. Power cycle: Turn the breaker off for 30 seconds, then on. This resets the sensor’s initial learning.
2. Check the mode: Many sensors have a test mode (short detection) and a normal mode. Make sure you’re not in test mode.
3. Look for heat sources: HVAC vents, ovens, direct sunlight — can cause false on/off.
4. Verify wiring: Did you connect the neutral? (Some sensors need it even if the fixture doesn’t). Also check that the load wire is the correct one.

If none of these work, the sensor might be faulty. But I’ve found that a simple re‑adjustment of the sensitivity and time‑delay settings fixes 4 out of 5 “broken” sensors. Don’t be like me — don’t skip the user manual’s step‑by‑step.

Scenario D: You Want to Connect Everything with IoT (ABB IoT Connecting)

Smart lighting is a game‑changer for energy savings and maintenance, but it’s not a plug‑and‑play gadget. The biggest mistake I see: people think “smart” means just screw in a connected bulb and download an app. The reality is, a proper IoT lighting system — like the ones we deploy with ABB’s Ability platform — requires a robust network infrastructure, gateway compatibility, and cybersecurity protocols.

People think IoT introduces more points of failure. Actually, the lack of proper planning causes the failures. I once worked on a project where we installed 40 wireless luminaires, but the building’s Wi‑Fi was spotty in the warehouse. The lights kept dropping off the network. The customer blamed the fixtures. We added a dedicated zigbee gateway, and everything worked flawlessly. That mistake cost $2,100 in extra gateway hardware and labor.

My pre‑IoT checklist (inspired by an ABB technical whitepaper):

• Confirm network coverage — use a site survey tool, not assumptions.
• Choose the right protocol — Zigbee, Thread, or Wi‑Fi? (ABB sensors and controllers mostly use Zigbee for reliability.)
• Set up a separate IoT network segment (security first).
• Define user permissions — who can adjust lights, who can set schedules?

If you’re going to connect 50+ devices, spend an hour upfront mapping the network. That hour will save you from a week of debugging later — trust me, I learned the hard way.

How to Know Which Scenario You’re In

Still not sure where to start? Here’s a quick self‑diagnosis:

• Your building is 10+ years old, you want to swap out old fixtures → Start with Scenario A (retrofit check).
• You’re building a new space or installing a showpiece chandelier (like Lunaria) → Go to Scenario B (height and clearance).
• A light with a motion sensor is acting weird (flashing, no response) → Use Scenario C’s checklist first.
• You want automated control across the whole floor or building → Scenario D (IoT infrastructure).

And in every scenario, remember: the 5 minutes you spend verifying now beats 5 days of correction later. That’s the bottom line I learned from $3,200 worth of mistakes.