It's Not About the Switch Brand
Honestly? I've been in quality control long enough to know that the brand on your light switch—Legrand, Lutron, Leviton—is often the least important part of a smart lighting system. It's the stuff behind the wall that bites you.
I'm a quality and compliance manager for a mid-sized electrical component distributor. I review roughly 200+ unique SKUs per year before they reach our customers. In Q1 2024 alone, I rejected 12% of first deliveries due to spec mismatches—things like incompatible dimming protocols or undocumented standby power draws that would have (frankly) fried someone's Zigbee network. So when someone asks about smart lighting, I don't start with the aesthetic. I start with the interoperability.
There is no single 'best' smart lighting setup. Your choice depends entirely on three things: whether you're retrofitting or building new, how tech-savvy your users are, and whether you need rock-solid local control or you're okay with cloud dependency. Let me walk through the scenarios.
Scenario A: The Retrofit with Existing Legrand Hardware
This is the most common call I get. Someone has a house or office with Legrand switches (usually their Radiant or Adorne line). They want smart dimming. They assume they need to replace the entire wall plate.
You probably don't.
Legrand's standard dimmer switches (like the RH703PT) are actually quite good for forward-phase dimming with LED loads. But here's the blind spot most buyers miss: your switch is just a manual interface. If you want automation—scheduling, motion detection, voice control—the switch itself is irrelevant. You need a Zigbee controller upstream of it, or a smart relay behind it. We've deployed the Legrange RH703PT alongside a Sonoff ZBMINI-L2 Zigbee relay for exactly this purpose. The wall switch stays. The smarts hide behind it.
Most buyers focus on the wall plate aesthetic and completely miss that the controller's maximum load rating (often 100W for LED in a ZBMINI-L2) dictates the total luminaire wattage they can control. The switch is just a button.
Cost impact? The Legrand dimmer alone is about $35-50 retail. Adding a $15 Zigbee relay gives you full app and sensor control. Replacing with a 'smart switch' from another brand costs $50-80 plus ripping out your existing wall plates. Net savings: $20-30 per switch location, and you keep your Legrand aesthetic.
What actually fails in this scenario:
I rejected a batch of 200 units in late 2023 where a Legrand dimmer was paired with an off-brand Zigbee controller. The controller was rated for 200W resistive load (incandescent) but only 80W inductive (LED). The customer wired 12 LED downlights at 7W each—84W total. The controller ran hot, tripped thermal protection after 15 minutes, and the lights started flickering. The vendor claimed 'works fine in testing.' They'd tested with a single bulb. Always test at full rated load.
Scenario B: Greenfield Installation—Designing Control Logic from Scratch
If you're building fresh, you get to think about control logic before you buy anything. This is where the helligkeitssensor Zigbee (light intensity sensor) becomes your most underappreciated tool.
The question everyone asks is: 'which Zigbee hub?' The question they should ask is: 'what triggers my lights?'
In a conference room we commissioned last year, we used a SAMPO Zigbee ceiling-mounted light sensor ($38) paired with a Philips Hue Hub (daisy-chained to a Conbee II stick for broader Zigbee 3.0 compatibility). The logic: if ambient light exceeds 500 lux AND no motion detected for 10 minutes, the system dims lights to 20%. If motion is detected and light is below 300 lux, it jumps to 80% output. The Legrand dimmer switch on the wall then acts as a manual override—pull the slider up to temporarily bypass the sensor for 1 hour.
Saved an estimated $4,200 on HVAC load by reducing lighting heat output in that room—in a room that was only rarely fully occupied. The client's facilities manager told me the light sensor 'paid for itself in six months.' (Note to self: ask for that in writing next time.)
Sensor placement catches everyone out:
The sensor's field of view matters. A ceiling-mounted helligkeitssensor zigbee placed directly above a window will read high daylight levels and keep lights dimmed—even if the corner desk behind the pillar is in deep shadow. We now spec two sensors per room if it's over 200 sq ft or has irregular architecture. The cost difference ($38 per sensor) is trivial compared to a room that's permanently half-dark.
Scenario C: The 'Nunchuck' Question—Motion Sensing That Isn't Just Motion
Let me address the question in your keywords directly: does the Wii Nunchuck have a motion sensor? Yes, it does. The Nunchuck contains a 3-axis accelerometer (STMicroelectronics LIS3L02AL, if you're curious). But here's why this matters for lighting: the principle of a cheap, simple motion sensor vs. a sophisticated occupancy sensor.
In the consumer space, people search for 'Zigbee controllers' and think any motion sensor will do. The Wii Nunchuck is a great example of a high-frequency, low-context sensor. It detects acceleration instantly—great for a game controller. Terrible for a light switch. It has no concept of 'ambient light' or 'is this motion meaningful (walking through a room) vs. meaningless (a plant swaying in an HVAC draft)?'
This is the oversimplification trap. It's tempting to think: 'any motion sensor + any Zigbee controller = smart lighting.' But pairing a basic PIR motion sensor (which detects broad motion, has a 2-3 second delay, and can't differentiate between a person and a pet) with a Zigbee controller will give you lights that either flash on-and-off constantly or stay on for 30 minutes after the room empties. Neither is good.
The 'buy the cheapest motion sensor' advice ignores the dwell time setting on the controller side. Most basic Zigbee controllers have a minimum dwell of 60 seconds. Pair that with a PIR sensor that has a 10-second timeout? Your lights will never turn off until the controller's timeout fires—which is 60 seconds after the last detection, not 10.
Nunchuck-as-light-controller (yes, someone did it):
A client once asked if they could wire a Wii Nunchuck to an ESP32 running Zigbee2MQTT to act as a gesture-controlled dimmer. They could. It worked. But the accelerometer output was noisy—random fluctuations of 0.05G caused the lights to dim and brighten imperceptibly, which over 30 minutes created a 'sick building' effect where occupants felt unsettled but couldn't pinpoint why. We had to implement a 0.3G deadband in the software. Firmware update fixed it. But the lesson: sensor sensitivity matters more than sensor presence.
How Do You Know Which Scenario You're In?
Here's a quick gut-check framework I use when I walk into a new project:
- Are your walls staying? If you're not re-drywalling, you're a Retrofit (Scenario A). Stop worrying about switch brands. Start looking at relay form factors.
- Are you specifying daylight harvesting? If yes, you're in Greenfield (Scenario B). Budget for at least one helligkeitssensor per 200 sq ft. Don't cheap out.
- Are you tempted to hack something together with repurposed game controllers? You're Scenario C. It's fun, it works, but budget at least 40 hours of firmware tuning to make it not drive people crazy.
Skipped the final sanity check on a 'budget' Zigbee controller last month because we were rushing (it was basically the same chipset as the approved one, right?). Wrong. The budget unit had a 2.5-second relay engagement delay—lights turned on 2.5 seconds after the sensor triggered. That's an eternity in a stairwell. $800 rework to swap out 34 controllers. The $18-per-controller 'savings' turned into a $23.50-per-controller loss.
So: buy Legrand for the wall (they make great switches). Buy your Zigbee controllers based on the relay type and minimum load specs. Buy your sensors based on the application context, not just the interface. And if you ask me whether the Wii Nunchuck has a motion sensor—yes. But don't use it for your office lighting.