This sounds very much like the problem I've been having...
I have several stations, but four primary stations that I use often. I've gone through a few rounds of changing their names so that Google/Gemini can recognize them, originally because no LLM AI was going to resolve "thojazzmic" and then later because Google/Gemini/Pandora seemed to have seemingly arbitrary problems resolving even more straightforward names.
But, especially since the recent migration to Gemini, the state has been more or less consistent:
I don't want to keep experimenting with changing their names, as (1) the current names are all words that should be easily recognizable, (2) Gemini does seem to be resolving the names, and (3) I have no reason to believe that that will fix anything at this point.
Ref. https://x.com/Thogek/status/2101734740030284055
Interestingly, I have a few Amazon Alexa/Echo devices which do not exhibit this problem at all and work consistently just fine with my Pandora station names. But, in general, I much prefer Google/Gemini's overall environment...
Hi @Thogek
Thanks for sharing these details, and I’m sorry for the trouble you’ve been having playing your stations through Google Home and Gemini.
The information you provided, including the stations affected and your experience with Gemini is very helpful.
I've passed your experience along to our engineering team for further investigation. Thanks again for taking the time to share such a detailed report and for your patience while our team takes a closer look.
Thanks, @TannerPandora.
I can verify that nothing has changed so far. Google Home/Gemini still plays Wondrous Variety on command without issue, but not the other three: sometimes the names are simply not recognized, other times they are recognized but "that can't be played right now".
Meanwhile, Alexa on an Echo Dot plays all four on command just fine.
I'd love to hear about any progress on this, whether the problem appears to be with Gemini, Pandora, or somewhere in between, etc.
Hi @Thogek
Thanks for following up.
I checked in and this issue is still being reviewed by our internal teams. I haven’t received any additional updates to share at this time, and I don’t have a timeline for when a resolution may be available.
I’ll continue to keep an eye on this and will share any new information here as soon as I receive an update.
Thanks again for your patience while this is being reviewed.
I have tracked this issue since 2024. How long have they been reviewing it?