Legrand Connecting IoT: Three Setups for Smart Lighting, What Lux Setting Means, and How to Choose

If you've ever stood in front of a wall of Legrand switches and wondered why there are three different ways to make the same light turn on, you know the feeling. The short answer is: there isn't one right answer. The longer answer depends on whether you want a simple local switch, a connected system with an app, or direct control from your own home automation hub.

I coordinate lighting control retrofits. Mostly commercial, occasionally residential. In March 2024, I had to swap out an entire corridor of occupancy sensors 48 hours before a tenant move-in because the original spec used a proprietary hub with no backup plan. That's the kind of call that makes me think in total cost, not just unit price.

When someone asks about “Legrand connecting IoT,” they're usually looking at one of these three setups:

1. Standalone controls: A Legrand switch, dimmer, and/or occupancy sensor operating on their own. No hub, no cloud, no phone app.
2. Legrand IoT Connect: A bridge/gateway that connects the devices to a phone app and cloud services, with Zigbee as the wireless transport.
3. Home Assistant Zigbee: You use a Zigbee coordinator and pair Legrand devices directly to Home Assistant, interpreting the Zigbee clusters in software.

These aren't product lines as much as routes. Sometimes the same hardware works in more than one route. Sometimes it doesn't. That's where people get into trouble.

Scenario 1: You Don't Want Another App

If you just need a wall switch that works, a sensor that turns lights off when nobody's in the room, or a dimmer that doesn't require a training course, start with standalone controls. This is the route for hallways, bathrooms, storage areas, and any room where “phone control” is a nice-to-have, not a need.

A standalone Legrand occupancy sensor is not exciting. That's the point. It sits there, detects motion, and follows the lux setting you configured. If you set the lux threshold correctly, it doesn't turn the lights on during the day. If you set it wrong, you get a call from a facilities manager asking why the lights never turn off.

But here's the catch: if you buy standalone because it's cheaper, and then later decide you want scheduling or remote access, you'll be buying again. I had a client who asked me to install 20 vacancy sensors. Two months later, they asked why the lights couldn't be scheduled for a weekend event. We had to add a bridge and re-pair every sensor. The total cost was higher than if we had bought connected versions from day one.

Scenario 2: You Want the Legrand IoT Connect Ecosystem

This is where “Legrand IoT Connect” actually shows up in a spec. A bridge or gateway uses Zigbee to talk to the switches and sensors, then connects to the app and cloud. You get phone control, scheduling, and sometimes energy monitoring.

When this route works well, it's great: no extra wiring, no complicated router setup, and the physical switches still work if the internet goes down. The app might not respond when you're away from home, but the lights in the building still function. That is a big deal for total cost thinking—the failure mode is annoying but not a safety issue.

The part people forget is that a central bridge is a single point of failure for automation. Firmware updates can change behavior. Device pairing can be slower than expected. If you're doing a rush install, set aside a full day for pairing and field tests. Trust me on this one.

I went back and forth between this option and direct Zigbee for a client last year. On paper, the bridge made sense: easier for their facilities team, better documented, fewer moving parts. But the client's IT policy didn't want any cloud dependency on the building network. My gut said the bridge would get rejected in procurement. We went with direct Zigbee instead. The lesson wasn't that one is better—it's that the right route depends on constraints you might not see on the spec sheet.

Scenario 3: You're Running Home Assistant and You Live in the Zigbee Cluster Library

If you already run Home Assistant and you're okay debugging YAML at 11pm, the Home Assistant Zigbee route—often spelled homeassistant zigbee in forum threads—is legitimate. But let's be honest about what it is: you're trading money for your own time. There is no cloud subscription, but there is also no support line.

This is where “zigbee cluster” becomes a practical term. Think of a cluster as a data contract between the physical device and the hub. An on/off switch exposes the On/Off cluster (0x0006). A dimmer adds the Level Control cluster (0x0008). A motion or occupancy sensor exposes the Occupancy Sensing cluster (0x0101), with attributes like occupancy, PIR configuration, and sometimes measured lux.

Home Assistant talks to those clusters through ZHA or Zigbee2MQTT. In theory, that's clean. In practice, not every Legrand device exposes every cluster in the same way. The basic on/off and dimming functions tend to work after pairing. But advanced settings, like a lux threshold, might be in a manufacturer-specific cluster that only the official app or a more recent driver can write to.

I want to say most Legrand Zigbee devices will pair with ZHA or Zigbee2MQTT, but don't quote me on exact model support. The hardware changes faster than the docs. If you're buying a sensor specifically for Home Assistant, check the device support list before you buy, not after.

Here's my own mistake: I knew I should check the device support list, but the box said Zigbee 3.0 and I thought, what are the odds? That was the one time the odds caught up. The sensor joined the network but never updated its occupancy attribute in Home Assistant. I spent almost a full day trying to figure out why a brand new sensor was “working” but not communicating.

How Do You Know Which Route You're In?

There's no master configuration that fits every project. But you can answer these four questions in five minutes:

1. Do you need access from your phone when you're off-site? If no, standalone is enough. If yes, go to the next question.
2. Are you already comfortable with Home Assistant? If yes, direct Zigbee is worth testing. If no, buy the bridge and avoid the rabbit hole.
3. Can your building tolerate a cloud dependency? If no, avoid the bridge and use direct Zigbee, or use no automation at all.
4. Who will support this after installation? If it's not you, choose the route your electrician or facilities team already knows. The cheapest option is the one that doesn't require a specialist to troubleshoot.

That last question is the one that saves the most money.

The Part That Changes Your Total Cost: The Bridge Decision

A standalone switch might cost less than a connected one. But if you later add a bridge, you're paying for the bridge, the labor to re-pair devices, and the time you didn't spend thinking about it before. That's the classic total cost trap.

One project I remember involved a client who saved about $35 per lighting point by buying the basic dimmer instead of the Zigbee version. After construction, conference rooms needed preset scenes. The quote on paper looked cheaper by maybe $400, but the actual change cost much more because the dimmers had to be removed and replaced. I don't remember the exact total, and I'm not going to invent a number. I just remember the project manager saying, “we should have just done it right the first time.”

That doesn't mean you should always buy the connected version. If a building has no need for scenes or remote control, the standalone product is the right total-cost answer. The point is to calculate the cost of the path you're on, not just the unit price.

What Is the Lux Setting on a Motion Sensor?

If you see “Lux” on a Legrand motion sensor, a datasheet, or in the app, it's an ambient light threshold. The sensor measures the light in the room and compares it to that value.

If the room's ambient light is above the lux setting, the sensor still detects presence, but it does not switch the lights on. If the ambient light is below the lux setting, motion will turn the lights on.

It is not motion sensitivity. It is not a delay timer. It's a way to keep lights from running in a bright room.

So what should you set it to? It depends on the space. In a daylit hallway, a threshold around 100–150 lux will keep the lights off during the day and let them turn on after sunset. In a dark stairwell, a lower threshold is fine. If you're not sure, start with the middle of the adjustable range and test it a few times. The bigger mistake is leaving the sensor in test mode and forgetting that test mode often ignores the lux threshold. That's why the sensor seems to turn on in bright daylight.

If you're controlling the sensor through Home Assistant, the lux value may appear as an attribute in the occupancy sensor entity, or it may be exposed through the Zigbee cluster. If it doesn't show up at all, check whether the app or a firmware update exposes it separately. Sometimes you need the app to set the lux threshold once, and then the Zigbee device will remember it.

Bottom Line

There is no universal setup. Start by deciding whether you want a local-only switch, a managed connected system, or direct Zigbee integration. Then calculate the total cost, not the per-unit price. And if you see a lux setting on a motion sensor, set it before you test the sensor—otherwise you'll spend an afternoon standing in the dark thinking the sensor is broken.

It's okay to be your own support team. It's also okay to buy the bridge and skip the rabbit hole. The only wrong answer is choosing a route because someone else's project worked out that way—without checking whether your hardware, your installer, and your timeline can handle it.

For Zigbee cluster details, the Connectivity Standards Alliance publishes the Zigbee Cluster Library specification. For specific Legrand device behavior, check the model's user guide or support page before assuming a manufacturer-specific cluster is exposed to Home Assistant.