Hi there, I've been running an audio group for over a year. This group includes two Nest devices, Google Nest Mini (2nd gen.) And a Google Hub (1st gen.). Up to now, the volume could be regulated with a voice command "louder" or "quieter". Or you said percentages, that was also possible. Today the group refuses to do so. The individual devices can still be controlled by voice command, only the group cannot. The voice then says "I'm sorry, the volume on the device could not be adjusted" (something like that).
You are talking to the hand, I'm afraid.
But you can try with "Okay Google, feedback!". However, I'm not sure if that will be ignored, too. Actually I don't know a channel to make Google aware of any problems. My experiences contacting Google in such situations have been extremely bad so far.
Yep having the same issue for a couple weeks, but sometimes it works and sometimes it doesn't. We have Hub Gen 1, Home Hub Max and several minis throughout the house. One will play a radio stations and others wont on command. One will change the volume by voice and others wont. Google please address and fix this obvious SW bug!
Well, it certainly makes me want to get rid of my thousands of dollars of Google/Nest turds now, so Sonos is successful there. However, it also makes me not want to ever buy anything Sonos either.
I'm really curious if this issue is due to a Google engineer being lazy or if it's something else.
I stuck in there after they discontinued the Chromecast Audio, which I liked due to optical audio out that I fed to larger amplifiers for different zones of outdoor speakers. Now, there's no option like how Amazon Dot offers audio out. Guess it's time to control my audio w a company that actually cares about user experience and product support. Just sucks cause I have multiple displays, cameras, doorbells, Nest speakers, a few AV receivers with Chromecast built-in, and 2 sound bars. So, this group volume issue is a deal breaker for me cause I use it a lot
Thanks for visiting the Community.
Since this thread hasn't had activity in a while, we're going to close it to keep content fresh. We hope you were able to get the help you need, but if the issue persists feel free to create a new thread, and provide as many details as possible so that others can lend a hand.