Something not working? Find your symptom below for step-by-step fixes for the most common WLED installation problems.
Still stuck?
The WLED community on Discord and Reddit r/WLED are very active and helpful. Include your LED strip type, controller, PSU specs, and any error messages. Discord / Reddit r/WLED
Most WLED installation problems fall into one of four categories: power issues, signal integrity problems, firmware configuration errors, or network connectivity failures. Working through these categories in order — power first, then signal, then firmware, then network — resolves the vast majority of reported issues without needing to replace any hardware.
This almost always indicates a power supply problem. Either the PSU is undersized for the current draw (check with the Power Calculator), the connection between PSU and strip has high resistance (clean the terminals and check wire gauge), or the PSU is overheating. A PSU running at over 90% of its rated capacity will throttle output, causing voltage sag and flickering. Size your PSU so the load is no more than 80% of the rated output.
This is voltage drop. Voltage at the far end of the strip is low enough that the LED ICs are operating out of spec. Add a power injection point at the far end of the strip — connect positive and ground from the PSU directly to the last injection pad on the strip. Use the Voltage Drop Calculator to find the exact injection spacing your installation needs.
Usually caused by a floating data line — the data wire is picking up noise from the environment, toggling the first few LEDs. Fit a 330Ω–470Ω resistor in series with the data line at the controller GPIO pin. Also ensure there is a shared ground between the controller and the LED strip.
The most common cause is an incorrect LED type selected in WLED's LED Preferences. WS2812B uses GRB colour order; some strips use RGB, RGBW, or GRBW. If your whites appear pink or your reds and greens are swapped, change the colour order in WLED settings. Also confirm your LED strip type (WS2812B, SK6812, APA102, etc.) matches exactly.
Possible causes: the LED count in WLED's settings is too low and the remaining LEDs are not addressed; or the data signal is not reaching beyond the first LEDs due to a broken trace on the strip, a bad solder joint, or a failed driver IC. Test by temporarily setting a higher LED count in WLED. If only 10 LEDs respond regardless of count, the strip has a physical break — locate it by measuring resistance between adjacent LED pads.
Check that your Wi-Fi network is 2.4GHz — ESP32 and ESP8266 do not support 5GHz Wi-Fi. Ensure the password does not contain special characters that might not be handled correctly in the WLED setup wizard (particularly &, ', and quotation marks). If WLED repeatedly fails to connect, reset credentials by holding the WLED button for 6 seconds (or using the factory reset option in the WLED app) and reconnect via the WLED-AP hotspot.
Move the controller closer to the Wi-Fi access point, or install a repeater. Use a static IP address for WLED (in your router's DHCP reservation settings) to eliminate IP lease renewal as a source of disconnections. If using Home Assistant, set up the WLED integration to automatically reconnect when WLED comes back online.
OTA updates require both the controller and your browser to be on the same local network. If the update fails mid-transfer and WLED becomes unresponsive, re-flash via USB using the WLED web installer at install.wled.me. Always keep a USB cable accessible for recovery purposes.
Ensure WLED and Home Assistant are on the same network subnet. Enable WLED's mDNS in Config → WiFi Setup (the hostname allows HA to find it). In Home Assistant, go to Settings → Integrations → Add Integration → WLED and manually enter the WLED IP address if auto-discovery does not work.
Power cycle the controller. If it still does not respond after 30 seconds, check whether the WLED-AP hotspot appears (which indicates the controller is alive but not connecting to Wi-Fi). If no hotspot appears, the firmware may have been corrupted — re-flash via USB. Also check whether your router assigned a new IP address (use a static IP or DHCP reservation to prevent this).