cancel
Showing results for 
Search instead for 
Did you mean: 
Replies are disabled for this topic. Start a new one or visit our Help Center.

Removed features

BugSlayer
Community Member

Google has removed yet another essential feature from its Hub/Nest device. Previously, if you connected external BT speakers to the Hub, it would play media (music etc.) on the BT speakers, but the Assistant would respond through the built in Hub /speaker. This is reflected in Google's own support documents:

Google Nest Help - Help Center, where it says:

"Note: All media playback will play on the external speaker that’s paired with the Google Nest or Home device. Alarms, timers and Google Assistant's responses will play on your Google Nest or Home device."

This worked well, and in my case it was essential to my audio set up, as I prefer to power off my receiver/amp when not playing music, but the BT stays connected because it is a separately powered external receiver that passes the audio to my stereo and its connected speakers. I also imagine that if you used BT headphones with the Hub you would still want the ability for other users to communicate with the Hub while you were listening to music. This is no longer possible. Both media AND Assistant responses are coming through whichever speaker has been set to default. This means if I turn off my stereo, I no longer hear verbal responses from my Hub.

It is such a shame that Google has cut back the abilities of the Hub instead of expanding them.

A few years back they eliminated the ability to cast music to the hub from an Android phone.  There used to be a "Cast my audio" button in Home dor the Hub Display.  Now there is just "Cast my screen" which has inferior audio quality. 

The motion sensing feature had such potential (it could have expanded to volume control, for example). Very sad!

 

 

 

7 REPLIES 7

Juni
Community Specialist
Community Specialist

Hi BugSlayer,

 

Thanks for reaching out and letting us know about your concern. When you select your preferred device for audio playback, all audio voice commands you use with your speaker or display play on your preferred speaker or group without the need to specify its name.

 

Supported cast devices:

 

  • Chromecast Audio
  • Cast audio groups
  • Chromecast built-in audio devices
  • Chromecast (1st gen), Chromecast (2nd gen), Chromecast (3rd gen), Chromecast Ultra, and Chromecast with Google TV
  • Android TV
  • Chromecast built-in TV

Alarms, timers and Google Assistant's responses should still play on your Google Nest or Home device and media playback should still play on the external speaker that’s paired with the Google Nest or Home device. A few questions: when did it begin? Were there any recent changes made? Also, what troubleshooting steps have you taken so far?

 

I look forward to your response.

 

Regards,

Juni

BugSlayer
Community Member

I'm not certain how long.  At leat a few months, maybe more.  I tried rebooting my Hub display, re-pairing the speakers, reinstalling Home.  I called Google Nest support and had to refer them to their own help pages to prove that the Assistant was supposed to play through the hub while media came through the default BT speakers.  They consulted with their tech people repeatedly and finally said that's just the way it works now - everything goes to the default speakers.  It's easy to test:  have you tried your own set up? 

Juni
Community Specialist
Community Specialist

Hey BugSlayer,

 

Thanks for the details you’ve shared. Do you still have the case number from our support team so we can look into this for you? 

 

Keep me posted.

 

Regards,

Juni

BugSlayer
Community Member

I don't believe they gave me one this time.  Were you able to test the issue for yourself?

BugSlayer
Community Member

Any new developments?

Juni
Community Specialist
Community Specialist

Hi there,

 

Since the steps didn't work on your end, we'd be happy to take a look into this for you. Please fill out this Contact Us form with all the needed information, then let me know once done.

 

Thanks,

Juni

BugSlayer
Community Member

I will certainly do that.   Is there a reason why you cannot test this issue on your own system?  I have asked you to do so twice and you have ignored my question.