Troubleshooting
Update failed or controller won’t start
3 checks, sorted by how often they are the cause. For all WLED controllers with ESP32.
Check in this order: the most common and simplest cause comes first. Usually the cause is found after two or three steps.
Most common cause
Right firmware file? The file must match the chip (ESP32, ESP32-C3, ESP32-S3 …). LAN controllers have Ethernet variants. If in doubt, ask the dealer.
Right firmware file?
The file must match the chip (ESP32, ESP32-C3, ESP32-S3 …). LAN controllers have Ethernet variants. If in doubt, ask the dealer.
WLED-AP visible?
If WLED starts but can’t find the Wi-Fi, it opens the WLED-AP hotspot (password wled1234). Set up again at 4.3.2.1.
Reflash via USB
With the web installer install.wled.me WLED can be reinstalled via USB cable in Chrome or Edge. Back up the configuration first if still possible.
Safety
Disconnect the PSU from mains before working on cables. Work on the 230 V side only by a qualified electrician.
Further help
WLED web installer ↗
Install WLED via USB cable in Chrome or Edge.
LED-Emotion: WLED basics (German) ↗
Power supply, consumption, GND, level shifter and installation explained in detail.
For business
Not solved? LED-Emotion’s WLED support (typically 30 minutes via remote or phone) usually finds the cause right away: request support · +49 5132 8305530.
Other problems
- Nothing lights up at all
- Flickering, glitter or random colours
- Colours are wrong (red is green …)
- Reddish, yellowish or dimmer towards the end
- Controller can't be reached on the network
- Too dim even at full brightness
- Glows or flashes when switched off
- Controller keeps rebooting
- Doesn't react to music
- Remote doesn't respond
- Lights up only up to a certain point
- Second output or zone stays dark
- Effects stutter or run slowly
- Strip, PSU or controller gets hot
- White looks bluish, pink or uneven
- Settings or presets are gone
- Home Assistant can’t find WLED
- Schedule switches at the wrong time
- Several controllers aren’t in sync