a month ago
Hi, I'm trying to cast my chromecast's audio through two Nest Wifi that are grouped in the google home app. I run into two separate issues. The first is that chromecast never maintains the connection to the bluetooth speakers, it constantly switches back to regular TV audio if I turn the chromecast off and turn it back on. I want it to always output to the Nest Wifi speakers.
Second, the volume control seems to do almost nothing until you get down to the very smallest volume numbers. eg theres almost no change in audio volume from 20 all the way down to ~4 or 3, then it slowly gets quieter until its muted at audio level 0. So audio levels 5, 10, 15, 20 all sound exactly the same.
When the chromecast is only outputting to the regular TV speakers (no bluetooth), the audio ranges are perfectly fine.
Whats going on?
4 weeks ago - last edited 3 weeks ago
Hi moj85,
Thanks for reaching out to the community! I understand your Chromecast with Google TV (4K) will not maintain its audio connection to your grouped Nest Wifi speakers after being power-cycled, forcing the audio back to your TV. Additionally, when the connection is active, the volume control is not consistent, with levels like 20 down to 4 producing almost no audible difference. That's definitely not the experience we want you to have, and I'm here to help!
To isolate this inconvenience, I'd like to know the following:
Please keep me posted.
Regards,
Juan
3 weeks ago
Hi, the Chromecast is not being unplugged. I'm just turning the TV off. The TV volume is set to a normal level - the TV's volume setting has no effect on the bluetooth Nest speakers. The TV volume set to high, low, or mute, theres no alteration to the bluetooth speaker volume. Both of the bluetooth speakers are Google Nest Audio devices.
3 weeks ago
Hi moj85,
Thanks for getting back to me! Let's continue isolating the main issue, and I'd like to recommend trying the following:
Please let me know if the issue persists after these steps.
Regards,
Juan
2 weeks ago
Yes, it still has the same problem, restarting didn't help. And judging from posts on reddit, many people have the exact same issue.