Can t play XM or local FM radiosays not available

[Maxwell1006]

When I try to listen to XM radio I now get can't find Xm or it is unavailable. I get same with local FM

[iRzapper]

Yep, I have the same problem and constantly get this response from google assistant for any request of SiriusXM:

"Sorry, I can't do that yet", and/or "Voice commands are not available yet for that App".

It's worked fine for the last several years, but no longer. Ridiculous how or why someone at Google try's to make  something better that is not broken, and breaks it in the process.

[Maxwell1006]

Yes finally after talking to them again yesterday it now works today

[iRzapper]

Hello Maxwell1006, 

Can you now play SiriusXM on Nest Audio by requesting through Google Assistant?

Thanks for letting me know, I still can't get any support from either Google directly by phone, not any of the so called "experts" here within this community. 

[Muddi]

Hey everyone,

Thanks for reaching out. Sorry to hear that you're having issues playing SiriusXM radio on your Google Home/Nest devices. To confirm, does it happen to all stations on SiriusXM? Do you have the same issue when using the Google Assistant app on your phone? Are you able to cast SiriusXM to your speakers? Are you able to play music or listen to radio stations from other music and radio services like YouTube Music, Spotify, and TuneIn? Also, what are the troubleshooting steps that you've tried?

@Maxwell1006: I'm glad to know that your issue is now resolved. Could you share some steps that helped you fix the issue?

Looking forward to your response.

Cheers,

Muddi

[iRzapper]

Yes, SiriusXM no longer exists on my system.  Upon any/all requests for anything, the constant answer is: "Voice commands are not available yet for that App".

I reported this in the first post of this string, (see that)

[Princesss]

Hi there,

Chiming in to see if you still need assistance with this. Hope the previous post helped. Let us know if you have additional questions, otherwise we’ll be locking the thread.
 

Best,

Princess

[Muddi]

Hey folks,

Due to inactivity, I'll go ahead and lock this thread in 24 hours. Feel free to start a new thread if you need assistance with your Google speakers and we'd be glad to assist you further.
 

Cheers,

Muddi

[Joseppi]

I noticed this started happening too when the Home app updated itself on my Android phone. The interface is now different and all my routines I had previously setup to stream music from SiriusXM now suddenly say voice commands are not yet available for the app. They were working just fine weeks ago and had no problem streaming music so not sure what Google changed recently but it seems to have broke it. To work around the issue, I've had to create daylong routines to just stream music at random times during the day. I've made a routine to stream channels from SiriusXM every two hours, i.e.: 12pm, 2pm, 4pm, 6pm, etc. The daylong routines have the same exact verbiage and phrasing as my non-daylong routines and the Home speakers recognize the commands just fine and stream music whereas they cannot recognize the non-daylong routine commands.

[iRzapper]

Hi Joseppi,

Yep, my streaming stopped with the latest interface update for Google Home when it came through for me on about 06/03/23, and I still can't play anything from SiriusXm.

With all due respect to your workaround provided, correct me if I'm wrong, it is supposed to be as easy as saying "Hey Google, play channel (whatever number) from SiriusXM" and it should play that channel, instantly.....as it did for the last several years.  No workarounds, not hassle, just a simple request, after all they sold us this crappy Nest Audio system as a "smart speaker(s) system".  As of today, still no fix or solution to this problem from Google tech support or the community "experts" here.  (I have one hopeful note at the end of this post)

I don't understand the logic of trying to fix something that isn't broken, just goes to show you why some Google people would never get jobs at an Apple type of company, two completely different mindsets.  One says "it's working great as is, let's see if we can break it for our paying customers", and the later simply improves their product without breaking it.

I agree with you and what you said in another post, since Google lost the patent infringement lawsuit with Sonos and had to payup approx $32.5 million, updates and support at Google has sucked. 

One bright note, finally, I got through over the phone to someone at Google who seems conscientious enough and wants to solve this problem.  That was yesterday (Tues), and he said give him until late Thursday or early Friday to work with their "specialists" to come up with a fix.  Let's see what comes of that.

I'll report back after I get that update.  (I'm told hope is never a plan) If Google can't fix this, it may be time to burn these (7) dimwitted Nest Audio speakers.

[iRzapper]

Update: (06/09/2023)

Hi Joseppi,

I told you I'd follow up after I heard back from the Google Tech I got in touch with on the phone last Tuesday.

He turned out to be useless, failed to follow through (as predictable with Google Support lately), and for that matter, the same with this community's support "specialists" and "experts" .  They'll ask you all sorts of questions, when provided, they never follow-up.  Unreliable people.

[Joseppi]

Thanks for the follow up iRzapper. I've learned to just wait these things out and they usually resolve themselves on their own, but only after a couple days or weeks.

[iRzapper]

UPDATE on 06/16/2023, regarding the problem with Google Assistant not Playing any channels from SiriusXM on my Nest Audio Speakers after the most recent Google Home Update:

I changed the Google Assistant "voice setting" from English (Australian), to English (United States), now I can request of Google Assistant to play any/all channels from SiriusXM on my updated Google Home structure, and all the music plays just fine, just like it did before the most recent Google Home update I received on 06/03/2023

After two weeks with this problem, this fix was provided by someone I was finally able to locate at Google who knew what he was doing, made the time to help, and went out of his way to help me solve the problem.  His name is "Albert", he saved the day when nobody else at Google Tech Support and/or within this Community could.

Thank you Albert.

[Muddi]

Hello iRzapper,

Thanks for updating the Community forum of your resolution — it's a big help! If you have any updates or just a discussion topic, feel free to start a new thread in the community. 

@Joseppi: How was your device?

Cheers,

Muddi