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

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.

does someone know how to completely remove spotcast settings…

I keep getting invalid client after I’ve added integration…

INVALID_CLIENT: Invalid client

I’m sure it’s because I used the sp_key instead of oauth client when I was doing the setup… I’ve completely deleted the HACS integration… and I even looked here: .storage/core.config_entries and there are no entries for it…

I’m playing with 5.0.0.0

I’ve also tried to ovewrite the page with the correct client_id… and it works but the call back fails with 500 Internal Server Error - Server got itself in trouble and I’m pretty sure it’s because the link proably is encoding the secret on the outgoing request…

anyways, would be lovely if someone knew how to reset the integration.

Are you having the 500 error when trying to go into configure?

As soon as I try to add the integration here, it goes straight to the website…

https://accounts.spotify.com/authorize?

Wait a minute you’re the one doing the PRs! Cool! lol

oh ok, I though you might have stumble on one of my mistake with the option flow. If your issue is with the OAuth credentials, when you are in the “Devices & Integration” you can click on the 3 dots in the top right corner and select “Application Credentials” you should be able to remove the saved credentials.

Also I just pushed build 4, I would suggest to install it before trying to reinstall. Thanks for trying out the beta.

There should be an entry for Spotcast that you can delete. If you need further help, please ask

Wait a minute you’re the one doing the PRs! Cool! lol

I was about to post a message about the beta release and saw your post, wasn’t about to left you hanging while I make my announcement

Hi Everyone,

I wanted to take the time to announce that I am releasing today the first build of Spotcast V5. I have been hard at work in the last 3 months doing a full rewrite of the Spotcast integration to modernise it and improve it as much as possible. This new version is bringing a lot of improvements in the way Spotcast works, while also bringing this integration to the modern Home Assistant with web interface configuration and ability to re-authenticate without reboot.

I’m at a point where I won’t be able to find improvements or bugs anymore and need the help of the community to stress test the heck out of it. So for any one interested, you can download the latest build in pre-release in HACS (at the moment of writing, we are at 5.0.0-b4.

Some of the improvements in the current version of the beta are:

  • a very significant improvement in start playback delay (from 15-2- to 1-2 seconds from personal experience)
  • Rewrite of the core system with its own OAuth manager
  • Separation of Spotcast functionalities is separate services
  • Rebuild of the websocket API
  • Creation of Spotify connect device media_players
  • Creation of Service Sensors
  • Creation of a configuration flow to enable configuring Spotcast from the UI
  • Creation of an option flow to permit modifying options without restarting Home Assistant
  • Creation of a reauth process for when credentials expires

Also in the backlog, we have a new logo to go with the release pending approval from the ha-brand repository.

If anyone is interested, please download the beta, try it, try to break it and send me feedback.

Hope everyone will enjoy this new step forwards for Spotcast.

4 Likes

Is the new beta of spotcast working only with premium users?

We talked about it in DM, but I want to make the information generally available to everyone. This is a regression bug. I’ll be working on fixing this one after work. I also created a free account to also test for non premium features from now own to ensure I don’t integrate more bug like this one going forward

1 Like

Hi, I’m trying the V5, I’m not an expert user, but I’m happy to try it. The thing I need most is the ability to see my google home and my chromecast to be able to send music directly from Home assistant.
from Github I see this function:
spotcast.transfer_playback
will this work to transfer music from a google home device to a google home group? I am looking for a solution to automate music from a device to the group because google home often does not do this function

Yes that will work. Chromecast groups are their own media_players in Home Assistant, simply select it as the target when using the transfer playback service

1 Like

thanks,
I tried from developer tools, actions to insert this:

action: spotcast.transfer_playback
data:
  media_player:
    entity_id: media_player.gruppo_cucina
  account: XXXXXXXXXXXXXXXXXX

but it doesn’t work
answer spotcast.transfer_playback Unknown error
I tried both specifying the account and not specifying it
I apologize for writing here, I don’t want to go too off topic, but I have no idea where to ask this

what version are you currently on? There was a bug in the transfer_playback service I fixed this morning. You need to make sure to be on 5.0.0-b5. If you still have the same error with this build, please open a ticket in the repo so I can track it.

1 Like

I had .4 now .5 I will continue to test and update you on github then. Thanks

ok then the issue you had was normal. Should be fixed with build 5

1 Like

spotcast.play_media doesn’t work for me either so I checked and it doesn’t work with any google home, only with bose and other spotify connect devices it works. Moto probably I’m doing something wrong, I’ll leave that to the more experienced. The beauty of spotcast was being able to wake up google home, I think it’s still possible, it’s probably my problem.

yeah very strange as it is working for me at the moment, any errors in your logs

Yes I find this, but I don’t know how to evaluate these errors, in fact I don’t want to clog up the topic, but I wasn’t sure if it was correct to report it on github

Registratore: homeassistant.components.websocket_api.http.connection
Fonte: components/websocket_api/connection.py:315
Integrazione: Home Assistant WebSocket API (documentazione, problemi)
Prima occorrenza: 16:07:22 (6 occorrenze)
Ultima registrazione: 16:35:48

[140586207973808] Error handling message: https://api.spotify.com/v1/me/player/play?device_id=4f41d83fac0c755864aaa9f29c8c22f9: Device not found (home_assistant_error) Diegocampy from 195.103.18.226 (Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Safari/537.36)
[140586207973808] Error handling message: https://api.spotify.com/v1/me/player/play?device_id=3d3e9b5ca32bcbedadf89e0715c81c4b: Device not found (home_assistant_error) Diegocampy from 195.103.18.226 (Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Safari/537.36)
[140586288761008] Error handling message: https://api.spotify.com/v1/me/player/play?device_id=4f41d83fac0c755864aaa9f29c8c22f9: Device not found (home_assistant_error) Diegocampy from 195.103.18.226 (Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Safari/537.36)

if you have any problem with spotcast, please open a ticket, worst case I’ll tell you its not spotcast fault and where you should be looking for your issue

when filling out the bug request, can you make sure to generate a debug log (instruction in the ticket form) and upload the information?

Thanks for this Felix.
I’m currently testing v5.0.0-b9 and all seems good :slight_smile:
Quick question, using spotcast.play_media, is it possible to resume Spotify from where it previously was ie. not specifying a specific URI?
Thank you

1 Like