music-assistant / hass-music-assistant

Turn your Home Assistant instance into a jukebox, hassle free streaming of your favorite media to Home Assistant media players.
Apache License 2.0
1.39k stars 51 forks source link

Two parallel Playlists: only the most recent one visible #2714

Closed ccoenen closed 2 months ago

ccoenen commented 3 months ago

What version of Music Assistant has the issue?

2.1.0

What version of the Home Assistant Integration have you got installed?

2024.6.2

Have you tried everything in the Troubleshooting FAQ and reviewed the Open and Closed Issues and Discussions to resolve this yourself?

The problem

I have two speakers in two rooms that I would like to be able to play different music at times. This mostly works, but here's one problem I came across: If I am playing two playlists, I can only see the most recently added playlist, the other one is gone (even after selecting the other player!)

How to reproduce

grafik grafik

Music Providers

Subsonic

Player Providers

AirPlay and SONOS

Full log output

music-assistant.log

Additional information

All of the steps above were performed on the Music Assistant web client and not in HomeAssistant.

Home Assistant runs on x86_64 in a container Music Assistant runs on a Raspberry Pi in a container

What version of Home Assistant Core are your running

2024.7.4

What type of installation are you running?

Home Assistant Container

On what type of hardware are you running?

Linux

ccoenen commented 3 months ago

Interesting thing to note: once the second playlist is "done" playing, the first playlist will be displayed just fine.

OzGav commented 3 months ago

This is confirmed and will be addressed in due course.

marcelveldt commented 3 months ago

fixed in 2.2.0

OzGav commented 2 months ago

This is partially fixed. Whilst the different queues are displayed if you select between two players from the NOW PLAYING view the number of tracks shown changes. The number in the queue is always indicating correctly.

marcelveldt commented 2 months ago

try again with the 2.2.1 / 2.3.0b2

OzGav commented 2 months ago

Confirmed fixed.