Spotcast - custom component to start playback on an idle chromecast device

Share your Projects! Custom Integrations
998

It works too with Google Devices?

999

@cediqqu
Not for sure on that, as I do not own any Google devices.

You would just have to try it.

1000 
action: spotcast.start
data:
  limit: 20
  force_playback: false
  random_song: false
  repeat: "off"
  shuffle: false
  offset: 0
  ignore_fully_played: false
  entity_id: media_player.ruimte1
  uri: spotify:playlist:37i9dQZF1DWWn9pcJIAKFl?si=d64afee1ee1347c7
  country: BE
  start_volume: 40

gives me “Failed to perform the action spotcast.start. Could not find spotify media player.” What am I doing wrong ?

1001

I will try :wink: thanks for your work!!

1002

I am not sure if I am missing something. But I have a few buttons on my dashboard to start playing music on specific speakers or speaker groups (Chromecast).
Using this:

    tap_action:
      action: call-service
      service: spotcast.start
      data:
        entity_id: media_player.sovrum
        category: Chill
        country: SE
        random_song: true
        shuffle: true
        repeat: track
      target: {}

But for some reason it does not start playing, I can hear it connecting to the Chromecast audio device, but it is not sending a play command. So it does seem to send the correct playlist to the speaker but not playing it?

1003

Spotcast Issue: One Google Home Device Stopped Working

Hey everyone, I’m having a peculiar issue with Spotcast in Home Assistant and could use some community insights. Here’s the situation:

The Problem

  • I have two Google Home devices, but suddenly one of them stopped working with Spotcast.
  • The non-working device still functions fine when controlled directly through the Spotify app.

Symptoms

  1. When trying to use Spotcast with the problematic device, I get: “HomeAssistantError: Failed to get device id from Spotify”
  2. The device isn’t visible in Spotify API responses through Home Assistant, but it shows up in my Spotify app.
  3. If I start playback on the device via the Spotify app, it temporarily becomes visible in Spotify API, but using its ID in the service call after the speaker goes off it still results in a error.

What I’ve Tried

  • Renewed my sp_dc and sp_key values and restarted HA
  • Tried various service call configurations (entity_id, device_name, device_id)

The Weird Part

The other Google Home device works perfectly fine with Spotcast with the same service call. Nothing changed in my setup when this issue started.

Has anyone encountered something similar or have ideas on what might be causing this? Any troubleshooting steps I might have missed?

Thanks in advance for any help!

Here is the Bug I opened: Only one Google Home device Stopped working · Issue #459 · fondberg/spotcast · GitHub

1004

I have set up Spotcast but I have an issue that the Spotify Integration does not display my Chromecast Devices only two standalone TV connections and Web Player (Chrome) .

I have looked in Spotify and there are two TV devices and a heading called “Google Cast Devices” that when I drill down on contain all of my devices in the Google Cast integration are present/

It just seems that these devices cannot be seen as they are at the second level not the primary level.

Any help in resolving would be appreciated.

1005

UPDATE : Created and checked the [sensor.chromecast_devices] and the Chromecast devices are present, but reloading the Spotify / SpotifyPlus Integrations does not make the devices appear in the Source options of either integration.

1006

OK, got the Spotify card working now with Spotcast and using that I can select a GoogleCast Device that then enables the device in Spotify / Spotcast integrations for a limited period of time.

Can anyone advise what that period of time is ? Also if there is anyway I can run a cycling Automation to keep the cast devices visible to the integration ? It’s not a pretty solution but it could help in enabling the additional functionality in the SpotifyPlus integration.