-
Yes they do. I had to do a refresh and then they appeared.
-
Yes, but also only the ones I´m currently streaming to.
-
You are right. Spotcast is required as well.
Regards
René
1 Like
@rene-zuch
Thanks Rene. From the SpotifyPlus Card Device Browser, can you do a click and hold on one of the Chromecast devices to display the details? If you could take a screen capture and replay back with it that would be great.
It will look something like this (this is for one of my Bose SoundTouch 10 devices):
I’m curious to see what some of the details are for Chromecast devices.
Thanks!
@rene-zuch
Thank you, that is really helpful. It appears that the Chromecast devices are not registered with Spotify Connect ZeroConf, as proven by the IP address of localhost and the IsDynamicDevice = true.
Supporting Chromecast will require similar processing as I do for Sonos devices, which will be a big effort to implement and support. This is not something I would attempt without having a device to test with.
@thlucas I ask you because you have always been kind in helping me. You are doing a great job, and for months I have switched to using Spotify Plus as well as Soundtouch Plus. Now I am confused again. I see updates on Spotcast, and on the original Spotify applications. I have generated many duplicate things, I wonder what is the best solution for me. In the end I am simply interested in being able to start music from spotify on google home, for a lullaby routine for my daughter, everything else I do by voice. I think that only spotcast allows me this, right? Sorry for the trivial question and outside of your automation, but if I understood correctly, this possibility is not on spotify plus, in fact after deleting spotcast, I could no longer obtain this. Correct?
For the same reason, even your beautiful new spotify card, does not show me the google home devices, but only those associated with spotify connect, right?
1 Like
@Diegocampy Not a problem, happy to help.
Chromecast devices are currently not fully supported by the SpotifyPlus integration. You can perform player functions (e.g. pause, resume, next track, etc) if the device is the currently active player, but you can’t wake up a device or initiate play of tracks / context.
This has been one of the most requested features, and I would love to provide support for these devices. The problem is that I do not have any Chromecast devices to test with, so I am not able to develop a solution.
If it were me, I would continue using the SpotCast features. I saw a post on the community forum about SpotCast V5 that might be of interest to you as well; it sounds like it’s a new version of SpotCast, though I am not familiar enough with SpotCast to know what it adds or replaces.
Hope it helps!
1 Like
yes i saw it and i’m trying it. Now i remember how i got to spotify plus, it was the only way to continue playing spotify from my account on my bose soundtouch.
For my needs i will have to continue using spotify plus, spotcast, and soundtouch plus 
maybe i will be able to abandon the official version of spotify one day, just in case i leave it there now
1 Like
When i use Get Current Users Profile, i always get Login ID as my username as string. It is not canonical (like 31l77y75hfnhk79f7gk6jkk878mg) as you mentioned. It is only the username without the @ mail address part. Should i use this username as my LoginID?
@febalci
Note that for some Spotify accounts, the LoginId and Username values are the same. Not sure why that is, as it’s a Spotify internals kind of thing.
The LoginId value can easily be found using the Spotify Developer Web portal, using the Get Current Users profile service. Click on the Try It button, then find the id response value.
The id response value will be the LoginId value.
2 Likes
@thlucas as mentioned earlier in this thread, I have an entirely Chromecast-based ecosystem. I have been looking for this type integration and dashboard panel for Spotify since I started using Home Assistant 4+ years ago. You noted that you do not have any Chromecast devices, however, depending on your model, the Bose Soundtouch may already support it: Chromecast Built-in FAQ | Bose. If you do work on Chromecast support at any point, I’d be glad to help with testing. Thanks, again, for developing this amazing and much needed integration.
1 Like
Hello everyone, joining this thread as I’m currently struggling with my Spotify Connect integration.
But it’s not clear to me if Spotify Plus integration can solve my issue. I need advice from you, the awesome community
I’m running my HA on a RPI, with a Jack cable connected to my sound system. My goal is to see my HA instance/RPI as a Spotify Connect device. Thus, it would allow me to play music from Spotify Connect directly on my sound system.
Is it something doable with Spotify Plus?
Thanks a lot for your help
@rml
Chromecast is only supported on the newer Bose Smart products; it is not supported on the older SoundTouch line of products, which is what I have.
Thanks for the info though-good stuff to know.
@Thompop
Check out the SpotifyConnect AddOn, which does exactly what you are asking for.
That should make your RPi show as a Spotify Connect device, which can be controlled by SpotifyPlus, HA Spotify, or even the Spotify mobile / desktop apps.
Hope it helps!
1 Like
Sorry folks, but I have some disappointing news from the Spotify Developer API camp. It turns out Spotify has decided to remove the following functionality without any sort of warning or grace period. This was announced on the Spotify Developer Forum Blog on Thursday November 27th 2024 (US Thanksgiving holiday - definitely nothing worth giving thanks for IMHO!).
The Spotify Web API will no longer be able to access or use the following endpoints and functionality in third-party applications (SpotifyPlus being one of them):
- Related Artists
- Recommendations
- Audio Features
- Audio Analysis
- Get Featured Playlists
- Get Category’s Playlists
- 30-second preview URLs, in multi-get responses (
SimpleTrackobject) - Algorithmic and Spotify-owned editorial playlists
What does this mean for me?
What these changes mean for the SpotifyPlus Integration and SpotifyPlus Card Dashboard users is that the corresponding functions that access the above features will no longer work, and in most case will return an error message.
What can I do about this?
You can make your voice and opinion be heard by posting a reply on the Spotify Community Forum. Let them know that this change is not acceptable and how disappointed you are. Please be respectful in the process; scream and shout with your internal voice if you have to (like I did). 
Can these functions be replaced with equivalent functionality?
I currently have no plans to try an re-implement the affected functionality, as the deprecated Spotify Web API functions were the only way to retrieve the information. It’s proprietary data, and if they don’t want to share then that’s their prerogative.
In Summary
Spotify is still a great platform for music streaming, but they lost a lot of respect from me today as a Spotify Champion and user of their Spotify Web API. As a developer of numerous API’s myself, it’s unheard of to simply shut off a feature or endpoint without giving some sort of notice or grace period; and we definitely don’t make major changes like this over a major holiday! IMHO, they totally dropped the ball on this one, not to mention dropped the hammer on numerous developers!
Just thought that you would want to know, and sorry to be the bearer of bad news. I will cross-post this in the SpotifyPlus Card community forum post as well.
5 Likes
FYI - just released a new version of the SpotifyPlus integration
Be sure to check out the SpotifyPlus Card Dashboard as well.
[ 1.0.67 ] - 2024/12/02
- Updated underlying
spotifywebapiPythonpackage requirement to version 1.0.22. - The above
spotifywebapiPythonpackage will now return an exception due to the functions being deprecated by the Spotify development team. More information can be found on the Spotify Developer Forum Blog post that was conveyed on November 27, 2024. The following methods will now raise aSpotifyApiErrorexception due to the Spotify development team changes:GetArtistRelatedArtists,GetTrackRecommendations,GetTrackAudioFeatures,GetFeaturedPlaylists,GetCategoryPlaylists,GetGenres. The following properties were also marked as deprecated for the same reason:TrackSimplified.PreviewUrl. - Due to the above changes made by Spotify, any Algorithmic and Spotify-owned editorial playlists are no longer accessible or have more limited functionality. This means that you can no longer obtain details via the
SpotifyClient.GetPlaylistandSpotifyClient.GetPlaylistItemsmethods for Spotify-owned / generated content (e.g. “Made For You”, etc). A404 - Not Founderror will be returned when trying to retrieve information for these playlist types.
3 Likes
Great integration!
I have a question about the media_player entity state Off, why does it exist?
In the Official spotify integration it always stays in Idle, which is good because if the spotify is triggered by other device (like an alexa) the entity will update itself, in the spotify plus after the music have started, I need to turn on the media_player manually
Is there a way to keep it always on, or go to idle of not playing?
2 Likes
@thlucas that’s basically the thing I asked a few posts ago, when you turn it on it reset the connected device/source (sonos or others) and queue, forcing the user to start again the playlist/track/whatever was playing. Keeping it idle might solve this.
Always trying to find the best solution for everything, I am forced to have 2 active integrations, spotify and spotifyplus.
Is only the official one able to recognize if it is running? Is there a chance that this will be fixed in the future?
It is not essential because I can do it with official Spotify, but if everything that the official one does could be done with plus, I would avoid having two
@Diegocampy I have disable the official Spotify, and use only the Spotify Plus ( I think that’s the way it meant to be used). I also use the Spotify API on Node Red to create a sensor to use in my dashboard footer Spotify Plus integration is a bit in late to refresh but it runs good.
1 Like
@rafareusch @Diegocampy @Sofa_Surfer
The turn_on / turn_off services were implemented to provide a more compatible media player experience for the Spotify Player. It also executes some extra logic that is required for Sonos device support, as they are considered restricted devices and cannot be controlled directly by the Spotify Web API functions.
The following extra functionality is also provided by these 2 services.
turn_on (state not equal ‘off’)
-
executes the Turn On Script option, if configured.
This option allows you to specify a script that will be executed when a
turn_onservice request is made to power on the integration. The script can be used to prepare the audio output device(s) (e.g. speaker, AV receiver, etc) for playing Spotify Player content. For example, you could have a script that performs the following actions:- turn on AV receiver.
- switch AV receiver input to AUX 1.
- issue a
media_player.select_sourceservice call to activate a source on the device (e.g. force the device to be re-discovered by the Spotify Web API as an available device). - issue a call to service
spotifyplus.player_transfer_playbackto transfer Spotify Player playback to the device.
The script is executed synchronously, which means the integration will wait until the script ends before proceeding with other power-related events. Any changes to the script take effect immediately - you do not need to restart HA for script changes.
The script configuration option is optional - you don’t have to select a script. If your device or audio equipment does not require any preparation steps to play output then leave the option blank.
-
gets the current Spotify Connect player state. This is required, in case the state has changed since it was last powered off.
-
updates the source list (Spotify Connect devices cache).
-
try to automatically select a source for play.
- if Spotify player is not found and a default Spotify connect device is configured, then select it;
- otherwise, select the last active device source;
- otherwise, select the currently active Spotify Connect device source;
- otherwise, we cannot automatically select a source!
- activates the selected source.
-
check if playing content is paused; if so, then resumes play.
turn_off (state equal ‘off’)
-
saves the currently active source.
-
pauses the Spotify Player.
-
executes the Turn Off Script option, if configured.
This option allows you to specify a script that will be executed when a
turn_offservice request is made to power off the integration. The script can be used to shut down the audio output device(s) (e.g. speaker, AV receiver, etc) after playing Spotify Connect Player content. For example, you could have a script that performs the following actions:- turn off AV receiver.
- turn off speaker device.
The script is executed syncronously, which means the integration will wait until the script ends before proceeding with other power-related events. Any changes to the script take effect immediately - you do not need to restart HA for script changes.
The script configuration option is optional - you don’t have to select a script. If your audio equipment does not require any shutdown steps after playing output then leave the option blank.