WLED 0.15 loses current sensor

[IGNWoudenberg]

The problem

Running several ESP’s (esp32, esp8266) with WLED firmware 0.14.4. Updated a few to 0.15 and discovered that the current sensor is not available anymore.

What version of Home Assistant Core has the issue?

2024.12.5

What was the last working version of Home Assistant Core?

2024.12.5

What type of installation are you running?

Home Assistant Supervised

Integration causing the issue

WLED

Link to integration documentation on our website

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

Diagnostics information

This entity is no longer being provided by the wled integration. If the entity is no longer in use, delete it in settings.

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

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

[sasukebinbin]

I'm having the same issue. Actually estimated_current and max_current will be unavailable when loading the component if light is off. If light is on, this two sensors will load but it will become unavailable again after the light turned off.

[bramstroker]

Looks like an upstream issue.
wled/WLED#4383

This will also hit users of my custom integration Powercalc, where I also rely on this information.

[kbickar]

The issue wled/WLED#4383 is unrelated to it not reporting in HA. Not sure if it's with the integration not compatible with the new WLED version or just WLED doesn't report it

[bramstroker]

The issue Aircoookie/WLED#4383 is unrelated to it not reporting in HA. Not sure if it's with the integration not compatible with the new WLED version or just WLED doesn't report it

What made you sure it's unrelated? I assume WLED integration is taking data from WLED API, and the issue report mentions no calculated current is reported anymore when the device is off, and it was before.
So I would say this is definitely related to the value not being reported to HA anymore. But did not deep dive yet.

[kbickar]

That issue was about no current reported when the device is off. There's no current reported in HA whether the device is on or off now.

The solution for the issue linked also doesn't fix HA

[bramstroker]

That issue was about no current reported when the device is off. There's no current reported in HA whether the device is on or off now.

The solution for the issue linked also doesn't fix HA

Clear. Thanks for elaborating.

[rwoelk]

I can confirm that reloading the WLED integration when the 0.15 WLED light is on shows estimated current draw. So the issues is only when the light is off.
I can also confirm that updating to WLED version 0.16-alpha as of 20250116 fixes the issue for me. The nightly build is here. https://github.com/Aircoookie/WLED/releases/tag/nightly

[IGNWoudenberg]

That is strange did not update anything and the values are displayed again?

[rwoelk]

Yes, without updating the WLED, and leaving it on. If I reload the integration it will work, until the LED turns off. I've now updated all mine to the nightly build.

[issue-triage-workflows]

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.