Troubleshooting
Remote doesn't respond
5 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.
Batteries and distance
Check the 2 × AAA batteries. The 4336-001 range is up to 50 m according to the manufacturer; walls and metal shorten it.
ESP-NOW enabled in WLED?
Config → WiFi Setup: enable ESP-NOW and set “Disable WiFi sleep”, otherwise button presses don’t arrive. Save; the controller restarts.
Remote registered?
Press a button: the MAC address appears under “Last device seen”. Add it to the list with +. WLED ignores unlisted remotes; up to 10 are possible.
Controller running WLED?
The 4336-001 is meant for the GLEDOPTO WLED controllers. For the 4321-WL4 (MiBoxer) no manufacturer confirms the combination; the MiBoxer 2.4G remote is intended there.
Same Wi-Fi channel?
ESP-NOW uses the controller's Wi-Fi channel. If the router changes channel automatically the link can drop. Set a fixed channel in the router.
Further help
WLED docs: ESP-NOW remotes ↗
Setup, button mapping and limits per the official documentation.
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
- 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