WLED Devices become unavailable after a couple of days

[AdmiralRaccoon]

The problem

Refering to this issue on WLED Github:
Aircoookie/WLED#4347

What happened?
After a couple of days, the device because unresponsible within Home Assistant as well as pinging it / access to the WebUI. Even pressing the button for toggeling won´t work. I have to remove power to get it working again, and then it will work again for the next 3-5 days.

I will notice when it stops working in the morning, as it supposed to wake me up in the morning.

To Reproduce Bug
Waiting several days

Expected Behavior
Working 24/7

Install Method
Binary from WLED.me

What version of WLED?
WLED 0.15.0-b7

Which microcontroller/board are you seeing the problem on?
ESP32-C3

Anything else?
It´s a WLED Slim LED Strip Controller from Athom:
https://de.athom.tech/blank-1/wled-slim-led-strip-controller

It´s doesn´t get hot
WIFI sleep is disabled
WIFI TX Power is at 8.5 dBm (that was the default)

What version of Home Assistant Core has the issue?

2024.11.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

WLED

Link to integration documentation on our website

https://www.home-assistant.io/integrations/wled/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

This was one of the anwers in the WLED community:

I think this issue more likely is related to an underlying problem with the ESPAsyncWebServer dependency. @AdmiralRaccoon, are you using Home Assistant by any chance? HA can be pretty aggressive in its polling and open many concurrent conenctions to the WLED device, which might lock it up.

See me-no-dev/ESPAsyncWebServer#157 and me-no-dev/ESPAsyncWebServer#1116

This is still easy to reproduce with a synthetic load:

wrk -c 1 -d 20 -t 1 --timeout 5 http://IP/json
Increasing concurrency, -c to e.g 8 will consistently lock up an ESP32-C3 on 0.15. I haven't tested other ESP32 variants recently, but they will likely fail around the same level of concurrency as well.

[home-assistant]

Hey there @frenck, mind taking a look at this issue as it has been labeled with an integration (wled) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of wled can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign wled Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

wled documentation
wled source
_{^{(message by IssueLinks)}}

[u20p17]

i have the same issue with a quinled dig-uno board connected via ethernet cable and home assistant 2024.12.3 + wled v0.15... would be nice if we could find a solution for this soon :)

[perseus177]

Same problem on board ESP8266
Firmware: 0.15.0