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

Playlist cycling via presets is broken in 0.14.3 #3260

Closed
1 task done
alackmann opened this issue Jun 22, 2023 · 3 comments
Closed
1 task done

Playlist cycling via presets is broken in 0.14.3 #3260

alackmann opened this issue Jun 22, 2023 · 3 comments
Labels

Comments

@alackmann
Copy link
Contributor

What happened?

In my 0.13.x installation of WLED, you can create a preset with the API command similar to P1=20&P2=22&PL=~ that when triggered will cycle through playlists 20,21,22 and then back to 20. These can be triggered either from the WebUI by pressing the preset OR from an external button macro (among others).

In all the 0.14.x versions I've tried, this is no longer working. Instead it repeatedly triggers the first playlist in the list. So in the example above, the playlist in preset 20.

To Reproduce Bug

  • Create 3 new playlists via the UI. In this example using IDs 20, 21 & 22 for the presets. Put different presets within each playlist.
  • Create a preset (can be any ID, but let's call it 3 in this example) that has the API command P1=20&P2=22&PL=~ as the preset content
  • Using the web interface, click on the new preset 3
  • Playlist 20 will play
  • Click playlist 3 again
  • Playlist 20 will restart again

Expected Behavior

  • On the second click, playlist 21 should play.
  • On the third click, playlist 22 should play
  • On the fourth, the cycle should restart and playlist 20 should play

Install Method

Self-Compiled

What version of WLED?

WLED 0.14.0-b3 (build 2306210)

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
@blazoncek
Copy link
Collaborator

Please try JSON API instead of HTTP API.
I.e. {"ps":"20~22~"}

@alackmann
Copy link
Contributor Author

Neither were working @blazoncek. My PR fixes both.

@blazoncek
Copy link
Collaborator

It breaks other (legacy) things.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants