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

Can not turn on LEDS with version above 14.0 #3854

Closed
1 task done
tomlut opened this issue Mar 25, 2024 · 3 comments
Closed
1 task done

Can not turn on LEDS with version above 14.0 #3854

tomlut opened this issue Mar 25, 2024 · 3 comments
Labels
bug fixed in source This issue is unsolved in the latest release but fixed in master

Comments

@tomlut
Copy link

tomlut commented Mar 25, 2024

What happened?

I have a Hyperion ambilight set up behind my TV consisting of:

250 LED WS2812 on segment 0, UDP sync interface enabled for main segment
20A 5V power supply (multiple injection points).
Quinled ESP32, data pin GPIO26

Using version 14.0 this works perfectly. Syncs with video frames and LEDs on/off control operates as expected.

Using any later version (14.1, 14.2) installed and configured fresh, (to eliminate update json config migration as the cause) the LEDs initially turn on but after turning off the LEDs either via the WLED web interface or the Hyperion interface the LEDs can not be turned back on.

To Reproduce Bug

Install 14.1 or later version.
Turn off LEDs, attempt to turn LEDs back on.

Expected Behavior

LED control and sync to operate.

Install Method

Binary from WLED.me

What version of WLED?

14.1, 14.2

Which microcontroller/board are you seeing the problem on?

ESP32

Relevant log/trace output

No response

Anything else?

Config file:

wled_cfg_tv-led-strip.json

Screenshot 2024-03-26 at 09-06-19 Sync Settings

Code of Conduct

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

I was able to replicate this using Hyperion on v0.14.2, but not with a build of v0.15. I am still investigating. Hyperion sets a transition time of 0 - I think this might be related.

@blazoncek
Copy link
Collaborator

yes, transition time 0 causes issues on 0.14

@willmmiles
Copy link
Contributor

OK - I think you can close this as a duplicate of #3720 then.

@blazoncek blazoncek closed this as not planned Won't fix, can't repro, duplicate, stale Mar 29, 2024
blazoncek added a commit that referenced this issue Mar 29, 2024
- Fix for transition 0 (#3854, #3832, #3720)
- copyright year update
- updated AsyncWebServer to v2.2.0
@blazoncek blazoncek added the fixed in source This issue is unsolved in the latest release but fixed in master label Mar 29, 2024
SonoDavid pushed a commit to SonoDavid/WLED that referenced this issue Apr 3, 2024
- Fix for transition 0 (Aircoookie#3854, Aircoookie#3832, Aircoookie#3720)
- copyright year update
- updated AsyncWebServer to v2.2.0

Changed wordclock mod to dutch version

Added wordclock NL version
softhack007 pushed a commit to MoonModules/WLED that referenced this issue Apr 9, 2024
- Fix for transition 0 (Aircoookie#3854, Aircoookie#3832, Aircoookie#3720)
- copyright year update
- updated AsyncWebServer to v2.2.0
adamsthws pushed a commit to adamsthws/WLED that referenced this issue May 9, 2024
- Fix for transition 0 (Aircoookie#3854, Aircoookie#3832, Aircoookie#3720)
- copyright year update
- updated AsyncWebServer to v2.2.0
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