ESP8266: network problems

[1rfsNet]

What happened?

I tried to install WLED on a new ESP8266. This worked, but I have massive problems with the network connection, as you can see in the following ping. There is no way to access the web interface.
I tried it with versions 0.15.0, 0.14.4, 0.14.3, 0.14.2 and 0.14.1, and the error pattern is identical everywhere. There is no problem with version 0.14.0. Everything works normally there. I was able to reproduce the problem with five other ESP8266s. Its always the same.
Another router was tested with the same result. The WLED-AP keeps opening and closing. But I can't open the web interface.

To Reproduce Bug

Installation via install.wled.me and manually flashed. Result is identical.

Expected Behavior

I would expect the network connection to work. Since the ESP works fine with version 0.14.0, I can rule out problems with the ESP and the network.

Install Method

Binary from WLED.me

What version of WLED?

WLED 0.14.1 and higher

Which microcontroller/board are you seeing the problem on?

ESP8266

Relevant log/trace output

Reply from 192.168.178.180: bytes=32 time=161ms TTL=255
Request timed out.
Reply from 192.168.178.180: bytes=32 time=138ms TTL=255
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.178.15: Destination host unreachable.
Reply from 192.168.178.15: Destination host unreachable.
Reply from 192.168.178.15: Destination host unreachable.
Reply from 192.168.178.15: Destination host unreachable.
Reply from 192.168.178.15: Destination host unreachable.
Reply from 192.168.178.15: Destination host unreachable.
Reply from 192.168.178.15: Destination host unreachable.
Reply from 192.168.178.15: Destination host unreachable.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.178.180: bytes=32 time=166ms TTL=255
Request timed out.
Reply from 192.168.178.180: bytes=32 time=143ms TTL=255
Reply from 192.168.178.180: bytes=32 time=187ms TTL=255
Reply from 192.168.178.180: bytes=32 time=426ms TTL=255
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.178.180: bytes=32 time=1252ms TTL=255
Reply from 192.168.178.180: bytes=32 time=7ms TTL=255
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.178.180: bytes=32 time=49ms TTL=255
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.178.180: bytes=32 time=195ms TTL=255
Request timed out.
Reply from 192.168.178.180: bytes=32 time=169ms TTL=255
Reply from 192.168.178.180: bytes=32 time=136ms TTL=255
Reply from 192.168.178.180: bytes=32 time=241ms TTL=255
Reply from 192.168.178.180: bytes=32 time=140ms TTL=255
Request timed out.
Reply from 192.168.178.180: bytes=32 time=292ms TTL=255
Request timed out.
Reply from 192.168.178.180: bytes=32 time=263ms TTL=255
Request timed out.

Anything else?

I have a lot of existing WLED instances on ESP8266 with versions 0.14.4 and 0.15.0. It seems to me that the problem only occurs with new installations.

Code of Conduct

• I agree to follow this project's Code of Conduct

[DedeHai]

so if all works on many of your devices, what makes you think this is a bug?
more likely bad hardware (which there is a lot of out there)

[netmindz]

I think you misread the report @DedeHai

It's only with the later releases he sees issues

Can you try the _compat build please @1rfsNet

[DedeHai]

I did ineed misread, I understood some devices to work.
chances are high that its a hardware issue though. @1rfsNet did you try with an added large capacitor on the 3.3V rail?

[blazoncek]

Possible duplicate of: #3764, #3690, #2932

[1rfsNet]

I have also noticed the following. I can easily update an existing ESP with WLED via install.wled.me (I had updated all the others via HomeAssistant). But if I completely erase an existing ESP and reinstall WLED, then exactly the same problem happens again. So it seems to only affect new installations. I think that this can also be used to rule out any kind of hardware defect.

@netmindz Where do I find this "_compat build"?
@DedeHai The ESP is connected to on my computer with USB. That shouldn't be a problem?!

[DedeHai]

The ESP is connected to on my computer with USB. That shouldn't be a problem?!

source does not matter, if there is not enough capacitance, wifi will not work right. and most boards do not have enough for the high demand WLED puts on the chip.

[1rfsNet]

The ESP is connected to on my computer with USB. That shouldn't be a problem?!

source does not matter, if there is not enough capacitance, wifi will not work right. and most boards do not have enough for the high demand WLED puts on the chip.

But that doesn't make sense. Why do I have 10 ESP8266 with 0.15.0 and 0.14.4 that were set up a long time ago and work fine, and new ones don't work, even though the ESPs are from the same batch? Sure, one may be broken, but not 5 pieces. Especially if it worked before, I erase the ESP and then reinstall it, then it no longer works. I can't explain it to myself.

[DedeHai]

install using the web installer?

[1rfsNet]

install using the web installer?

yes mostly but also tried one to flash manually.

[DedeHai]

try the hardware fix and report back.

[Barabba11]

Hi mates, before opening an issue I would be aware if there is already this bug opened, since on the forum somebody reported me the solution and wrote it's known, but I can't find it around here. Please tell me,

0.15.0 on ESP8266 wake up from st-by after 2-3 minutes if SNTP client is active, if I uncheck it it keeps turned off as desidered.
I hope you will fix it in next release

[DedeHai]

@Barabba11 you can open a new issue, but describe in detail how to reproduce because I just tried that and it does not happen on my board.

[1rfsNet]

0.15.0 on ESP8266 wake up from st-by after 2-3 minutes if SNTP client is active, if I uncheck it it keeps turned off as desidered. I hope you will fix it in next release

This is not the same issue. I waited hours and nothing changes.

@Barabba11 you can open a new issue, but describe in detail how to reproduce because I just tried that and it does not happen on my board.

I don't know what else to write, after all, I didn't do much more than use the WebInstaller (as usual). And that with several different ESP8266s.

[Barabba11]

I've made some tests, zthe LED turn on even if NTP is unselected, and it start witha reboot (the boot preset is chosen). Activate NTP just reduces the time on the next turn on/reboot, it can be only one minute if selected and offset time is set high. In my opinion the but is on the offline part of the program, somehow a mistake happens and it reboots.
I also noticed that if I unselect the scedules (I've never touched/set them) on the next reboot they are selected again, why?
I would add, chosing the time zone between CEEST and EEST is complicated and has no sense in my opinion, I don't know what they are and I can't find my time zone which is GMT+3h, so I leave GMT and I add 10800seconds, but it' not that smart. Why don't you indicate here just offset hours instead of those labels?
Thank you

[Benoit221]

Hello,

I have the same problem. And effectively on the same board if i "update" to 0.14.0 from 0.15.0. Ping and wen are working.
I'm using an ESP8266 NodeMCU v3 from aliexpress (esp12e).

Best regards,
B LORAND

[Benoit221]

Another important thing. Version 0.15.0 was perfectly working in ap mode. But not after i connect it to my ap. After i update to 0.14.0, settings are always present and wifi was working on my AP. I don't try to update to 0.15.0 via ota for now.

Best regards,
B LORAND

[Barabba11]

Hi mate, my issue was solved flashing again by https://install.wled.me/ I strongly recomend you do it before loosing time finding a solution for your issues.
I've also recomend staff to notify with evidence to all users to flash web, on the download page. Chances are many users are not aware about that

[Benoit221]

It's what i used.B LORAND -------- Message d'origine --------De : Barabba11 ***@***.***> Date : 10/02/2025 09:25 (GMT+01:00) À : wled-dev/WLED ***@***.***> Cc : Benoit LORAND ***@***.***>, Comment ***@***.***> Objet : Re: [wled-dev/WLED] ESP8266: network problems (Issue #4521) Hi mate, my issue was solved flashing again by https://install.wled.me/ I strongly recomend you do it before loosing time finding a solution for your issues. I've also recomend staff to notify with evidence to all users to flash web, on the download page. Chances are many users are not aware about that —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***> [ { ***@***.***": "http://schema.org", ***@***.***": "EmailMessage", "potentialAction": { ***@***.***": "ViewAction", "target": "#4521 (comment)", "url": "#4521 (comment)", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { ***@***.***": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

[splitbrain]

For what it's worth, I am having the same issue on a NodeMCU ESP8266. Downgrading to 14.0 makes the device work flawlessly again.