12-09-2023 09:25 AM - edited 12-09-2023 07:29 PM
For quite some time, I've had an automation created as a shortcut to listen to a daily podcast in the morning. The automation includes 1 starter ("daily podcast") and one action ([x] Play the latest episode .. [Podcast name]) and had worked without issues for a very long time.
In recent months, my wife and I found that the automation was less reliable, often "picking up where we left off" instead of playing the most recent episode. However for a while it seemed that if the other partner said the keyword it would work correctly. In the past couple of weeks, it just doesn't work at all... We've found ourselves waking too early in annoyance, yelling "hey google stop!" and fumbling for our phones to open the podcast app to cast to the speaker manually rather than using the automation tools that we have paid for...
In the course of troubleshooting, the automation has been deleted, recreated as either a personal routine and a household routine.. sometimes after re-creation it works correctly, other times it doesn't. We know that there are no conflicting routines because when the automation is deleted, the speaker gives us directions and information about a nearby bakery with a similar sounding name.
<frustration continues>: A long time ago, the routine was configured to use Spotify as a podcast app, but after a long time we just decided that the integration was broken and gave up in favor of using Google podcasts assuming that keeping the routine in the same ecosystem would help. This, and other inconsistencies managing lighting and smart plugs in our home over the years has been very frustrating... almost enough to make this long time supporter of Google products jump ship to another provider.<frustration portion ends>
[edit] Obviously written in frustration, but if anyone has tips, they would be appreciated.
12-19-2023 11:57 PM
I have exactly same routine and same issue going for months too. Would like to see a solution to it. Did you found some?
12-23-2023 09:01 AM
No resolution for the automation that I know of.
We did find that starting the podcast using the phrase "play the newest episode of ..." usually works.
Feels like a step backwards to modify the user behavior given all the efforts to enable natural language prompts.
12-23-2023 09:13 AM
nks, that does not foe me well as I am from Slovakia listening to local podcasts and google does not understand well Slovak names of the podcasts :), so it usually will play some random playlist from spotify 🙂
Thats why this routines worked very well for me because when I type the name of the podcast it will start the correct on. When it starts the podcast I can say "play latest episode of this podcast" and there is 50/50 chance it will work. To me it looks like a clear bug and I cant imagine we are the only two experiencing this issue.
01-05-2024 06:06 AM
We have found that issuing a second command "play the newest episode" after Google indicates it is "continuing" seems to work.
Still a kludgy workaround IMO, but it is currently working.
01-05-2024 06:08 AM
will try that, thanks
12-27-2023 11:11 AM
I also have this problem. It's been several months now that my morning podcast "continues" instead of starting the latest episode. Changing the settings and even building a new routine do not work. The latter was suggested by Google Home help. It seems like the "play the latest episode" functionality has just gone away for some unknown reason.
08-28-2024 03:08 PM
I have a similar issue. My morning routine of playing the latest episode of the podcast has worked until about a week ago when it started playing random music after saying it was playing the episode. Since yesterday, it is playing a specific playlist that we never set up or heard of. Asking to play the latest episode of the podcast, triggers that same playlist or random music. I tried to delete the action and add it back in but no luck. Any suggestions?