Your last edit sounds good. This is what i’m looking for for playing my favorite spotify playlists.
i have spotcast and use now the custom spotify card but i’m not happy with the layout of it.
can you share your config how you have setup the spotify playlists instead of the radio streams?
Basically you just need to edit the service call used in the script and the service data, so it will envoke spotcast and the Spotify URI instead of radio streams.
Just replace the names accordingly (also in the other places) to match everything and then create an entities card with Lovelace. I don’t use the script as an entity, but have created a button with button-card and linked that to the script. i didn’t like the script button (too small and on the side).
Thank you very much. That is easier than i thought.
The entities card in combination of de mini-media-player-card in en vertical-stack-card must be a very nice spotify card.
thank you.
Yes, that is what I have. Entities, with button card below it and mini media player (that only shows when playing). Wrap the whole stack inside a popup card using browsermod and you’re really cooking ;)!
The condition looks at the state of the entity and only shows it only when the condition is met. You can also use the multiple state_not variables if you want it to show not only when playing, but also when paused. If you chang the conditions to state_not: off it basically says show it always except when state is not. You can add multiple state_not variables.
In this case I advise you to not use state: playing but use state_not: off, otherwise you will only see the card when playing and it will disappear when you pause it I advise to read the documents I linked about the conditional card if you have any issues.
Invalid config for [group]: [Radio] is an invalid option for [group]. Check: group->group->group->Radio. (See /config/configuration.yaml, line 12).
Invalid config for [group]: [Residence Radio] is an invalid option for [group]. Check: group->group->group->Residence Radio. (See /config/configuration.yaml, line 12).
change the group entity_id to remove the capital 'R’s and change the spare for an underscore… plus the indentation was off. You don’t use the domain when in a domain named yaml file either
# group: <----since you are saving this in groups.yaml , you can't then use the domain heading group: (it's not required or allowed)
residence_radio:
name: Residentie Radio
entities:
- input_select.radio_station
- input_select.chromecast_radio
- script.radio538
- input_slider.volume_radio
@Bob_NL Thanks for your guide. I’ve set up everything but now I don’t know wich card shall I use to show the first picture of your post? I mean the main one with selectors you put under the Frontend: section. Is there a specific card to view the groups in Lovecale?
@Knot83 I created this topic long before lovelace excisted. I’m sure there are plenty of way better options than the oldschool method I’m using (to everybody: please feel free to share awesome lovelace cards in combination with the radio in this topic ).
However, this is my lovelace config:
entities:
- input_select.radio_station
- input_select.chromecast_radio
- action_name: Play Radio
entity: script.radio538
- entity: input_number.volume_master
- sensor.radiovolume
- input_text.stream_url
- action_name: Play stream
entity: script.play_stream
show_header_toggle: false
title: Residentie Radio
type: entities
Thanks for sharing (y). I missed that post. Will look into it.
Same here, I have a killer alarm clock (if I may say so myself) including lullabies, wakeup light and of course the radio which I use every day but it also became a very complex project. I did not find the time and desire to untangle the whole thing and make it usable for everyone who is interested.
I tied the Spotify playlist picker inside a vertical stack-in-card with conditional mini media player cards. If more speakers are active (with other streams) I can swipe between the mini media player cards and control the speakers. I also incorporated swiper card. Looks really clean
Came across this test of yours after I could not get my Google Home Minis to play anything. When I try your test in the dev-services panel or through any other method my speaker plays a tone which I presume to be an error tone. (It’s not the usual “Casting started tone”.)
Any idea what may be happening?
Thank you.
I’ve never had an error tone played before that I can think of. Have you been able to cast to the Home mini from HA before? If this is your first attempt I’d suggest checking the config, but that stream link should work…