SpotifyPlus Card Dashboard

For a playlist:-

  "currently_playing_type": "track",
  "actions": {
    "disallows": {
      "skipping_prev": true,
      "toggling_repeat_track": true
    }
  },
  "smart_shuffle": false

For an album:-

  "currently_playing_type": "track",
  "actions": {
    "disallows": {
      "toggling_repeat_track": true
    }
  },
  "smart_shuffle": false
1 Like

I think I found the issue - coding bug on my part.

It appears that I have the toggling_repeat_track and toggling_shuffle actions parsing switched! Basically, the “disallows” operations for the repeat track and shuffle are reversed.

            self._TogglingRepeatTrack = root.get('toggling_repeat_track', None)
            self._TogglingShuffle = root.get('toggling_shuffle', None)

It’s hard to believe this condition hasn’t manifested itself sooner, as that code has not changed since it was put in (2024/01).

Let me get it corrected, and I will push out another release.

Thanks for your patience!

Thank you for your reply, Lucas. I have a separate account for her. I guess you misunderstood my point.


On the picture you can see an overview of some albums. I would like to have just one layer above it, for example an icon for Ninjago and when she clicks on the icon she sees all the albums you see here. Another icon for i.e. Lion King…

1 Like

@jaustin
Update SpotifyPlus integration to latest v1.0.74, and try again please.
Thanks!

Perfect! Thanks for sorting this so quickly.

1 Like

@SeppelM83
Ahhhh, I see.

Unfortunately, there is currently no way to do that.

However, I might be able to create a new user preset type that could open the playlist section and filter the list by specified criteria (e.g. "Folge "). So she would use the user preset section as a starting point, clicking on the “Ninjago Favorites” preset item; it would then open up the playlist favorites, and filter the list by “Folge” (or whatever criteria you specify).

The only limitation is that she has to name her Playlists with a common naming structure so that the filter works correctly. For example, playlist names:
“Folge 01 Playlist (Ninjago)”
“Folge 02 Playlist (Ninjago)”
“Folge 03 Playlist (Ninjago)”
“Folge 04 Playlist”
“Folge 05 Playlist (Ninjago)”

User preset item:
“Ninjago Favorites”, with filter criteria of “(Ninjago)”.

The above would yield “Folge 01-03 and 05” being presented in the Playlist section; Folge 04 would be omitted since it did not contain “(Ninjago)”.

Would something like that be acceptable?

Thanks a lot! I will try it. One more question: is it possible to disable the longpress function to get more details of i.e. a title or playlist?

@SeppelM83
Sorry, disabling long-press is not possible as it’s core functionality of the card.

How do you hide devices on this card please? The SpotifyPlus Integration I’ve managed to hide my devices within Spotify Media sources, but this card still shows all the devices possible despite hiding them within your integration.

Thank you!

1 Like

@jellytotz

The hidden devices will be corrected in the next release of the card.

Thanks for bringing them to my attention.

1 Like

FYI - just released a new version of the SpotifyPlus Card Dashboard

[ 1.0.27 ] - 2024/12/28

  • This release requires the SpotifyPlus Integration v1.0.76+ release; please make sure you update the SpotifyPlus integration prior to updating this SpotifyPlus Card release.
  • Updated logic to correctly account for idle state; the SpotifyPlus integration will go into idle state (instead of staying in paused state) after it detects that the Spotify Web API has dropped the current play state (e.g. the device disconnects from Spotify Connect).
  • Updated Devices section to remove device entries that wish to be hidden as specified by SpotifyPlus integration configuration “hide devices” option.
  • Added ability to play recently played tracks starting from selected track, which will now automatically add the following tracks (up to 50) to the player queue. Prior to this, only the selected track would play and then play would stop. Note that the 50 track limitation is a Spotify Web API limit.
  • Added ability to play player queue tracks starting from selected track, which will now automatically add the following tracks (up to 50) to the player queue. Prior to this, only the selected track would play and then play would stop. Note that the 50 track limitation is a Spotify Web API limit.

Hello Lucas,
first of all I am very impressed by your integration, top work!
I have now noticed that if I listen to “living room” with the playback device and then select “bathroom” the next time, the playback starts again in the “living room” until I press “bathroom” a second time. Is this a known problem, or is there a workaround?
Best regards
Stefan

@Richi
Do you have a default device set in your SpotifyPlus integration configuration options? If so, it will default to that device when turned on.

Hi, no i have not selected a default device. it doesn’t matter which player i switch to, it always plays on the last played device first. however, this only occurs when i restart the player.

@Richi
Please Open a New Issue on GitHub so we can track progress.

Not sure what is going on here, and will have to research it.

When I want to play a playlist I get "could not play media item. validation error: device not found… What could be the problem ?

My God, it’s magnificent.

Is there a way to pick a section to which the card defaults on open? I’m usually headed straight to the user presets

1 Like

@fmon
Thanks. There is no way to do that currently; I will add it to the list of feature requests though. Good idea!

@Faecon
The device not found error is usually caused by a Spotify device being dropped from the Spotify Connect device list due to inactivity. Is is a Chromecast or Amazon Echo device perhaps? If so, then that is the issue. For those devices you must activate them via the Spotify app (e.g. mobile, desktop, web, etc).

I am currently working on a way to re-awaken Chromecast devices (without Spotcast), but am not ready to release it just yet.

No, they are a sonos devices.

when I look at the media_player.spotifyplus_oefenzaal, it is indeed inactive. Is there something wrong in de settings ?