[BUG] DPL stops itself right after starting

[fmueck]

Is there an existing issue for this?

• I have searched the existing issues

Check common causes of LMS (plugin) problems

• The list has no fix for my issue

What happened?

I had the dynamic playlists working, adding new titles... but not consistently. It does not work anymore now, after trying different players, restarts etc.
My setup consists of different players, where I tried to start/stop different dynamic playlists. Can there only be one dynamic playlist playing on one server, or are the players completely independent?

Now when I start a DPL (be it on a Squeezelite player or a Baby), both from the Material UI and the squeezer app, it stops itself right away with the toast message: Dynamic playlist stopped

Meaning new titles are no longer added, and it effectively becomes a static playlist.
The DPL menu item also does not show the "active DPL" in this case. Starting the DPL from this menu also does not change the mentioned behavior.

Expected Behavior

DPLs should work normally and not stop adding tracks right after being started.

Steps To Reproduce

Start a DPL, check if new tracks are being added as you move through the playlist.

LMS version

9.0.4

Plugin version

4.5.4

Your OS (incl. version)

Debian (Docker) - EN - utf8

What web skins / controllers are you seeing the problem with?

Material

Please check whether the problem can be reproduced with other web skins / controllers.

• I have checked this

What browsers are you seeing the problem on?

Firefox

Environment

Lyrion Music Server Status
Lyrion Music Server Version: 9.0.4 - 1759678152 @ Mon Oct 6 03:47:26 UTC 2025
Hostname: schmalzserver
Server IP Address: 192.168.11.111
Server HTTP Port Number: 9000
Operating system: Debian (Docker) - EN - utf8
Platform Architecture: x86_64-linux
Database Version: SQLite
Total Players Recognized: 7
 
Perl and Module Versions
Perl Version: 5.36.0 - x86_64-linux-gnu-thread-multi
Audio::Scan: 1.10
DBD::SQLite: 1.58 (sqlite 3.22.0)
IO::Socket::SSL: 2.081
Mozilla::CA: Unknown
Net::SSLeay: 1.92 - OpenSSL 3.0.17 1 Jul 2025

Is there relevant log output for this?

• I have searched the server log

Relevant log output

[25-10-18 14:32:47.2978] Plugins::DynamicPlaylists4::ProtocolHandler::overridePlayback (64) fav list client command = [
  "dynamicplaylist",
  "playlist",
  "play",
  "playlistid:dplccustom_test-dpl",
]
[25-10-18 14:32:47.2979] Plugins::DynamicPlaylists4::Plugin::cliPlayPlaylist (3327) Entering cliPlayPlaylist
[25-10-18 14:32:47.2981] Plugins::DynamicPlaylists4::Plugin::cliPlayPlaylist (3356) params = { playlistid => "dplccustom_test-dpl" }
[25-10-18 14:32:47.2982] Plugins::DynamicPlaylists4::Plugin::cliPlayPlaylist (3359) number of user req params = 0
[25-10-18 14:32:47.2982] Plugins::DynamicPlaylists4::Plugin::cliPlayPlaylist (3371) Got: playlistid = dplccustom_test-dpl
[25-10-18 14:32:47.2983] Plugins::DynamicPlaylists4::Plugin::stateStop (1475) stateStop
[25-10-18 14:32:47.2985] Plugins::DynamicPlaylists4::Plugin::getPlayList (513) Get playlist: dplccustom_test-dpl
[25-10-18 14:32:47.2985] Plugins::DynamicPlaylists4::Plugin::playRandom (818) playRandom called with type dplccustom_test-dpl
[25-10-18 14:32:47.2986] Plugins::DynamicPlaylists4::Plugin::playRandom (821) pluginData type for myPlayer = dplccustom_test-dpl
[25-10-18 14:32:47.2988] Plugins::DynamicPlaylists4::Plugin::clearPlayListHistory (7126) Deleting playlist history for player: myPlayer
[25-10-18 14:32:47.2990] Plugins::DynamicPlaylists4::Plugin::clearCache (7183) Multiple clients: Clearing cache for client: 00:aa:aa:aa:aa:aa:
[25-10-18 14:32:47.2991] Plugins::DynamicPlaylists4::Plugin::getPlayList (513) Get playlist: dplccustom_test-dpl
[25-10-18 14:32:47.2992] Plugins::DynamicPlaylists4::Plugin::playRandom (891) playlistLimitOption = undef
[25-10-18 14:32:47.2993] Plugins::DynamicPlaylists4::Plugin::playRandom (904) requested dpl = dplccustom_test-dpl
[25-10-18 14:32:47.2993] Plugins::DynamicPlaylists4::Plugin::playRandom (905) complete client mixinfo dump = {}
[25-10-18 14:32:47.2994] Plugins::DynamicPlaylists4::Plugin::playRandom (912) Play or DSTM play -- numItems = maxNumberUnplayedTracks = 20
[25-10-18 14:32:47.2995] Plugins::DynamicPlaylists4::Plugin::playRandom (934) 
Current client playlist before adding new tracks:
tracks in total: 1
songs remaining: 0
songIndex: 0
MIN. number of unplayed songs to be added: 5
MAX. number of new unplayed tracks to be added: 20
Actual number of tracks to be added (numItems): 20
[25-10-18 14:32:47.3002] Plugins::DynamicPlaylists4::Plugin::findAndAdd (526) Starting random selection of max. 20 items for type: dplccustom_test-dpl
[25-10-18 14:32:47.3003] Plugins::DynamicPlaylists4::Plugin::getPlayList (513) Get playlist: dplccustom_test-dpl
[25-10-18 14:32:47.3003] Plugins::DynamicPlaylists4::Plugin::findAndAdd (533) is static PL = undef
[25-10-18 14:32:47.3004] Plugins::DynamicPlaylists4::Plugin::findAndAdd (535) playlistTrackOrder = undef
[25-10-18 14:32:47.3005] Plugins::DynamicPlaylists4::Plugin::findAndAdd (543) dplUseCache = 1
[25-10-18 14:32:47.3006] Plugins::DynamicPlaylists4::Plugin::findAndAdd (557) Cache empty. Getting track IDs
[25-10-18 14:32:47.3007] Plugins::DynamicPlaylists4::Plugin::findAndAdd (562) Iteration 1: total trackIDs so far = 0 -- limit = 20 -- offset = 0
[25-10-18 14:32:47.3007] Plugins::DynamicPlaylists4::Plugin::getTrackIDsForPlaylist (1384) Calling: Plugins::DynamicPlaylists4::Plugin with: id = dplccustom_test-dpl, limit = 20, offset = 0
[25-10-18 14:32:47.3008] Plugins::DynamicPlaylists4::Plugin::getTrackIDsForPlaylist (1402) parameterHash = {}
[25-10-18 14:32:47.3009] Plugins::DynamicPlaylists4::Plugin::getTrackIDsForPlaylist (1403) Calling: Plugins::DynamicPlaylists4::Plugin :: getNextDynamicPlaylistTracks
[25-10-18 14:32:47.3010] Plugins::DynamicPlaylists4::Plugin::getNextDynamicPlaylistTracks (6120) Getting tracks for dynamic playlist: 'test-dpl' with ID: test-dpl
[25-10-18 14:32:47.3011] Plugins::DynamicPlaylists4::Plugin::getNextDynamicPlaylistTracks (6121) limit = 20, offset = 0, parameters = {}
[25-10-18 14:32:47.3012] Plugins::DynamicPlaylists4::Plugin::getInternalParameters (6243) playlistLimitOption = undef
[25-10-18 14:32:47.3013] Plugins::DynamicPlaylists4::Plugin::getInternalParameters (6245) playlistVLnames = undef
[25-10-18 14:32:47.3014] Plugins::DynamicPlaylists4::Plugin::getInternalParameters (6247) playlistVLids = undef
[25-10-18 14:32:47.3016] Plugins::DynamicPlaylists4::Plugin::getInternalParameters (6321) pluginData 'cachedArtists' = {}
[25-10-18 14:32:47.3017] Plugins::DynamicPlaylists4::Plugin::getInternalParameters (6322) pluginData 'cachedAlbums' = {}
[25-10-18 14:32:47.3018] Plugins::DynamicPlaylists4::Plugin::replaceParametersInSQL (6367) Replacing 'PlaylistMinAlbumTracks' with 3
[25-10-18 14:32:47.3019] Plugins::DynamicPlaylists4::Plugin::replaceParametersInSQL (6367) Replacing 'PlaylistTrackMinDuration' with 90
[25-10-18 14:32:47.3019] Plugins::DynamicPlaylists4::Plugin::replaceParametersInSQL (6367) Replacing 'PlaylistVariousArtistsString' with NULL
[25-10-18 14:32:47.3020] Plugins::DynamicPlaylists4::Plugin::replaceParametersInSQL (6367) Replacing 'PlaylistVariousArtistsID' with 8818
[25-10-18 14:32:47.3020] Plugins::DynamicPlaylists4::Plugin::replaceParametersInSQL (6367) Replacing 'PlaylistExcludedGenres' with 
[25-10-18 14:32:47.3021] Plugins::DynamicPlaylists4::Plugin::replaceParametersInSQL (6367) Replacing 'PlaylistOffset' with 0
[25-10-18 14:32:47.3022] Plugins::DynamicPlaylists4::Plugin::replaceParametersInSQL (6367) Replacing 'PlaylistTopRatedMinRating' with 60
[25-10-18 14:32:47.3022] Plugins::DynamicPlaylists4::Plugin::replaceParametersInSQL (6367) Replacing 'PlaylistLimit' with 20
[25-10-18 14:32:47.3023] Plugins::DynamicPlaylists4::Plugin::replaceParametersInSQL (6367) Replacing 'PlaylistPlayer' with '00:aa:aa:aa:aa:aa:'
[25-10-18 14:32:47.3023] Plugins::DynamicPlaylists4::Plugin::replaceParametersInSQL (6367) Replacing 'PlaylistMinArtistTracks' with 3
[25-10-18 14:32:47.3024] Plugins::DynamicPlaylists4::Plugin::replaceParametersInSQL (6367) Replacing 'PlaylistPeriodPlayedLongAgo' with 2
[25-10-18 14:32:47.3024] Plugins::DynamicPlaylists4::Plugin::replaceParametersInSQL (6367) Replacing 'PlaylistCurrentVirtualLibraryForClient' with ''
[25-10-18 14:32:47.3025] Plugins::DynamicPlaylists4::Plugin::getNextDynamicPlaylistTracks (6127) sqlstatement = select tracks.id, tracks.primary_artist from tracks join genre_track on genre_track.track = tracks.id join genres on genres.id = genre_track.genre and genres.namesearch in ('TESTGENRE') left join dynamicplaylist_history on dynamicplaylist_history.id = tracks.id and dynamicplaylist_history.client = '00:aa:aa:aa:aa:aa:' WHERE tracks.audio = 1 and dynamicplaylist_history.id is null group by tracks.id
[25-10-18 14:32:47.3038] Plugins::DynamicPlaylists4::Plugin::getNextDynamicPlaylistTracks (6180) sql statement 1: exec time = 0.00122904777526855 secs
[25-10-18 14:32:47.3038] Plugins::DynamicPlaylists4::Plugin::getNextDynamicPlaylistTracks (6182) Got 489 track IDs
[25-10-18 14:32:47.3039] Plugins::DynamicPlaylists4::Plugin::getTrackIDsForPlaylist (1409) Found 489 trackIDs for playlist 'test-dpl'
[25-10-18 14:32:47.3039] Plugins::DynamicPlaylists4::Plugin::findAndAdd (573) Iteration 1: returned 489 tracks in 0.00320816040039062 seconds
[25-10-18 14:32:47.3040] Plugins::DynamicPlaylists4::Plugin::findAndAdd (604) Adding new tracks to total tracks vars exec time = 3.09944152832031e-06 secs
[25-10-18 14:32:47.3040] Plugins::DynamicPlaylists4::Plugin::findAndAdd (605) Total track IDs found so far = 489
[25-10-18 14:32:47.3045] Plugins::DynamicPlaylists4::Plugin::findAndAdd (611) Storing complete info hash in cache exec time = 0.000468969345092773 secs
[25-10-18 14:32:47.3046] Plugins::DynamicPlaylists4::Plugin::findAndAdd (637) total tracks in cache = 489
[25-10-18 14:32:47.3047] Plugins::DynamicPlaylists4::Plugin::findAndAdd (638) Total exec time so far = 0.00442314147949219 secs
[25-10-18 14:32:47.3047] Plugins::DynamicPlaylists4::Plugin::findAndAdd (647) Shuffling ALL track IDs for cache
[25-10-18 14:32:47.3048] Plugins::DynamicPlaylists4::Plugin::shuffleIDlist (746) Using normal shuffle mode
[25-10-18 14:32:47.3049] Plugins::DynamicPlaylists4::Plugin::shuffleIDlist (749) Shuffle exec time: 0.000153064727783203 secs
[25-10-18 14:32:47.3050] Plugins::DynamicPlaylists4::Plugin::findAndAdd (659) Limiting the number of new tracks to be added to the specified limit (20)
[25-10-18 14:32:47.3052] Plugins::DynamicPlaylists4::Plugin::findAndAdd (669) Limiting exec time: 0.000124216079711914 secs
[25-10-18 14:32:47.3069] Plugins::DynamicPlaylists4::Plugin::findAndAdd (686) Adding new tracks from cache to DPL history exec time: 0.0016782283782959 secs
[25-10-18 14:32:47.3070] Plugins::DynamicPlaylists4::Plugin::findAndAdd (691) Shuffling limited track ID selection
[25-10-18 14:32:47.3070] Plugins::DynamicPlaylists4::Plugin::shuffleIDlist (746) Using normal shuffle mode
[25-10-18 14:32:47.3071] Plugins::DynamicPlaylists4::Plugin::shuffleIDlist (749) Shuffle exec time: 4.29153442382812e-05 secs
[25-10-18 14:32:47.3071] Plugins::DynamicPlaylists4::Plugin::findAndAdd (709) Playing dplccustom_test-dpl with first trackid 49445
[25-10-18 14:32:47.3556] Plugins::DynamicPlaylists4::Plugin::findAndAdd (717) Adding 19 tracks to the end of the playlist.
[25-10-18 14:32:47.3669] Plugins::DynamicPlaylists4::Plugin::findAndAdd (725) Adding tracks to client playlist exec time: 0.0597159862518311 secs
[25-10-18 14:32:47.3669] Plugins::DynamicPlaylists4::Plugin::findAndAdd (727) Got 20 tracks for dynamic playlist "test-dpl" in 0.0667030811309814 seconds.

[25-10-18 14:32:47.3676] Plugins::DynamicPlaylists4::Plugin::playRandom (969) number of added items = 20
[25-10-18 14:32:47.3677] Plugins::DynamicPlaylists4::Plugin::getMsgDisplayTime (7499) Display time: 2.45s for message 'Starting dynamic playlist:test-dpl'
[25-10-18 14:32:47.3678] Plugins::DynamicPlaylists4::Plugin::getMsgDisplayTime (7499) Display time: 2.52s for message 'Starting dynamic playlist: test-dpl'
[25-10-18 14:32:47.3681] Plugins::DynamicPlaylists4::Plugin::stateNew (1443) stateNew with dpl type 'dplccustom_test-dpl' and params: {}
[25-10-18 14:32:47.3682] Plugins::DynamicPlaylists4::Plugin::cliPlayPlaylist (3391) Exiting cliPlayPlaylist
[25-10-18 14:32:47.3718] Plugins::DynamicPlaylists4::Plugin::commandCallback (7360) received command initiated by /eaa006d6/slim/playerprefs/00:aa:aa:aa:aa:aa:|387||eaa006d6|Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:144.0) Gecko/20100101 Firefox/144.0
[25-10-18 14:32:47.3719] Plugins::DynamicPlaylists4::Plugin::commandCallback (7368) Skipping playlist play dynamicplaylist://dplccustom_test-dpl
[25-10-18 14:32:47.3728] Plugins::DynamicPlaylists4::Plugin::commandCallback (7360) received command initiated by /eaa006d6/slim/playerprefs/00:aa:aa:aa:aa:aa:|387||eaa006d6|Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:144.0) Gecko/20100101 Firefox/144.0
[25-10-18 14:32:47.3728] Plugins::DynamicPlaylists4::Plugin::commandCallback (7373) received command dynamicplaylist playlist play
[25-10-18 14:32:47.3729] Plugins::DynamicPlaylists4::Plugin::commandCallback (7381) while in mode: dplccustom_test-dpl, from myPlayer
[25-10-18 14:32:47.3774] Plugins::DynamicPlaylists4::Plugin::commandCallback (7360) received command initiated by /eaa006d6/slim/playerprefs/00:aa:aa:aa:aa:aa:|387||eaa006d6|Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:144.0) Gecko/20100101 Firefox/144.0
[25-10-18 14:32:47.3774] Plugins::DynamicPlaylists4::Plugin::commandCallback (7373) received command playlist loadtracks
[25-10-18 14:32:47.3775] Plugins::DynamicPlaylists4::Plugin::commandCallback (7381) while in mode: dplccustom_test-dpl, from myPlayer
[25-10-18 14:32:47.3776] Plugins::DynamicPlaylists4::Plugin::commandCallback (7420) cyclic mode ending due to playlist: playlist loadtracks command
[25-10-18 14:32:47.3776] Plugins::DynamicPlaylists4::Plugin::getPlayList (513) Get playlist: disable
[25-10-18 14:32:47.3777] Plugins::DynamicPlaylists4::Plugin::playRandom (818) playRandom called with type disable
[25-10-18 14:32:47.3777] Plugins::DynamicPlaylists4::Plugin::playRandom (821) pluginData type for myPlayer = disable
[25-10-18 14:32:47.3778] Plugins::DynamicPlaylists4::Plugin::playRandom (822) client pref type = dplccustom_test-dpl
[25-10-18 14:32:47.3778] Plugins::DynamicPlaylists4::Plugin::getPlayList (513) Get playlist: dplccustom_test-dpl
[25-10-18 14:32:47.3779] Plugins::DynamicPlaylists4::Plugin::clearPlayListHistory (7126) Deleting playlist history for player: myPlayer
[25-10-18 14:32:47.3781] Plugins::DynamicPlaylists4::Plugin::clearCache (7183) Multiple clients: Clearing cache for client: 00:aa:aa:aa:aa:aa:
[25-10-18 14:32:47.3784] Plugins::DynamicPlaylists4::Plugin::playRandom (891) playlistLimitOption = undef
[25-10-18 14:32:47.3784] Plugins::DynamicPlaylists4::Plugin::playRandom (904) requested dpl = disable
[25-10-18 14:32:47.3786] Plugins::DynamicPlaylists4::Plugin::playRandom (905) complete client mixinfo dump = { offset => 20, type => "dplccustom_test-dpl" }
[25-10-18 14:32:47.3786] Plugins::DynamicPlaylists4::Plugin::playRandom (906) currently active dpl = "dplccustom_test-dpl"
[25-10-18 14:32:47.3787] Plugins::DynamicPlaylists4::Plugin::playRandom (934) 
Current client playlist before adding new tracks:
tracks in total: 20
songs remaining: 19
songIndex: 0
MIN. number of unplayed songs to be added: 5
MAX. number of new unplayed tracks to be added: 20
Actual number of tracks to be added (numItems): 0
[25-10-18 14:32:47.3787] Plugins::DynamicPlaylists4::Plugin::playRandom (1011) cyclic mode ended
[25-10-18 14:32:47.3787] Plugins::DynamicPlaylists4::Plugin::getMsgDisplayTime (7499) Display time: 2.87s for message 'Dynamic PlaylistsDynamic playlist stopped'
[25-10-18 14:32:47.3789] Plugins::DynamicPlaylists4::Plugin::getMsgDisplayTime (7499) Display time: 2s for message 'Dynamic playlist stopped'
[25-10-18 14:32:47.3791] Plugins::DynamicPlaylists4::Plugin::stateStop (1475) stateStop
[25-10-18 14:32:47.3792] Plugins::DynamicPlaylists4::Plugin::stateStop (1475) stateStop
[25-10-18 14:32:47.3793] Plugins::DynamicPlaylists4::Plugin::clearPlayListHistory (7126) Deleting playlist history for player: myPlayer
[25-10-18 14:32:47.3794] Plugins::DynamicPlaylists4::Plugin::clearCache (7183) Multiple clients: Clearing cache for client: 00:aa:aa:aa:aa:aa:
[25-10-18 14:32:47.7928] Plugins::DynamicPlaylists4::Plugin::commandCallback (7360) received command initiated by /eaa006d6/slim/playerprefs/00:aa:aa:aa:aa:aa:|387||eaa006d6|Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:144.0) Gecko/20100101 Firefox/144.0
[25-10-18 14:32:47.7929] Plugins::DynamicPlaylists4::Plugin::commandCallback (7373) received command playlist newsong

Anything else? 📎 Attachments etc.

No response

[AF-1]

4.5.4 was released in July. Haven't heard anything like this from users yet.

Can there only be one dynamic playlist playing on one server, or are the players completely independent?

Each player can play a different dynamic playlist.

Have you grouped your players? If so, ungroup them.
I just did a quick (successful) test with 3 Booms and 1 SB Radio all playing their own dynamic playlists. Used web browser as controller (Logic Teal skin). For one player I used Material (browser). LMS 9.0.4 same as you.

BTW did you redact the player mac address(es) from the server log? In your case they might be useful to see which players sends which command and when.

I suggest this test:
Maybe note the time (~hh:mm:ss) for important actions (and sometimes wait a few secs) so you can tie the actions to the server log messages.

1. ⚠️ Do not Material or another controller (app) first. Instead use the e.g. the Logic Teal skin in your browser for testing.
2. Clear the client playlist on all players.
3. Power off all but one player. Not just standby.
4. Start a dynamic playlist on the one remaining player.
5. It should start playing. Check dynamic playlist playback status in DPL home menu.
6. Forward to the next track. Check dynamic playlist playback status in DPL home menu.
7. Play the last track. It should add new songs at some point. Check dynamic playlist playback status in DPL home menu.
8. If this work as expected, leave the player playing the dynamic playlist.
9. Now power on another player.
10. Do you have a second browser installed? If so, you use this to control the second player. It's easier than clearing the cache when you switch between players.
11. Repeat steps 4-7 for this player with another dynamic playlist (easier to tell them apart in the log). BUT this time after each step check the dynamic playlist playback status in DPL home menu for both players.

Does it work? If not, let me know at which time you did what and post unredacted the server log.

If it worked, repeat the steps (2-11) with another controller. First Material. And then last with the squeezer app.

[fmueck]

Thank you AF-1 for promptly responding, and providing detailed instructions for further debugging.

The issue was caught with the second player - both players in this case were Squeezelites. Everything worked fine on the first one, but when skipping a song on the second player, it no longer showed its active DPL (first player kept playing unaffected).

Second player was controlled using a different browser, with Logic Teal. Initialization steps done as requested. Unfortunately I missed your suggestion to note the crucial times 😬, so times in the log are the only times.

⚠️ Do not Material or another controller (app) first. Instead use the e.g. the Logic Teal skin in your browser for testing.	
  ok
Clear the client playlist on all players.
  ok
Power off all but one player. Not just standby.
  ok

STUDIO (Squeezelite)
Start a dynamic playlist on the one remaining player.
ok
It should start playing. Check dynamic playlist playback status in DPL home menu.
ok
Forward to the next track. Check dynamic playlist playback status in DPL home menu.
ok
Play the last track. It should add new songs at some point. Check dynamic playlist playback status in DPL home menu.
ok
If this work as expected, leave the player playing the dynamic playlist.
ok
Now power on another player.

GLASHAUS (Squeezelite)
Start a dynamic playlist on the one remaining player.
ok
It should start playing. Check dynamic playlist playback status in DPL home menu.
both ok
Forward to the next track. Check dynamic playlist playback status in DPL home menu.
ACTIVE DPL NO LONGER VISIBLE IN SECOND PLAYER, first player is ok
Find the "stopped" string in the logs at line 2946
Play the last track. It should add new songs at some point. Check dynamic playlist playback status in DPL home menu.
same situation

What might look a bit strange is in line 2897-2898. _getTargetPlayerList now suddenly refers to the first, already playing player (Studio), while we are handling the second one (Glashaus):

[25-10-19 13:00:37.4727] Plugins::DynamicPlaylists4::Plugin::handleWebList (1535) active dynamic playlist for client "Glashaus" = mobile_dpl
[25-10-19 13:00:37.4729] Plugins::DynamicPlaylists4::Plugin::_getTargetPlayerList (5976) targetPlayerList = [{ id => "00:00:00:00:00:00", name => "Studio" }]

Player info of those involved (MAC all zeros looks a bit strange, but this was the working player):

  Glashaus
  Player Model: SqueezeLite
  Player Type: squeezelite
  Firmware: v1.9.9-1372
  Player IP Address: 192.168.11.11
  Player MAC Address: b8:27:eb:66:57:49
   
  Studio
  Player Model: SqueezeLite
  Player Type: squeezelite
  Firmware: v1.9.9-1372
  Player IP Address: 192.168.11.100
  Player MAC Address: 00:00:00:00:00:00

Also curious that fhe "initiated by" lines all point towards Firefox, while I definitely did the operations on the second player in MS Edge.

Unredacted log attached, hth.

dpl4-server.log

Trying to restart the DPL on the second player loads the playlist, and the active DPL shows up momentarily in the Home > Dynamic Playlists view for the player, but reloading that view I notice that is immediately not showing any active DPL anymore for the player.

[AF-1]

Is the one with the zeros running on the same machine as LMS?

❗️ And you didn't say: have you synced or grouped any of your players?
BTW please add a list of your installed plugins.

Lines 2897-2898 are harmless, just reporting where you can transfer your active dynamic playlist to.
But there is this line:

[25-10-19 13:00:37.4794] Plugins::DynamicPlaylists4::Plugin::commandCallback (7373) received command playlist loadtracks

If some other plugin or process sends a playlist loadtracks command, this would make DPL stop the active dynamic playlist. loadtracks is one of several stop commands.
2 lines down is the confirmation:

[25-10-19 13:00:37.4795] Plugins::DynamicPlaylists4::Plugin::commandCallback (7420) cyclic mode ending due to playlist: playlist loadtracks command

I've noticed that you seem to have 2 SB Radios connected to LMS.

Could you please kill all squeezelite players and try the test (outlined in my last post) with the 2 SB Radios and Logic Teal?
Please let me know the time stamp of when you start a dynamic playlist on your second player.

P.S. And include the unredacted log, of course. Thanks.

[fmueck]

Is the one with the zeros running on the same machine as LMS?

Yes! But, it is not the same LMS that the players are currently connected to. It is the old LMS which I am migrating away from (no players are connected to it any more, but it is still up). Should I kill it for testing?

And you didn't say: have you synced or grouped any of your players?

No players are synced or grouped at this time. Sidenote here, with the old LMS I noticed that sometimes the players were back in a group that I removed long ago after a restart... but not recently, and not with the new LMS.

BTW please add a list of your installed plugins.

I was looking for a way to get a list of them, but I cannot find it; so pasting a screenshot:

Now, on to the test sequence as you suggested with only the HW players, using Teal and two browsers, all Squeezelites killed (but the old LMS also still up).
Summary: First try failed, but then after a server restart, it is working. So... the squeezelites could have something to do with it?

RADIO EG (Baby)
Start a dynamic playlist on the one remaining player.
19:04:22 - ok
It should start playing. Check dynamic playlist playback status in DPL home menu.
19:04:50 - no, it does not show the active DPL.
Restarting the server to start off fresh.

RADIO EG (Baby)
Start a dynamic playlist on the one remaining player.
19:08:21 - ok
It should start playing. Check dynamic playlist playback status in DPL home menu.
19:08:01 - ok, active DPL confirmed
Forward to the next track. Check dynamic playlist playback status in DPL home menu.
19:09:00 - ok, active DPL confirmed
Play the last track. It should add new songs at some point. Check dynamic playlist playback status in DPL home menu.
19:09:47 - ok, active DPL confirmed
If this work as expected, leave the player playing the dynamic playlist.
ok

Now power on another player.
RADIO OG (Baby)
19:10:32 powered on.

Start a dynamic playlist on the one remaining player.
19:11:14 - ok, active DPL confirmed on both players.
It should start playing. Check dynamic playlist playback status in DPL home menu.
Forward to the next track. Check dynamic playlist playback status in DPL home menu.
19:12:59 - ok, active DPL confirmed on both players.
Play the last track. It should add new songs at some point. Check dynamic playlist playback status in DPL home menu.
19:13:33 - ok, active DPL confirmed on both players.

dpl4-2-server.log

[AF-1]

Haven't had a chance to look at the new log but I suspected that the Squeezelite players had something to do with this.
In your first log I saw a couple of lines with commands coming in that I've never had with any players used for testing (Boom, Radio, SqueezePlay, Touch, pCP).

How many Squeezelite players are there in your lineup? One is from the Local Player plugin, right? On what machine is the second Squeezelite player running? Also, Local Player plugin or bare-metal install?

When you're doing tests, I'd definitely stop/kill the old LMS if it's on the same network as the new one and players can still connect to it. BTW I usually stop LMS before testing, delete the server log and then restart. Keeps the log clean.

You could run another test with the 2 Squeezelite players: stop/kill the old LMS (any LMS really but the new one), connect both Squeezelite players to new LMS, then power off one of them and start the test.

Anyway, just wanted to let you know that it'll probably take a week or two before I find the time to do further testing on my end.

[fmueck]

The setup:

• Two Squeezebox Radios
• One Raspberry Pi Zero W running Squeezelite under Raspbian, package install. Just updated to latest sourceforge version as of today.
• One Raspberry Pi Zero W 2 running newest pCP.
• One Raspberry 3B running Squeezelite under Raspbian, package install. Just updated to latest sourceforge version as of today. The former LMS was running there, and is now stopped.
• One x86 server hosting the new LMS in a docker install, on Fedora 42. On the same machine, there is another squeezelite player running, just the regular updated Fedora package. The local player in docker did not work, so I kept the squeezelite there as-is.

Fixed the all-zero MAC problem by changing the squeezelite runlevel to network-online.

Also to note, homeassistant via the normal integration also has access to the LMS setup, in addition to the Squeezer mobile apps.

Just did a quick and dirty test with all players on (no logs):

• Start a DPL on a Squeezelite. OK - open the DPL menu to check.
• Just switching to another player in the Teal top right dropdown now leads to the following:
• The switched-to player now also immediately displays the active DPL and plays it
• Other players in the house turn on and also show the very same DPL!
  It looks like in this scenario, there might be a problem that leads to players and DPLs being mixed up. Very strange (and different to the other behaviour from before, that DPLs are stopped right after they are started. Will keep a look out for that one too of course).

Anyway, just wanted to let you know that it'll probably take a week or two before I find the time to do further testing on my end.

Thank you for letting me know, no worries.

[AF-1]

I did some tests with Squeezelite here but couldn't reproduce your issue. To be fair, I can't 100% rebuild your setup with all those players.

I've made some changes to the plugin (4.5.5): Many debug log messages which are usually not needed for most debug use cases are no longer written to the log by default (but can be reenabled in DPL settings). That should get many messages out of the way with no relevance to your issue.
And I've mofified the debug messages in the commandCallback function to make it clear(er) which player sends which command. Well, I've tried.
So when you do your tests, search for messages with DynamicPlaylists4::Plugin::commandCallback.
Assuming that all of your players have a unique id / MAC address, you basically have to find out what's sending the playlist loadtracks command to the server which makes DPL stop adding tracks.

* Just switching to another player in the Teal top right dropdown now leads to the following:
* The switched-to player now also immediately displays the active DPL and plays it
* Other players in the house turn on and also show the very same DPL!

I've known about this for a long time. I think it's a skin issue. I don't remember exactly if it was a timing or a cache issue or something else completely. But I couldn't fix this on my end. AFAIK it doesn't happen with other controllers or skins (like Material).

[fmueck]

Did another testing session with the new plugin. At first, everything went quite smoothly, even with all players on (it seems that setting the plugin loglevel to DEBUG did not stick, or I mis-clicked APPLY or something, as there is no plugin log output during the "good" time). It got confusing, because I was only using Firefox and Edge to test, and even though using a new private Edge window for each player, they seem to switch back to another player at some point.
Then the "one player controls all" known bug you mentioned happened, and as you noted that it could be related to Teal, I switched to Material.
Using Material, on one player, I was unable to start a DPL - it was the same thing as before, "playlist stopped" right after the start, with an extremely short delay in the logs themselves. Note that I observed before that the "client" message is unreliable, it always shows Firefox even for the actions manually initated in Edge (maybe the http backend gets confused?).

[25-11-01 17:17:10.7032] Plugins::DynamicPlaylists4::Plugin::playRandom (974) number of added items = 20
[25-11-01 17:17:10.7033] Plugins::DynamicPlaylists4::Plugin::getMsgDisplayTime (7507) Display time: 2.94s for message 'Starting dynamic playlist:Artists - random'
[25-11-01 17:17:10.7035] Plugins::DynamicPlaylists4::Plugin::getMsgDisplayTime (7507) Display time: 3.01s for message 'Starting dynamic playlist: Artists - random'
[25-11-01 17:17:10.7038] Plugins::DynamicPlaylists4::Plugin::stateNew (1448) stateNew with dpl type 'dpldefault_artists_001_random' and params: { 1 => 0 }
[25-11-01 17:17:10.7039] Plugins::DynamicPlaylists4::Plugin::cliPlayPlaylist (3396) Exiting cliPlayPlaylist function
[25-11-01 17:17:10.7044] Plugins::DynamicPlaylists4::Plugin::commandCallback (7365) received command initiated by /bd4f7b72/slim/playerprefs/00:04:20:26:8f:c4|23||bd4f7b72|Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:144.0) Gecko/20100101 Firefox/144.0
[25-11-01 17:17:10.7045] Plugins::DynamicPlaylists4::Plugin::commandCallback (7379) received command: dynamicplaylist playlist play
[25-11-01 17:17:10.7046] Plugins::DynamicPlaylists4::Plugin::commandCallback (7388) client: "Radio EG" - "00:04:20:26:8f:c4"
[25-11-01 17:17:10.7046] Plugins::DynamicPlaylists4::Plugin::commandCallback (7389) masterClient: "Radio EG" - "00:04:20:26:8f:c4"
[25-11-01 17:17:10.7047] Plugins::DynamicPlaylists4::Plugin::commandCallback (7390) masterClient mixinfo type: dpldefault_artists_001_random
[25-11-01 17:17:10.7103] Plugins::DynamicPlaylists4::Plugin::commandCallback (7365) received command initiated by /bd4f7b72/slim/playerprefs/00:04:20:26:8f:c4|23||bd4f7b72|Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:144.0) Gecko/20100101 Firefox/144.0
[25-11-01 17:17:10.7104] Plugins::DynamicPlaylists4::Plugin::commandCallback (7379) received command: playlist loadtracks
[25-11-01 17:17:10.7105] Plugins::DynamicPlaylists4::Plugin::commandCallback (7388) client: "Radio EG" - "00:04:20:26:8f:c4"
[25-11-01 17:17:10.7105] Plugins::DynamicPlaylists4::Plugin::commandCallback (7389) masterClient: "Radio EG" - "00:04:20:26:8f:c4"
[25-11-01 17:17:10.7106] Plugins::DynamicPlaylists4::Plugin::commandCallback (7390) masterClient mixinfo type: dpldefault_artists_001_random
[25-11-01 17:17:10.7106] Plugins::DynamicPlaylists4::Plugin::commandCallback (7428) stop command detected: "playlist loadtracks". Let's stop adding tracks. Dynamic playlist is no longer active.

server.log

[AF-1]

About the browser-skin bug: I don't switch between players in the browsers (Safari, Firefox ESR) very often. But I seem to remember that you can sort of sometimes work around this bug. After I've started a dynamic playlist in the browser for player 1, I usually wait like 5 seconds before switching to another player. Or I reload the browser page before switching.

Concentrating on the commandCallback messages, here's an excerpt from my server.log where I started a new dynamic playlist on a Boom (Main) while 2 other Booms were playing different dynamic playlists:

[25-11-01 11:18:04.7577] Plugins::DynamicPlaylists4::Plugin::commandCallback (7365) received command initiated by JSONRPC
[25-11-01 11:18:04.7579] Plugins::DynamicPlaylists4::Plugin::commandCallback (7379) received command: dynamicplaylist playlist play
[25-11-01 11:18:04.7581] Plugins::DynamicPlaylists4::Plugin::commandCallback (7388) client: "Boom - Main" - "00:01:af:03:ff:05"
[25-11-01 11:18:04.7583] Plugins::DynamicPlaylists4::Plugin::commandCallback (7389) masterClient: "Boom - Main" - "00:01:af:03:ff:05"
[25-11-01 11:18:04.7585] Plugins::DynamicPlaylists4::Plugin::commandCallback (7390) masterClient mixinfo type: dpldefault_songs_073_notrated_by_genre_decade_ratedpercentage_dpsv_apc
[25-11-01 11:18:04.7620] Plugins::DynamicPlaylists4::Plugin::commandCallback (7366) received command initiated by PLUGIN_DYNAMICPLAYLISTS4
[25-11-01 11:18:05.3471] Plugins::DynamicPlaylists4::Plugin::active (7482) mixStatus = "dpldefault_songs_073_notrated_by_genre_decade_ratedpercentage_dpsv_apc"
[25-11-01 11:18:05.3497] Plugins::DynamicPlaylists4::Plugin::commandCallback (7379) received command: playlist newsong
[25-11-01 11:18:05.3500] Plugins::DynamicPlaylists4::Plugin::commandCallback (7388) client: "Boom - Main" - "00:01:af:03:ff:05"
[25-11-01 11:18:05.3502] Plugins::DynamicPlaylists4::Plugin::commandCallback (7389) masterClient: "Boom - Main" - "00:01:af:03:ff:05"
[25-11-01 11:18:05.3504] Plugins::DynamicPlaylists4::Plugin::commandCallback (7390) masterClient mixinfo type: dpldefault_songs_073_notrated_by_genre_decade_ratedpercentage_dpsv_apc
[25-11-01 11:18:05.3506] Plugins::DynamicPlaylists4::Plugin::commandCallback (7402) new song detected (0)
[25-11-01 11:18:05.3508] Plugins::DynamicPlaylists4::Plugin::commandCallback (7422) Will check in 20 seconds if new songs have to be added

No playlist loadtracks command here. And no interference with the dynamic playlists on the other Booms.

Here's a thought: Other users on the forum reported the same issue but not only with DPL, also for the LMS default plugin Random Mix AKA RandomPlay.
Maybe you could check if you can reproduce your issue with RandomPlay / Random Mix, meaning: Start a random mix on player 1, skip some tracks, let it play, then start a different random mix on player 2, and so on.
In version 4.5.6 I've moved even more debug level messages to the "verbose" debug log level (plugin settings, disabled by default). This should make it easier to find and focus on relevant (commandCallback) messages.

[mikeysas]

Interesting to follow. I am one of the folks who have stumbled on a similar sounding issue with DPL and Radom Mix. There are multiple threads going back several years on the Lyrion Forum discussing this issue (mostly with Random Mix) but nobody to date (myself included) have been able to consistently recreate the problem that I have seen where DPL or Random Mix just stops adding tracks. For me this issue is very random where sometimes it is week and often many months before it happens again.

[fmueck]

I will test this in more detail later, but from previous tests I recall that also with the normal random mix, the issue occured. So we might be on the right track there.