custom-cards / spotify-card

Spotify playlist card for Home Assistant card
Other
391 stars 64 forks source link

Current Player Device Wrong #116

Open nunofmds opened 4 years ago

nunofmds commented 4 years ago

Describe the bug A clear and concise description of what the bug is.

To Reproduce Steps to reproduce the behavior:

  1. Go to lovelace dashboard, select a group player with several cast devices
  2. Click on select any playlist and press play
  3. The current playing device changes to a standalone device from the group instead of keep the selection. The play continues to work on all of the group, so the functional part is working, only the selected device or current playing changes.

Expected behavior Keep the current playing device, group and any other that's selected.

Screenshots Selected to play on Ceiling All

image

Shows playing on Upstairs Bathroom but the playing is on Ceiling All image

Environment (please complete the following information):

Configuration Nothing special, everything standard.

Additional context

type: 'custom:spotify-card' limit: 8 spotify_entity: media_player.spotify_xnuno account: default grid_covers_per_row: 4 display_style: grid playlist_type: discover-weekly

FL550 commented 4 years ago

If you open the spotify app, what is the playback device shown there? The playback device is taken directly from spotify, so this could be the issue.

nunofmds commented 4 years ago

Yes it matches the info that's on the lovelace card... but I started the playlist from the lovelace card and selected the group and not the device currently being displayed on both, spotify and card.

FL550 commented 4 years ago

The card uses spotify for all information about playback. It can start playback on chromecast devices itself but any further interaction is done directly with spotify. So as far as I can see, there is unfortunately nothing we can do about this issue.

nunofmds commented 4 years ago

Yes but if I start the playlist from spotify and select the group it shows up correct on both, spotify and card.

This seems to be an issue from the card itself and the way it starts the broadcast or something...

FL550 commented 4 years ago

Maybe @fondberg has an idea?

fondberg commented 4 years ago

I think this is an issue with groups only and the way spotify reports playback. Chromecast has implemented groups but spotify hasnt so there is a master cast device which is listed as playing in spotify apis if i remember correctly

nunofmds commented 4 years ago

Ok... strange that if i start the cast from spotify app everything works as expected on both sides... anything I can do to help fixing this?

fondberg commented 4 years ago

I need to try an replicate it. Will have some time soon to look into it.

I will ping you if i need some help

fondberg commented 3 years ago

Is this still an issue?

IAmBecomeDeth commented 1 year ago

I can confirm this as well. I came to report it.

Functionally works, but once playing music, shows wrong cast destination. I have 12 cast devices and 5 or so groups for each room as well as multiple "party" settings for including or not including bedrooms or bathrooms. I'm not sure if I'm overloading the list, maybe?

When I choose to play on "party" or "party2 or any cast group (99% of usage) it says "Bedroom Second Speaker". If I choose a specific device, it will say the correct device. If I set cast to party from my phone, current player shows correctly in both Spotify app and Lovelace.

I noticed that when selecting from phone, it shows "Party" (chrome cast group) under Spotify connect. When listed under chrome cast it does not show correctly.

IAmBecomeDeth commented 1 year ago

Testing more over the past few hours... The incorrect device that's being displayed is not static. Now it shows a different (also incorrect) device. Additionally, I figured out that the current destination shows up as Spotify connect whether correct or incorrect, so that isn't the reason. I'm going to test adding party to my known devices and see if it makes any difference. Won't be able to test til tomorrow.

It's really odd that it's showing the information incorrectly in Spotify app...yet still working as expected on the correct speaker group.