FAQ

Connection issues

I have entered my WiFi credentials and rebooted, but I can not connect to the module now!

If you did not enter a static IP, the module will automatically obtain a dynamic IP from the router. You can check it in the router configuration or in the settings page, if the Access Point is still enabled.

The module once was connected, but I can no longer reach it.

First, make sure you can reach the connected WiFi yourself (with another device). See if you can connect to the Access Point, then go to 192.168.4.1/reset. Else, power-cycle the module manually.

The led.local address (mDNS) does not work.

This only works with Apple devices out of the box. You can install Bonjour to make it work in Windows. Furthermore, this only works with DHCP and not when you have configured a static IP.

Is it safe to do a port forwarding to the public internet to control the lights from anywhere?

See this page.

LED issues

My LEDs don't turn on at all.

Please make sure you have connected the strip to GPIO2 and it is sufficiently powered.

My LEDs act funny and flicker randomly.

Reason 1

The ESP8266 is a 3.3V microcontroller while the WS2812B LED uses 5V. I have personally got away with this in most cases, but you should technically add a level shifter.

Reason 2

You have an incorrect software version.

• For WS2812B (RGB) use the RGB binary. (if you use the source make sure the first line in WS2812FX.h is commented out)
• For SK2812 (RGBW) use the RGBW binary. (or make sure the first line in WS2812FX.h is NOT a comment)

Reason 3

You use an ESP32. The support is not yet finalized and you may run into issues.

Not all my LEDs turn on.

Reason 1

To prevent over-current, by default the LED count is limited to 10. If you have more and can power them, go to LED settings and increase the LED count! WLED supports up to 1200 individual LEDs right now.

Reason 2

There is currently a strange bug which may cause LED 3 and 4 to be always off. It may be worked around by power-cycling a few times.