No longer able to stream music directly to Chromecast Audio or use it as a Default music speaker

[RetiredBy55]

Hello Community,

Up until a few days ago, I've been able to stream Spotify to my Chromecast Audio. This device has been working flawlessly but now something has changed.

Here's my configuration: Google Nest Audio (obtained as a replacement when Google Home Audio devices were bricked), 4 Google Home Minis and 1 Google Chromecast Audio. All devices are on the same mesh WiFi network and are reporting as connected. They're all running the latest cast firmware. They all respond to verbal commands correctly (not the Chromecast as it has no input.) I can stream music to them directly via a linked premium Spotify account. While streaming, I am able to transfer the audio from once device to another via the UI in Spotify. 

The output Chromecast Audio, which is named "Stereo", is connected to my home stereo and has been set as the Default music speaker for the Google Nest Audio. Until a few days ago, I've been able to invoke the Nest as follows: "Hey Google, play (insert request here)" to which it responds "Alright. Playing (request) on stereo." The result is the music request plays on the stereo.

Now when I attempt the same request, I get the same response but nothing happens. No music and no indication of music playing when looking at either the Nest or the Chromecast via the Google Home app on my Android device. If I attempt to force music to the Chromecast with "Hey Google, play (request) on stereo", the response is "Alright. Playing (request) on stereo" but nothing plays.

I've rebooted all the Google devices, reset the Chromecast to factory, and reset the network. Still no music.

What have I missed? Any suggestions? Thanks in advance for any help you might offer.

[Justmurdoch]

The fact that services such as SiriusXM and YouTube Music continue to play as before (voice command —> speaker —> CCA) and that the WiiM streamer is experiencing the exact same issue as the CCA is an indication that any loss of support for the latter device is not to blame. It is clear that the issue at bar is due to a recent firmware upgrade to Google speakers which is not playing nicely with the Google cast technology seeing as multiple (but not all) music services have been affected.

[RetiredBy55]

Hello Daniel moralesvincente and Moderator,

Any updates on testing or firmware release dates to share? While the workaround that @DeaneG  found is useful, I think you'll find that many here concur this is not a permanent solution and as @Snap indicated we're hoping Google isn't dropping support for the CCA.

[Thunder3dan]

No sure if fix a got rolled out but this has started working again for me. 

[DeaneG]

Still broken for us.

[Justmurdoch]

Still broken for me as well. Interestingly, on the Google Home app, under the default speaker options for the Nest Hub, I have a new device just above the CCA which is referred to as a “Nest Hub” device. 

[Justmurdoch]

Is your setup from a Google Nest Hub/speaker to the Chromecast Audio?

[DeaneG]

Yes, that's correct. It's still not working.

[Thunder3dan]

I tried on multiple devices.  Google home mini to CCA started working today.  Google Nest Hub display to CCA started working today.  Lenovo 8" Display to CCA started working today.  

[DeaneG]

That's great. I'll check mine again later.

[RetiredBy55]

No changes here. Neither Nest Audio -> CCA nor Mini-> CCA work. Some things actually seem worse. For example, I can start Spotify on a Mini and then move it to the CCA but, once there, I cannot pause or control volume from the Mini.  I swear this was working previously.  Control from Google Home works though.

I checked cast firmware and I'm up-to-date with what is published: 3.75.456944 (was 3.74.444798 back on 2/12/2025) on the Nest and Minis and 1.56.281627 (no change since 2/12/2025) on the CCA.  Anyone seeing anything different? Maybe a phased rollout?

[brsgraves]

We've been busy at home and I haven't had time to verify working or not working or fw versions.  I'll spend some time tonight taking a look and send an update.

[brsgraves]

Still the same issue as before.  Spotify still not working with CCA as default speaker.  FW has not changed from when the issue surfaced.

[Christoforadams]

Still not working here from nest hub or google home mini to CCA.

[MarcusP]

Still not working for my nest mini and WIIM

[Snap]

Still not working for me either

[zeeroof]

Same situation here

cannot play on CCA set up as default audio output of a google mini while asking the google mini to play 

Cannot play on CCA while asking the google mini to play on CCA

cannot play on CCA group while invoking speaker group from google mini

- services not working  : Spotify , Radio France 

Working

- the above while invoking  YouTube music 

- invoking « Spotify & on google nest audio « while taking to google mini 

all CCA are with firmware 1.56.281627

tried from google mini v1 3.75.456944 , and google nest audio  3.75.456944 (456944)

[Christoforadams]

CCA still broken. Fix this please.

[Christoforadams]

Bumping daily until we get a solution.

[Justmurdoch]

I was planning on fully committing to the Google ecosystem and purchasing the Nest Doorbell and Pixel Tablet, however, and given the response of Google to this ongoing issue, or lack thereof, will wait to see Apple’s smart home tablet before making a decision. Google just seems to be repeatedly shooting themselves in the foot as of late and not caring about the end user.

[DeaneG]

It's only in the past four weeks. Both Google and Apple take months to fix things like this.

[Christoforadams]

The last time this happened it took about 4 weeks. 

[Christoforadams]

Daily Bump until addressed.

[RetiredBy55]

We're just about at the 4 week mark. 

[lerroybrown]

Having same issue with my 4 CCA's 

I tried factory reset hoping might reset firmware but no luck

please fix  🙂

[Christoforadams]

Daily bump. Still no comment from tech support.

[RetiredBy55]

Crickets.

[Hshcast]

Even that doesn't come out of my CCA 😉

[MarcusP]

I'm also very disappointed. Can this defect be escalated? There is no communication. We're being ignored. 

[Justmurdoch]

@DeaneG To my point. This silence would not occur with Apple. The plethora of contributions to this thread have basically done the bulk of the work for Google and yet there is no forecasted fix let alone a status update.

[DeaneG]

Not even any acknowledgement of a problem. But does Google monitor this forum? Maybe it's not the right way to tell Google about a bug.

[RetiredBy55]

Maybe we're not asking right. Hey Google - fix my Chromecast.

[RetiredBy55]

I had a chat with a Senior Technical Support representative from Google today. A consultation to a higher / engineering team is being initiated. I'm to expect an email back in 24 - 48 hours. 

Stay tuned.

[DeaneG]

Thank you!

[Christoforadams]

Daily bump

[AndrewLP]

Keep up. Thank you. This needs to be fixed

[AndrewLP]

I am happy I found this forum. I have 2 places each with mini nests all over both houses talking to all my Chromecast Audio devices. All of a sudden none are working at either home. I have done all the usual attempts to fix. It's clear I have the same issue as everyone else here. Google please fix. 

[4thFallenHorse]

Just lost a day to trying to resolve, before seeing this forum. At least I can take comfort in it not being just my set up.

hopefully a fix comes soon.

[Christoforadams]

Daily bumpo. Please fix google?

[RetiredBy55]

A case number has been assigned.

[phletixh0n]

Hello, adding a variation to the topic.

CCA plugged in directly to AV-receiver and connected to the wifi network. Router menu on http://192.168.0.1/ explicitly shows the CCA as connected to the wifi network.

Android phone and MacBook Pro also confirmed as connected to the same wifi network.

CCA shows up as online destination in several apps (Google Home, YouTube Music, local radio apps, etc, etc).

When clicking on the CCA as the destination to cast to, nothing happens.

Was working fine this morning even.

Currently nothing gets thru to the CCA after multiple reboots of all devices and network even though it still shows as a valid destination...