Legrand Request Project Review

Legrand Daylight Sensor Won't Work? The 3 Mistakes I Made (So You Don't Have To)

If you're Googling "Legrand daylight sensor" or "Legrand wifi dimmers," you're probably in one of two situations: your new system isn't doing what you expected, or you're planning an install and want to get it right the first time.

I'm an electrical contractor. I've been handling commercial and high-end residential lighting control orders for 7 years. In that time, I've personally made (and documented) 12 significant mistakes during specification and installation, totaling roughly $14,000 in wasted budget and rework. I now maintain our team's pre-install checklist to prevent others from repeating my errors.

This isn't a marketing piece. It's a collection of specific screw-ups I made with Legrand daylight sensors and WiFi dimmers, what I learned, and the questions you should be asking before you even open the box.

1. "Why Isn't My Legrand Daylight Sensor Turning the Lights Off?" (The Oversimplification I Believed)

The short answer: It probably is working. Your expectation of how it works is wrong.

From the outside, it looks like a daylight sensor should act like a light switch triggered by the sun: enough sunlight? Lights off. Not enough? Lights on. Simple, right?

The reality is more nuanced. (I learned this the hard way.)

On my first project using Legrand occupancy/vacancy sensors in 2020, I installed a daylight sensor in a south-facing office. I assumed it would keep the LED fixtures off all afternoon. Instead, they would flicker on and off every 15-20 minutes. I blamed the sensor. Sent it back. Got a replacement. Same problem.

It took a call to Legrand's tech support (and a slightly embarrassed admission that I hadn't read the full spec sheet) to understand: the daylight sensor measures ambient light at the sensor's location, not at the task surface. The light coming through the window was hitting the sensor, but the sensor was also detecting shadows from a tree branch blowing in the wind. The rapid changes in light level triggered the sensor to toggle the lights.

It's tempting to think a daylight sensor is a simple photocell. But commercial-grade sensors like Legrand's use algorithms to average light readings over time to prevent flickering. My problem wasn't a faulty sensor — it was a sensor doing exactly what it was designed to do, just not what I expected.

What I do now: I map the sensor's field of view to the actual window placement. If direct sunlight hits the sensor, I adjust the trim pot or use the app to reduce sensitivity. For offices with variable outdoor shading (trees, adjacent buildings), I use a lower sensitivity setting.

Another thing: People assume you can use a standard light fixture with any sensor. The reality is that LED drivers and dimmers must be compatible. Legrand publishes compatibility lists. I ignored one once. The fixtures buzzed. (Note to self: always check the list first.)

2. "Do Motion Sensor Light Bulbs Exist?" (The Question That Led to a $1,200 Mistake)

Yes, they do. But when a client asked me this in early 2023, I assumed they wanted a simple, integrated solution for a hallway. I didn't ask enough questions.

The client had seen consumer-grade motion sensor light bulbs at a big-box store. They wanted that functionality in a new build. I spec'd individual motion-sensing bulbs for six fixtures. Cost: about $50 each. Seemed straightforward.

On a 6-piece order where every single item had the issue, the problem became immediately obvious after install. The bulbs would sense motion in their own immediate zone. A person walking through a room would trigger the first bulb, then stop triggering it as they moved to the next zone. The first bulb would time out and turn off, leaving the next section dark. It created a "chase" effect instead of uniform lighting. That error cost $300 in replacement bulbs plus a 2-day delay and an unhappy client.

The better solution for that space was a centralized motion sensor connected to standard dimmers — specifically, a Zigbee motion sensor paired with Legrand's connected dimmers. The sensor covers the whole room; the dimmers respond simultaneously. One sensor, six lights, zero chasing.

Lesson learned: Just because a product exists doesn't mean it's the right solution for the application. Motion sensor light bulbs work well for closets and small spaces (bathrooms, pantries). For larger rooms, a centralized approach is better.

I now have a pre-qualification question I ask every client: "Do you want the sensor in every fixture, or one sensor controlling multiple fixtures?" Their answer tells me how much homework I need to do.

3. "I Bought Legrand WiFi Dimmers, But They Won't Connect. What Now?" (The Assumption That Broke My Timeline)

This happened in September 2022. I had a two-week window to wire and commission a new office space. The spec called for Legrand WiFi dimmers throughout. I ordered 20 dimmers, installed them in a day, and started the pairing process.

I assumed the setup would be straightforward: download the app, scan the QR code, connect to the network, done. Had tested one dimmer at the shop. Worked fine.

In the field, with 20 dimmers and a commercial-grade WiFi network (multiple access points, different SSIDs for different bands), I hit a wall. 14 dimmers paired easily. 6 refused to connect. I spent an entire day troubleshooting. Reset dimmers. Restarted router. Moved the phone closer. Nothing.

Turned out the issue was the network's band steering. The network was pushing the dimmers to the 5GHz band at setup (even though they're 2.4GHz devices, Legrand dimmers have a known sensitivity during initial provisioning). The solution? Temporarily disable band steering on the access point nearest to the dimmers, or create a dedicated 2.4GHz IoT network.

I assumed the dimmers would handle a managed network like any other WiFi device. Didn't verify. Turned out the pairing process is more fragile during initial setup than after it's connected.

That day cost me roughly $800 in billable labor that I couldn't charge to the client (it's a network issue, not a dimmer issue) plus a 1-week delay while the IT team made the network change. A 15-minute conversation with the building's IT manager before installation would have saved the entire day.

My fix: I now include a pre-install network questionnaire in my scope of work. Questions include:

  • Is there a dedicated 2.4GHz network?
  • Is band steering enabled on the access points?
  • Can I get a guest or IoT SSID that's locked to 2.4GHz?
  • What is the WiFi password? (Amazing how often this is an issue).

These questions feel basic. But missing one can cost you a day.

4. (Bonus) "My Occupancy Sensor Leaves Me in the Dark." (The Sensitivity Setting I Didn't Know Existed)

This one is quick but worth mentioning.

I had a client complaint about a Legrand occupancy sensor in a bathroom. The sensor would turn the lights off while someone was still in the stall.

I assumed the sensor placement was bad. Moved it. Problem persisted.

Reading the fine print on the spec sheet (I should have done this before): Legrand occupancy sensors have adjustable time delays and sensitivity levels. The default time-out is 15 minutes, but in a small space like a bathroom, the sensor's field of view might not detect subtle movement in a stall.

I adjusted the sensitivity from the medium default to high (using the trim pot on the sensor). Problem solved. A one-minute adjustment that I spent two hours troubleshooting.

In my first year (2017), I made the classic mistake of thinking all sensors work identically. They don't. PIR (passive infrared) sensors detect large motion. Ultrasonic sensors detect fine motion. Some Legrand sensors combine both. Reading the spec sheet isn't optional — it's the difference between a one-hour install and a four-hour troubleshooting session.

The fundamentals haven't changed — a sensor detects motion and triggers a light — but the execution has transformed. What was best practice in 2020 may not apply in 2025.

The Pre-Install Checklist I Use Now

After three rejection scenarios (client rejection of motion-chasing bulbs, network pairing failure, and sensor sensitivity issues), I created this checklist:

  1. Sensor placement: Is the Legrand daylight sensor in direct or dappled sunlight? Adjust sensitivity or plan for an average reading delay.
  2. Wireless network: 2.4GHz? Dedicated SSID? Band steering off? IT team aware?
  3. Sensor type: Occupancy (auto-on/auto-off) or vacancy (manual-on/auto-off)? Client preference confirmed?
  4. Compatibility: Check Legrand's compatibility list for LED driver and dimmer pairing.
  5. Zigbee vs WiFi: If using zigbee motion sensors (like those paired with a hub), check hub placement and mesh network strength.
  6. Time delay: Set the time delay (common: 5-15 minutes) and test in the actual space before signing off.

I've used this checklist on 24 projects in the last 18 months. It's caught 47 potential errors — from mis-spec'd sensors to incompatible WiFi settings — before they became site issues.

Not glamorous. But it works.

Why this matters

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