Troubleshooting
Second output or zone stays dark
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.
Second output added?
Config → LED Preferences: each output needs its own entry with its own GPIO, start LED and length. Add another output with +.
Right GPIO?
The pins are in the controller’s datasheet, e.g. 4321-WL4: data GPIO 4, 16, 18, 19. A swapped pin leaves the zone dark.
Start LED overlapping?
Output 2 starts where output 1 ends (start = length of output 1). Overlaps lead to duplicated or missing pixels.
Segment switched on?
In the segments area of the UI, check that a segment exists for the second zone and is switched on.
Further help
LED-Emotion: “LED Preferences” menu (German) ↗
Every setting in WLED’s LED menu step by step.
Controller comparison →
Outputs, relays, microphone, LAN and datasheets of all controllers.
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
- 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