After troubleshooting hundreds of smart lighting installations, a pattern emerges: users blame Zigbee, WiFi, or the gateway when their smart lights go offline. They buy repeaters, swap gateways, even rip out perfectly good Zigbee bulbs for WiFi-direct alternatives — and the problem persists.
The real culprit is often the LED driver — the power supply hidden inside every smart light.
The Two "Brains" of a Smart Light
Every smart light contains two critical subsystems:
- Communication module (Zigbee/WiFi/BLE chip) — receives commands from the network
- LED driver — converts 220V/110V AC to constant-current DC for the LED beads
The communication module typically draws just 3.3V at tens of milliamps. Where does this power come from? The driver's auxiliary winding.
If the driver's output is unstable — due to excessive ripple — the Zigbee chip experiences intermittent brownouts. The light still illuminates, but the module "disappears" from the network. The app shows "offline." A power cycle brings it back, only for it to drop again hours later.
This is not a network issue. It's a power quality issue.
Three Failure Modes, Three Root Causes
Type 1: Light Works, App Shows "Offline" → Ripple Interference
Symptom: The light is physically on, but the app shows disconnected. Rebooting fixes it temporarily.
Root cause: Non-isolated drivers with insufficient output filtering. When grid voltage fluctuates, the DC output ripple exceeds what the communication module's voltage regulator can handle.
Diagnosis: Other Zigbee sensors/switches on the same gateway work flawlessly. Only specific lights drop out.
Solution: Switch to isolated drivers. The galvanic isolation provided by the transformer reduces common-mode ripple by an order of magnitude.
Type 2: Flickering/Dropouts at Low Dimming → PWM Oscillation
Symptom: Light flickers or disconnects below 10% brightness. Stable at higher levels.
Root cause: Cheap drivers claiming "0-100% dimming" lose current regulation at low PWM duty cycles. Poor loop compensation causes low-frequency oscillation.
Diagnosis: Use your phone's slow-motion camera. If you see pulsing at low brightness, the driver's PWM resolution is too low.
Solution: Select drivers with ≥12-bit PWM resolution (4096 levels). At 1% brightness, this provides 40 discrete steps.
Type 3: All Devices Drop When a High-Power Light Turns On → EMI Radiation
Symptom: When you turn on a high-wattage ceiling light, nearby sensors, locks, and other Zigbee devices all go offline simultaneously.
Root cause: Substandard drivers skip EMI filtering. The switching noise conducts through the power line and radiates in the 2.4GHz band.
Diagnosis: Reproducible every time the specific light switches on.
Solution: Only use drivers with EMC certification (EN 55015 / GB/T 17743). If the product page mentions CCC but not EMC, they likely skipped full testing.
The 2026 Driver Selection Checklist
| Parameter | Requirement | Why It Matters |
|---|---|---|
| Topology | Isolated | Stable under grid voltage variation |
| Output Ripple | ≤ ±5% | Prevents communication module brownout |
| PWM Resolution | ≥ 12-bit (4096 levels) | Smooth dimming, no oscillation at 1% |
| Certification | EMC (EN 55015) | No interference with other smart devices |
The Bottom Line
Before you replace your gateway, add a repeater, or blame your Zigbee network — check the LED driver inside your lights.
Is it isolated or non-isolated? What's the ripple specification? Does it maintain stable output at 1% dimming?
Answer these three questions and you'll solve 90% of "network problems" that were never network problems at all.
Stable smart lighting starts with a quality driver power supply.
NEXLAMP — Smart Lighting Driver Power Supply Specialist | www.nexlamp.com
Top comments (0)