Closed fpfuetsch closed 2 years ago
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!
(message by CodeOwnersMention)
wled documentation wled source (message by IssueLinks)
I just checked my Pi-Hole installation (local DNS ad blocker) and saw that during the last 24 hours the DNS name of the WLED controller got resolved more than 200k times 💥. The DNS request must originate from home assistant which also would explain why the controller breaks after connecting it to Home Assistant -- it just gets spammed with requests.
Interestingly the requests continued after I "deleted" the WLED integration in Home Assistant and I saw something like "couldn't unload WLED integration" in the logs (unfortunately flushed the HA logs afterwards).
Seems like the problem got resolved by restarting home assistant. Will reopen an issue if it occurs again.
The problem
I am running WLED version 0.13.1 on an ESP32. As soon I set up the WLED integration in Home Assistant the WLED frontend breaks after a few minutes and is no longer available. After resetting the controller the frontend is up again for some seconds but the breaks again (only flashing it resolves the problem).
If I do not use the integration, WLED works perfectly fine.
What version of Home Assistant Core has the issue?
core-2022.3.5
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Container
Integration causing the issue
wled
Link to integration documentation on our website
https://www.home-assistant.io/integrations/wled/
Diagnostics information
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
I already tried to investigate if there are any useful logs on the controller's side using debug logging but weren't successful. There are no hints in the controller's logs about the breaking behaviour. Even if the frontend is no longer available the controller stays connected to the WiFi and keeps printing the default debug logs as if it was perfectly fine.