I understand this isn’t an issue with the script but was wondering if anyone can point me in the right direction. As you can see from the attached screenshot, I have created a folder named packages in the same place where my config.yaml file is found yet i’m getting the following error Integration error: packages - Integration 'packages' not found.
Looks like you didn’t place packages: under the homeassistant: key. It now tries to add it as an integration, but it is part of the homeassistant settings
Can you check, and if you are unsure, you can share your configuration.yaml so I can help you
I thought I had done this. Is this not correct?
No, it should be indented.
Add two spaces in front of it.
Ahh of course, Sorry was really obvious once you pointed it out lol. Thank you as always.
Every time I restart, the result is the same…I have tried to put in a call service the yaml code you gave me as node, but it returns me error…probably I am not doing the things in the right way…I will try now to install the new version and see if something will change.
I have installed the new version. But the problem persists. So, it does not resume.
Here the traces, if they can help.
google home resume - Pastebin.com
google home resume helper - Pastebin.com
P.s. in the yaml I see :
speaker_groups:
media_player.huis_groep:
- media_player.keuken_hub
- media_player.slaapkamer_hub
- media_player.pepijn_mini
- media_player.woonkamer_mini
- media_player.zolder_mini_marleen
- media_player.zolder_mini_martijn
- media_player.floris_mini
media_player.boven_groep:
- media_player.pepijn_mini
- media_player.slaapkamer_hub
- media_player.zolder_mini_marleen
- media_player.zolder_mini_martijn
- media_player.floris_mini
media_player.beneden_groep:
- media_player.keuken_hub
- media_player.woonkamer_mini
media_player.zolder_groep:
- media_player.zolder_mini_marleen
- media_player.zolder_mini_martijn
I don’t have groups, so I have deleted all these rows. I hope it is not a problem.
As mentioned at the top of the settings section, all settings can be removed if they don’t apply to your setup
# enter settings for the script here, all settings are optional, you can remove sections if you don't need them
I’ll have a look at the traces
Are the names of de media_player entities in Home Assistant exactly the same as the devices in the Google Home app?
Devices in cast integration:
Devices in Google Home app
These should be named exactly the same. When they are discovered the first time, that will be the name, but if you rename them in Home Assistant, spotcast will not work on those devices anymore
The name in google home is “Ufficio speaker”.
The name in Home assistant is “Ufficio speaker” too.
The entity_id is “media_player.ufficio_milena”
Looks fine, this is the error I see in de trace
"error": "Failed to get device id from Spotify"
That is usually caused by the wrong banner in my experience, but that doesn’t seem to be the case here.
On the spotcast GitHub I see some people facing similar issues: Automations with spotcast start service stopped working · Issue #334 · fondberg/spotcast · GitHub
Spotify not resuming after upadte to the last versions of scripts 
2022-11-26 14:39:14.909 INFO (MainThread) [homeassistant.components.script.google_home_resume_helper] 00 - Google Home Resume - Helper Script: If at step 2: Resume needed?: Resume playing: Spotify?: Executing step Wait until song is playing (timeout: 0:00:10)
2022-11-26 14:39:16.324 ERROR (MainThread) [homeassistant.core] Error executing service: <ServiceCall spotcast.start (c:01GJT2K94M907P79VMW6K885RK): entity_id=media_player.kuchyna, force_playback=True, limit=20, repeat=off, random_song=False, shuffle=False, start_volume=101, offset=0, ignore_fully_played=False>
Trace:
https://dpaste.org/Vjmek
Unfortunately there is nothing I can do here, this is an error caused by the spotcast custom integration. The script performed the service call as it should
What do you mean with “it’s not letting me through to the scripts area”?
If you placed them in scripts.yaml you should be able to delete the old scripts in the user interface
Hi, I’m trying to implement casting my small gate dashboard into nest hub using “Google Cast: Show lovelace view” service. But the automation and script somewhat triggered every time I cast the said dashboard. What I noticed is if the nest hub is playing Spotify, the cast works with no errors but if it is idle, it will fail and only show the cast icon and I get these warning and error logs.
Here’s the traces:
https://www.dpaste.org/NCdwq
https://www.dpaste.org/xxFnr
https://www.dpaste.org/H18SQ
@williever Just to eliminate this has anything to do with the script, could you set the dashboard_cast setting for the script to false
Then the automation will nog trigger the script when you cast a dashboard.
After changing the setting, please reload automations from Developer tools > YAML
Then try casting the dashboard again. Now the script should not get triggered anymore. If you still receive the same errors, it is not related to the script.
However, all 3 traces don’t show any errors, so I’m not sure if there is much I can do at all
It’s working now. Thank you.
So no errors with dasboard_cast: false?
And casting the dashboard works both when the hub was playing and when it’s idle?
@chicknlil25 These screenshots don’t help much unfortunately.
Are you sure you are redirected to scripts.yaml or is the message more in line of this:
That would indicate that it’s NOT located in scripts.yaml
What do you have in your configuration.yaml after script:?
Can you share your entire confirmation.yaml configuration.yaml? If you don’t want to share it publicly you can also send it in a direct message.
Their should be some way how these scripts are included.
