WLED Integration needs Reload after WLED Restart

[VDRainer]

The problem

Since Beta 2024.3.0b5, after Restart of the WLED Device, the device no longer responds in Homeassistant. The WLED Integration needs a Reload to start working again.

I have 2 WLED devices running on esp32, version 0.14.1, both show the same behavior

I found no changes about WLED in the beta release notes, so i think it has to do with the startup optimizations.

What version of Home Assistant Core has the issue?

core-2024.3.0b6

What was the last working version of Home Assistant Core?

What type of installation are you running?

Home Assistant Core

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?

Nothing in the logs about this, just one line at reloading the Integration.
2024-03-05 21:39:06.196 DEBUG (MainThread) [homeassistant.components.wled] Manually updated wled data
2024-03-05 21:39:43.790 DEBUG (MainThread) [homeassistant.components.wled] Finished fetching wled data in 0.297 seconds (success: True)
2024-03-05 21:39:43.886 DEBUG (MainThread) [homeassistant.components.wled] Manually updated wled data

Additional information

No response

[home-assistant[bot]]

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)}}

[botfixer]

Hm, i think it has nothing to do with Beta 2024.3.0b5.

I experienced this since i am using WLED (about 3-4 month).

Today i am on:

Core 2024.2.5 Supervisor 2024.02.1 Operating System 12.0

As a workaround, I am using an automation which restarts the WLED integration every day. I always thought that caused by random wifi interruptions. Now I have tested it and it is like you described. After WLED restart, i need to reload the integration.

I could also imagine that there is another situation that creates the same effect. Because I also observed this without the WLED controller has restarted.

[VDRainer]

Thanks for the comment. You're right, did some further testing and a downgrade to 2024.2 and had the same issue.

I had an automation that restarted WLED in the morning with a shell_command curl -s "http://192.168.2.146/win&RB" -o /dev/null and never had problems with it.

Since b5 and b6 the wled light doesn't work in the morning and i have to reload the integration with another automation. :smile:

Changed the last working version above, but keeping this open.

[VDRainer]

I could also imagine that there is another situation that creates the same effect. Because I also observed this without the WLED controller has restarted.

I just discovered that too. But never had any problems with it before 2024.3

[lundyfpv]

Seeing same issues with WLED, a reload fixes the issue.

HA: 2024.3.0 WLED: 0.14.0

[Gh0st-drive]

Also experiencing this issue, reloading device fixes the issue.

Core - 2024.5.2 Supervisor - 2024.05.1 Operating System - 12.3 Frontend - 20240501.1