Hello - just noticed a small issue on all of the 8266’s I have tried.
I have loaded WLED 14.4 on an 8266 (several actually) and attached a string of 50 pixels.
When powered on, the first 13 LEDS briefly light up as white before the solid amber default kicks in. This is not normally a problem, but if I reduce the configured number of LEDs in WLED to under 13 - like 10, for example - then power on the controller, the first 13 LEDs blink white, and then only the configured 10 LEDs change to amber. The next 3 remain white since the controller isn’t aware of them.
I have tried ESP-12E and ESP-12F 8266’s from different vendors. All seem to exhibit the issue.
I have loaded 13.3, 14.0-4 and 15.0 b4 - all exhibit the same issue. Tried 80MHz and 160MHz - issue seen on both.
My ESP32s, however, seem to run fine with no white blink on power up.
Has anyone else seen this problem?
Here is a link showing what I describe. In the video, I am using a Duo2Go 2-port controller with an 8266 attached, but I have verified that the same issue occurs when you bypass the controller and power eh lights directly from the 8266.
When powered on, you see a brief 13-LED white blink. Then, the first 10 change to amber, leaving 11-13 white.
If I were to reduce the LED count to 1, for example, the reboot. The first 13 flash white. Then only the first pixel goes to amber, leaving 2-13 white.
This happens on BOTH outputs.
I have tested this with several different ESP8266, bought from different vendors.
As I continue to research - I see the same issue here:
Sounds like it is being chalked up to “garbage on GPIOs 2 and 1” (my two outputs) at bootup. Is there any practical way to mitigate? I have a full setup with level shifters in place.
Overall this is not a terribly severe issue - but an annoying one.
It only presents itself as a problem if you are only running less than 13 LEDs, and have extras after that you don’t plan to use and don’t want to cut off.
