WLED Update entity becomes unavailable when turning on/off light

[N3rdix]

The problem

I observed a strange behaviour with the update entity of the WLED integration becoming unavailable for a few seconds when toggling the light. The debug log did not give any hint what could go wrong, is this an expected behaviour or even better, can it be avoided (besides updating, but sometimes there might be reasons why delaying an update)?

Logs when turning the lights on:

2024-03-01 13:57:21.195 DEBUG (MainThread) [homeassistant.components.wled] Manually updated wled data
2024-03-01 13:57:22.050 DEBUG (MainThread) [homeassistant.components.wled] Manually updated wled data
2024-03-01 13:57:32.607 DEBUG (MainThread) [homeassistant.components.wled] Finished fetching wled data in 0.418 seconds (success: True)

Then turning the light off again:

2024-03-01 13:57:34.658 DEBUG (MainThread) [homeassistant.components.wled] Manually updated wled data
2024-03-01 13:57:44.586 DEBUG (MainThread) [homeassistant.components.wled] Finished fetching wled data in 0.397 seconds (success: True)

https://github.com/home-assistant/core/assets/70015952/a8ddbbea-318c-4efc-9c2b-22b39d7514a2

What version of Home Assistant Core has the issue?

2024.1.6

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

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

[Raptylos]

Try reverting the WLED Firmware to 0.14.0. Credits to @smarthomeaf Same issue as described in thread https://github.com/home-assistant/core/issues/110235

[N3rdix]

It's not the same behavior, device is still responsive and does not need a power cycle as described in the issue you are referring to.

As I am still on 0.14.0 this is not the solution here...

[Raptylos]

In your video it is stating v0.14.1 edit: maybe it is the availiable version that i saw in your video On that version, I had the same issues with single WLED instances but using scenes with multiple instances made it much worse.

[N3rdix]

No, it's the update entity indicating there IS an update to 0.14.1 available. Exactly the entity which goes unavailable when toggling the light 😃 TLDR; I am still on 0.14.0

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[N3rdix]

Still an issue...

[donoghdb]

I would agree. I have the same issue, every sensor becomes unavailable, then they all come back and the state is incorrect.