Troubleshooting
Home Assistant can’t find WLED
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
Same network? Auto-discovery uses mDNS and doesn’t work across VLAN or guest network boundaries. Then add the integration manually with the IP address.
Same network?
Auto-discovery uses mDNS and doesn’t work across VLAN or guest network boundaries. Then add the integration manually with the IP address.
WLED version current?
The Home Assistant integration needs WLED 0.14 or newer. The version is shown under Info.
Fixed IP address?
If the IP changes, Home Assistant loses the connection. Assign a fixed address for the controller in the router.
Safety
Disconnect the PSU from mains before working on cables. Work on the 230 V side only by a qualified electrician.
Further help
Home Assistant: WLED integration ↗
Official description of the integration.
Guide →
Setup step by step: WLED-AP, Wi-Fi, LED settings, presets, Home Assistant.
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
- Update failed or controller won’t start
- Schedule switches at the wrong time
- Several controllers aren’t in sync