11-06-2022 01:12 AM
Hi all, a quick question. Current firmware on my google nest audio is 299498 (I currently experience the frequent connection loss both thru wifi and bluetooth). I noticed that the latest production firmware is 313652. So why does my device not update (and a forced update seems not possible). Any views or ideas? I hope the update fixes the annoying issue. Thanks all.
12-24-2022 10:08 AM
@Dan_A i just filled out the form as well.
12-25-2022 02:39 PM
12-25-2022 04:06 PM
please keep this thread alive. im eager to see what the results of completing the magic form of truth.
12-26-2022 10:20 AM
Hi MrJinx,
We understand that this step is a little out of the way, but it's a great start to check it further with our upper support team who can give you additional troubleshooting steps if needed. Kindly fill out this form and tell us once done.
Thanks,
Dan
12-26-2022 10:25 AM
i've completed your form and yet to hear from anyone. how many times do you have to give me the same bad advice?
12-28-2022 03:08 PM
I explained all the steps to be taken to solve this issue, but only a few of you follow my directions. And still keep complaining in this thread. Adding your device to a new home (create one) will solve the issue. And don't travel to your office to create a new home (you fool).
12-28-2022 05:05 PM
what if your advice only works every so often? i tried your advice several times before having to figure out an alternative fix.
google should have a more straightforward way to manually update their firmware. also, they should put out products that work as advertised.
12-28-2022 10:24 PM
Sometimes people have different network setups with firewalls and Adblockers like PiHole and Adguard. And if you haven't got a second phone to create a hotspot it might then be a good idea to take it to another place. Nobody can tell exactly what the problem is, is it the new home structure or is it something that blocks the communication to google? And will the speaker update at the next update after this workaround? Nobody really knows at the moment. Maybe google will come with an explanation and final solution.
12-29-2022 04:58 AM
all of that said, it's a problem with google, its product, and technical support.
12-29-2022 05:36 AM
despite all of this back and forth, the excuses are ridiculous. this tech is inconsistent and does not work as advertised. for most, the problem is not ad blockers, firewalls or network congestion. this is a problem with google and its IT.
12-29-2022 07:28 AM
My speaker is still 299498, but inexplicably it sometimes works in speaker groups. Sometimes doesn't. Sometimes unceremoniously drops the connection without any feedback. What changed on my network? Nothing. I've rebuilt GH homes so many times and even my wifi network, but the issues don't correlate with anything. And when it is working, I can't troubleshoot (would you want to want to remove and add back 20+ devices?). And sometimes when it's not working, I just don't have time to spend troubleshooting this product.
I appreciate the kind help and support on forums and in chats, and certainly understand the anger and frustration of the users. But I think we just need to accept the reality that this is what it is. Someone asked me why I was spending so much time troubleshooting a kludge instead of just using Sonos. That's a good question.
I will keep monitoring the progress on this thread (and other related threads), but I'm done wasting my time. I wish all of you the best with GH, and in the New Year!
12-29-2022 08:03 AM
i'm in the same boat. way back, when groups and stereo pairs worked, I loved my google speakers. sometime, perhaps after the lawsuit result, the google home and speakers began to have issues, hours and hours of this, that and the other have not fixed their problems. it's not me. it's them.
12-31-2022 10:05 AM
here's what i found out. after adding the google nest pro mesh, groups and stereo pairs work.
01-01-2023 01:08 AM
And yesterday the disconnect issue popped up again - so new firmware has not solved the problem… what a laugh, google and its useless products - nevertheless happy ny to all
01-01-2023 07:12 AM
google should have a guide of how many devices can be connected to a type of wifi. so far, the google nest pro mesh is working well for me.
01-24-2023 11:17 AM
01-24-2023 11:39 AM
thanks for looking into this. i've filled out the form several times. when do I hear from someone?
01-25-2023 06:16 AM
I just filled out the form. FYIW, after factory resetting my Nest Audio, I'm still on 1.56.299498. My lastest gen Chromecast with Google TV is 1.61.329909. Since this forum's been open for months, it would appear that the Nest Audio is stuck.
01-24-2023 12:21 PM - edited 01-24-2023 12:22 PM
I was able to resolve this issue using the procedure outlined by Cossey here:
However, I will say this is somewhat of a ridiculous process to have to go through. It's really not how I like to spend a Saturday afternoon (it takes a while to do this for 3 speakers). I really hope that I don't have to do this every time in order to get new firmware. I do have a bunch of older google mini speakers on the same network that did not require this, so I'm somewhat optimistic.
01-24-2023 12:53 PM
I agree. I have 19 speakers for that I went through a similar process. I'm incredibly disappointed in the Google hardware, firmware, and technical support.
01-25-2023 06:44 AM
@Dan_A: so far so good - as I mentioned above, my speakers were updated (without any intervention from my side), and since then connection seems stable. Fingers crossed, and sorry to hear that other members still have issues.... Pity that Google is not able to solve this for its customers
01-25-2023 07:28 AM
ivan,
im having problems with my speakers. as I mentioned, I have 19 speakers of various types. Home, Home-Mini, Nest-Mini and Nest. How many do you have? Can you get them to stereo pair and play in a group? I can not get all of them to play in a group or ad-hoc group? Also, I've had issues trying to playing them as stereo pairs? Which version of Home app are you on? Unfortunately, I'm on the Preview version and it's buggy. I don't recommend testing that Preview app.
Good luck