Spotify Lovelace Card

Share your Projects! Dashboards & Frontend
,
141

I was having the same issue as you trying to play a playlist to one of my Echo’s. Turned out I had to tell Alexa to play first then I could select other Playlist ect,

143

Hi, for me everything is in place but when I try to play something from the playlists I get: Failed to call service media_player/play_media

I restarted HA but still nothing. I hear the beep in the chromecast where I select to play to, but the music won’t start.

Tks in adavance

144

I think might be related to the issue that HASS hasn’t updated to use the latest pychromecast yet. See the note on spotcast git page for info

145

Hi,
I would love to leverage this project on my Hassio.
Can I please get some guidance?

  1. Where exactly to I place the code:
  1. Where do I place the project’s files?
  2. Readme say: Add the card to lovelace config
  • where is the lovelace config? I don’t have such a file (sorry for the nob questions)…
146

Tks, that was it! Let’s hope they update the pychromecast component! Magnificent card!!

147

hey!
Weird, can’t find a doc on the built-in editor for lovelace (the UI frontend for HASS) but this thread explains it: How do I add custom cards with the Lovelace UI?

148

I’ve got a family account for Spotify and I’d like to put a drop-down menu on my interface to select different family members and have the selected person’s playlists appear in the list. I’m assuming that the playlists displayed are based on the account connected to the secret configured in the client_id. Is there any way to accomplish what I’m trying to do?

149

Hi! This is not possible with the current functionally. I know of people using different tabs with different accounts which is possible. You can specify the account in the lovelace config for the card

150

Any possibility having the card available in HACS?

151

Hi,
I’ve an issue with this card running on Fully Kiosk Browser, when I click on the authenticate button I get a blank page with
“response_type must be code or token”

it’s running fine on my desktop pc with firefox/chrome

152

I don’t know what a full kiosk browser is…

153

This one, I use it on my home assistant dedicated tablet :grinning:

154

I had to enable the browser address bar.
When I click on the authenticate button an https://accounts.spotify.com/authorize Url is set but it’s not loading automatically, if I select it and manually launch it the spotify card loads correctly.
Without the address bar I couldn’t see this and clicking twice on the authenticate button causes the “response_type must be code or token” error

155

For me the syntax is not clear. I use the homeassistant cloud. On the homassistant page I have a main view “haushaltXXX” and subtabs per room e.g. “Wohnzimmer”. What should be the redirect URL?:

  1. HAcloud/lovelace/haushaltXXX/wohnzimmer
  2. HAcloud/lovelace/default_view/haushaltXXX/wohnzimmer
  3. ‘…’

I tried already a couple of permutations. Always a redirect error. The standard spotify app works seemlessly with the link HAcloud/api/spotify.

Regards,

Volker

156

Hello all,

I am still struggling with the redirecting url. I use the HA cloud and can setup the spotify app via the redirect url HA-cloud/api/spotify.
My lovelace overview has a main card (default the home tab I think) named “haushaltXXX” and subtabs “wohnzimmer”, etc. The redirect link should be then

  1. HA_cloud/haushaltXXX/wohnzimmer
  2. HA_cloud/lovelace/haushaltXXX/wohnzimmer
  3. HA_cloud/lovelace/wohnzimmer
  4. etc.

I tried these and other permutations. All the time I get an redirect URL after I logged on to the spotify account when clicking on activation.

Regards,

Volker

157

Spotify web api requires the browser to be able to to do redirects. This is part of the OATH specification so if the kiosk browser disallows redirects then it won’t work. And clicking it should not be needed. Especially twice which will cause all sorts of state problems

158

The redirect URL must be the same as the URL you see when the spotifycard authenticate button is seen, copy paste this into the dev console and make sure you have the correct client_id set in the card config in lovelace. Try first in an incognito window in chrome to rule out browser caches and stale data.

159

Thank you for the quick answer. I understand now the syntax. It did not solve my problem, but indeed I may have a browser (settings) problem.

160

Yeah, it is common to have plugins that disallow redirects which is a must for OATH

161

I had the same issue with redirect INVALID_CLIENT: Invalid redirect URI
did a little inspection with spotify web API, I have this set to my external HA address for obvious reasons.
I was trying to authenticate when connecting to HA from my internal address, hence the failure in redirection. When I accessed HA from my external address the authenticate button worked fine… But I still can’t get this to work when I access from my internal address, eg. 10.0.0.xx:8123. Is there a fix for this?