Skip to content
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

webui power button unresponsive after regaining control from hyperion #3865

Closed
1 task done
quixotic120 opened this issue Mar 29, 2024 · 1 comment
Closed
1 task done
Labels
bug fixed in source This issue is unsolved in the latest release but fixed in master

Comments

@quixotic120
Copy link

What happened?

in instances where hyperion fails to release control of WLED after powering off and a manual override is required I am unable to power off WLED with the webui. I can click the webui button and see the animation that indicates it was clicked but nothing occurs on the device. rebooting the device allows the button to work. All other features such as changing color, brightness, patterns, etc work after manual override. Power button does not work regardless of whether webui is accessed from browser (tested chrome, safari, firefox), iOS app, android app

issue occurred with both 14.1 and 14.2 but did not occur with 14.0 and prior

To Reproduce Bug

start hyperion
stop hyperion with failure to release control - if you manually override while hyperion is still running it tends to just regain control again
manually override
try to power off

Expected Behavior

WLED powers off

Install Method

Binary from WLED.me

What version of WLED?

0.14.2 2403170

Which microcontroller/board are you seeing the problem on?

ESP32

Relevant log/trace output

No response

Anything else?

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@willmmiles
Copy link
Contributor

Hyperion sets the transition time to 0, which is bugged in v0.14.1 and v0.14.2. Ref #3854 and #3720. v0.14.3 or newer should have the fix.

@blazoncek blazoncek added the fixed in source This issue is unsolved in the latest release but fixed in master label Mar 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug fixed in source This issue is unsolved in the latest release but fixed in master
Projects
None yet
Development

No branches or pull requests

3 participants