-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Estimated Current Isn't Reported When Off Since 0.15.0 #4383
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
0.15.0 uses new ABL, please update settings and verify again. |
Same |
That is expected. ABL calculation has been moved into LED output driver to support per output limitations. |
@blazoncek got it, sadly that way the consuption of the esp itself is lost. |
ESP current is 120mA constant and irrelevant when LEDs are off as far as calculation goes. |
it's not reported to Home Assistant Integration also, lost my power consumption values after 0.15.0 |
that's right, same here. |
@blazoncek would it be possible to just report the 0.12A fixed instead of 'not calculated'? Or is there any good reason to break backward compatibility with HA? If this is something that is not possible with the new ABL, then this needs to be reported to HA to implement a fix for the new behaviour IMHO. |
@DedeHai please cherry-pick blazoncek/WLED@eb748f5 from my repo. |
@AlexKusnezov can you check if its ok now? latest bin with a fix is here: https://github.com/Aircoookie/WLED/actions/runs/12378696924 |
thanks, looks good. |
What happened?
Estimated Current Isn't Reported When off Since 0.15.0:

0.14.0:

Brighness limiter was on in both cases
After reverting back to 0.14.0 brightness limiter got disbaled so I had to re-enable it manually
Also on Athom bulbs 0.15.0 doesn't report estimated current at all!
To Reproduce Bug
Expected Behavior
Estimated Current should be prperly reported
Install Method
Binary from WLED.me
What version of WLED?
0.15.0
Which microcontroller/board are you seeing the problem on?
ESP32
Relevant log/trace output
No response
Anything else?
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: