Troubleshooting
Controller can't be reached on the network
4 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.
2.4 GHz Wi-Fi available?
The controllers only use the 2.4 GHz band. With mesh or band steering, a dedicated 2.4 GHz network name helps.
WLED-AP hotspot visible?
If the controller can't find your Wi-Fi it reopens WLED-AP (password wled1234 unless changed). Then correct the Wi-Fi details at 4.3.2.1.
IP address instead of .local
.local names don't work on every device. The IP is in the router's device list; the WLED app searches automatically.
Signal too weak?
Metal enclosures, aluminium profiles and walls attenuate heavily. Move the controller closer to the router or choose a LAN controller.
Further help
Guide →
Setup step by step: WLED-AP, Wi-Fi, LED settings, presets, Home Assistant.
LED-Emotion: WLED basics (German) ↗
Power supply, consumption, GND, level shifter and installation explained in detail.
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
- 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
- Update failed or controller won’t start
- Home Assistant can’t find WLED
- Schedule switches at the wrong time
- Several controllers aren’t in sync