r/GoogleWiFi • • Feb 19 '23

Nest Wifi Nest WiFi Now Sucks - Google Always Ends Up Slowly Breaking Everything

181 Upvotes

I was once one of the biggest fans of Google products, but the must be the only company that actually launches a product that works before slowly breaking it overtime via over the air updates.

Nest WiFi seems to be the latest addition to this long and growing list. My mesh was running totally fine for ages now however evidently like so many others it freezes and I randomly get no internet. I've set my router in to modem mode, changed the DNS, factory reset but the mesh is still dropping out, needing a forced restart after which its fine for a while.

Google support is useless. If you're thinking about getting the nest or adding to the Google eco system, I'd think again and look elsewhere.

Alphabet get your engineers to stop playing games around the GooglePlex, get them to get their fingers out and start undoing some of the damage being done to your smart home range and your brands reputation. Everywhere you look online people have complaints and it looks like you're going backwards in this department. Sort it out FFS.


r/GoogleWiFi • • Mar 16 '24

Never again, this router is trash

134 Upvotes

I've about had it with this piece of shit. Every so often it will lose the internet connection and refuse to reconnect. I can take the cable and plug it into my computer, renew my IP, and get online, so I know it's not the modem. It seems like the god damned dumbass router gets stuck in whatever fucked up state it's in and won't actually refresh the connection even when leaving the fucking thing unplugged for a while and plugging it back in. Can't connect to configure the worthless white lump because it's offline and can only be configured through the Google Home app if it's online. My mesh points lose their connection every once and a while and that's annoying, but rebooting them will fix it so whatever, but this is driving me crazy. Factory resetting the fucking thing seems to be the only reliable fix, which is fucking outrageous when I'm pretty sure putting a 'renew IP' button on the 192.168.86.1 page would solve the problem. I will never buy Google networking gear again, it's massively disappointing and frustrating to deal with. If I wanted my shit to be so smart and helpful that I'm left up shit creek when it fucks up I'd be an Apple customer.

Thanks for coming to my TED talk.


r/GoogleWiFi • • Sep 13 '21

I know the mods really aren't that active, and I know this is off-topic, but the sub logo should be the image below instead of a generic wifi icon

Post image
132 Upvotes

r/GoogleWiFi • • May 30 '26

Nest Wifi After 6+ years, I finally solved all my Nest WiFi issues. Thanks, Google!

Post image
123 Upvotes

r/GoogleWiFi • • May 26 '25

Parental problems Teenager discovered VPNs

123 Upvotes

The kid is very smart, and figures workaround from the PC and phone to use free VPNs to access websites blocked by the CloudFlare DNS (.3 one). And keeps downloading sketchy apps. I approve their curiosity and explained the risks but it causes issues on the network. Is there a way to block those Free VPNs from our Google WiFi 6?

UPDATE: Thank you all for your helpful answers and suggestions, I have read through them and figured that there isn't a feature in the router that can help other than using a different DNS provider.


r/GoogleWiFi • • Dec 21 '21

R.I.P. OnHub Onhub discontinuing support from Dec 2022. Really disappointed that the app won't work.

Post image
116 Upvotes

r/GoogleWiFi • • Apr 03 '22 Popcorn

"espressif" device type joined my network

102 Upvotes

Hello all, I'm using the first generation Google WiFi. Guest network is not activated and I've never shared my password with anyone. Not even my partner. I just type the password when connecting a new device. It's a strong password. Combination of upper, lower, numbers and symbols. I just got a notification that a device of type "espressif" joined my network. It's name is also "espressif". I googled that, and it's a Chinese ioT company. Could I have been hacked? What can I do? I only found a way to "pause" that device. But I guess if they hacked it then they know the password so need to change the password. But I'm wondering if they found a vulnerability rather than guess the password.


r/GoogleWiFi • • Apr 16 '26

Google Wifi TIL: You Can Flash OpenWRT

99 Upvotes

Now I have full control to all my pucks and also RGB lighting (kinda) 😁

Everyone behind this, you guys are amazing.


r/GoogleWiFi • • Apr 08 '23

This pretty much sums up Google WiFi Pro.

Post image
99 Upvotes

Starting on Monday 3 of my 4 WIFi Pros started blinking a yellow light. I unplugged all, then plugged back in about 12 inches from the router, yet they still blink yellow. I paid $600 for this weekly frustration.


r/GoogleWiFi • • Apr 14 '20

I am developing a desktop client for Google WiFi/OnHub! Any suggestions?

Post image
95 Upvotes

r/GoogleWiFi • • Jun 21 '21

In the 90s, my lil brother and I created a set of rules to call 'dibs' for internet that night on our single dial-up connection. Today, I have 34 devices connected to my home internet.

Post image
94 Upvotes

r/GoogleWiFi • • Nov 30 '17

Google actually added my suggestion

Post image
92 Upvotes

r/GoogleWiFi • • Jun 10 '21

Google home app for wifi management is terrible

91 Upvotes

So Google wifi app was not perfect but it allowed me to do things that the Google home app cannot do or fails to do

  1. I can't see historical devices that connected to my network.. Google wifi allowed me to choose a period of connectivity and then I see all devices that are online and offline that connected to my wifi during that chosen period up to 30 days

  2. The port management inside Google home doesn't show any of my port forwards so I'm unable to edit them when I need to, and port management is disabled inside Google wifi too. I currently have no way to edit forwarded ports. I need to factory reset my entire Google wifi system just to delete ports

  3. Because I can't see the ports already forwarded, everytime I try and forward a port that I've already forwarded, I get an error in the Google home app

  4. Setting DNS settings is a pain and takes a lot of saving and resaving before the settings take effect

  5. When I first set up my Google wifi devices, it doesn't detect internet connection from ISP modern through PPPoE login. It takes trying over and over and over again for up to 30 minutes before the internet connection is detected

  6. Although my DHCP lan pool starts at 192.168.86.20, my ip cameras are being assigned to ip addresses lower than that causing it to conflict with my static IP address devices

After using Google wifi for years, I'm really feeling some serious frustration with the wifi management in Google home app

https://www.reddit.com/r/GoogleWiFi/comments/nxuvxy/fyi_to_those_who_are_lucky_enough_to_have_not_yet/?utm_medium=android_app&utm_source=share

Update: Thanks to u/Galactic-Toast who indicated that rolling back a version of Google wifi re-enables all the greyed out settings in the Google wifi app, so at least thinks that aren't working in Google home can still be controlled in the older Google wifi app. I just assumed the disabled action was a server side action but it helps to know that it was an actual app version update, making rolling back possible


r/GoogleWiFi • • Oct 14 '18

Google Wifi is Ridiculous

85 Upvotes

So, I set aside the morning to install the new network in my home using Google WiFi. Was initially leaning towards Unifi because I’m a geek but Google’s built in parental controls sold me. So I connect the pucks, download the app and ..... wait that’s it?

In under 15 minutes: max bars throughout the house (2 story 2000+ sqft home with modem tucked in under stair closet). Ping 10-14ms. 4K streaming without skipping a beat. Was planning on using AP mode since I have hardwired cat 6, but honestly I don’t need to. Love the app and network stats. Simple, hassle free, no tweaks required. Love it!


r/GoogleWiFi • • Apr 11 '21

Do NOT migrate Google WiFi into Google HOME app.

82 Upvotes

Google notified me Google WiFi app is being obsoleted and being replaced with Google HOME app. They instructed me to migrate / import my WiFi network into the HOME app. I did it and ran into 2 major bugs:

  1. Everyone in your household (including kids) have full access to the WiFi settings such as schedules. There is no way to selectively grant Manager control to specific devices/services. Everyone has manager access to everything.

  2. Once you migrate WiFi to be controlled by HOME app, there is no way to undo it. Other devices in HOME app allow you to select device -> Settings -> delete. That option does not exist for WiFi in the HOME app.

I chatted with Google Support. They suggested removing my kids from the HOME app, but that is not practical as the kids need access to the HOME garage opener.

Google Support said to try a factory reset on my Google WiFi pucks and reconfigure them in the WiFi app. That means I'll probably have to reconfigure all my attached devices as well. And that still may not remove my WiFi from HOME control.

Do NOT migrate Google WiFi into Google HOME app. At least wait until they have worked out these 2 serious bugs.


r/GoogleWiFi • • Oct 06 '20

Google Wifi quietly relaunched at $99 with three-pack for $199

Thumbnail
9to5google.com
79 Upvotes

r/GoogleWiFi • • Oct 31 '19

Client Isolation Issue

77 Upvotes

So I'm encountering a weird issue with my Google Wi-Fi right now and it's creating a client isolation.

I have 3 Google Homes and 6 Chrome casts. Last night my Google Wi-Fi went completely bonkers and stopped letting me cast anything. This morning I completely reset everything to fix the issue, but now something odd is happening with one of the nodes.

My living room nodes seem to be isolating clients. When my phone connects to the living room node it can only see Chromecast devices that have also connected to living room. However when my phone connect to either of the other Google Wi-Fi nodes it can see and cast to ANY chromecast device, including the ones connected to the living room. Not accurate anymore.

I've tried reseting the node, again, setting a wired backhaul, wireless backhaul, changing phones, changing computers. It doesn't seem to matter. That one All nodes are isolating clients for some reason.

EDIT1, Chromecast Technician: So google support just tried to tell me that the reason why I could only see certain chromecasts was because as I moved nodes I moved networks and they were separated. (That's not how Mesh works).

Edit 2, Different Technician. Google Wi-Fi technician again: "Your devices can't be isolated because you're not on isolated networks you're on a MESH. "

Edit 3: No resolution. Use the submit feedback button and pray

Edit 4: The issue seems to be caused by my living device. When that node is disconnected things work fine. When it's connected I have issues. UPDATED EDIT 4: Adding/Removing individual nodes seems to fix the issue temporarily, but after about 5 minutes the Google Wi-Fi nodes will move devices to different nodes automatically and Chromecasts will be lost agin.

Edit 5: Here comes the blame game. It's Chromecast's fault, no it's Google WiFi fault, no Chromecast, no mesh

Edit 6: We're factory resetting the Chromecasts now. 3 hours into the call.

Edit 7: Google support said they were going to research and call me back in an hour

Edit 8: After no help from Google I've decided to try something. I unplugged all my Wi-Fi points except the main, and guess what? It's works. Guess it's a problem with Mesh like I keep trying to tell them. Not a Chromecasts problem.

Edit 9: 1.5 hours later someone a supervisor from Chromecast calls back. THE ISSUE ISN'T WITH CHROMECAST YOU FUCKING GITS ITS WITH GOOGLE WIFI.

Edit 10: 1 hr later. Another supervisor, telling to reset the Chromecasts.....again

Edit 11: Nope, apparently, the issue is that I have a custome LAN address not the default 192.168.86.0/24 now. Fucking really?

Edit 12: apparently "the cloud" isn't syncing the clients properly. Ah yes, the illustrious cloud.

Edit 13: Now, 7 hours later, they are finally asking for diagnostic reports.

Edit 14: Many thanks to /u/CyborgHobo for pointing out what might actually be a real cause.

Edit 15: People are reporting on Google Home that they are having issues with Googole home devices not being visible. https://www.reddit.com/r/googlehome/comments/dpu84j/has_google_broken_speaker_groups_again/

Edit 16: I've submitted the issue the Verge so hopefully it can actually get highlighted in news and put a little pressure on Google to fix it. Right now I have $200 paperweights since 2 of the routers are unplugged.

Edit 17: I also submitted it to 9to5google and Forbes. Hopefully someone picks it up and runs an article on it.

Edit 18: /u/KathleenGarrity from Google commented below, but wanted to do more troubleshooting. I'm not doing more troubleshooting and I'm certainly not doing it over Reddit.

Edit 19: Google emailed me again asked for the diagnostic reports and logs I already sent them 36 hours ago. Looks like someone isn't reading their own case notes. If they're even taking any.

Edit Fuck this: November 8th No update

Edit: November 18th: Things seem to be working again. I've put things through the normal tests and they're coming back normal. Credit to u/smitty8100 for noticing

Edit: November 18th: Nope. Didn't work. Things are still broken.

Last edit: On November 21st I got a email saying it was fixed. At first it didn't work, but after a factory reset and setting up the network with Google home not Google WiFi it now works.

Last Last Update: It appears we were all correct. The issue was infact mDNS as confirmed by This email I recieved today November 26th.


r/GoogleWiFi • • Jan 08 '24

Google Wifi Teenage son always tells me our 300mbps internet sucks for gaming on our Google 1st Gen Mesh Network. What can I do?

76 Upvotes

The mesh routers work great for everything/everyone for phones/streaming...but he says our wifi sucks on ping and his gaming that he can't even play competitively. I started to google and found the google wifi has a lot of issues with gaming it appears?

Are there any affordable mesh networks worth trying? I have access to a discount store that did have some Netgear Nighthawk mesh routers (hub & 1 extender) for only $55. My google wifi has the 1 hub and 2 extenders. Would the Nighthawk be worth trying for better speeds? Or what is a good one thats affordable and is a mesh network for gaming?

Thanks for any tips!


r/GoogleWiFi • • Oct 30 '22

“Everything’s fine…”

Post image
76 Upvotes

r/GoogleWiFi • • Jan 30 '22

Floor Plan I have 45 Google Wi-Fi’s in my two bedroom apartment and still have low speeds and poor mesh signal. Please help!

76 Upvotes

I keep adding more and it’s not improving. It doesn’t make any sense. These things are total trash! I’d rather not replace all my furniture with these things but it’s getting close.


r/GoogleWiFi • • Oct 18 '20

Solved!!! - Unusable Google Wifi - packet loss over ethernet - Sonos interaction was root cause

73 Upvotes

TL;DR - My Sonos devices were causing a spanning tree storm and knocking my network offline for two to thiry seconds a few times an hour. Removing the Sonos devices from the network fixed everything. I still need to update when I get things working with the Sonos again which I'll do today or tomorrow.

I have been experiencing sustained periods of packet loss from all the devices on my network for some time now. It got worse over the summer and I finally had some time to debug over the past few weeks. I got so much help from the prior posts here and I thought I would share my voyage and the successful conclusion.

My network setup is relatively simple:

Modem in bridge mode -> primary google puck -> unmanaged switch 1 -> unmanaged switch 2 -> 4 to 5 child wired google pucks

As you can see above all of my pucks are wired into the primary via two unmanaged switches. I have the first switch there so I can simplify my network for testin purposes and connect only my laptop into the first switch and disconnect everything downstream (including the child pucks).

The symptom was that my 2019 Macbook Pro would show as connected to the wifi, have a very strong signal (-35 to -40dBM) and have no internet connectivity. I immediately assumed that there was some interference so I added more pucks and move the primary into my office (about 6 feet from my computer). I did a variety of other crazy, invasive, annoying things like disconnecting our DECT phone system, making a tinfoil hat for a nearby puck, etc. That all improved my signal to near perfect but did not have any impact on the issue.

I wrote two scripts to diagnose the problem:

  1. a script that would constantly ping the Google Wifi gateway (192.168.86.1 in my case) and timestamp the results

  2. a script that would use the aiport utility I found in other posts here and log and timestamp those results. That would give me the signal and noise for my wifi and help rule out whether or not the issue was interference

// TODO #1 open source these scripts at some point

I started running both scripts on my wife's 2012 Macbook Air several rooms away as well as my computer. After less than an hour I was able to observe the issue - both computers dropped 100% of the packets to the gateway. Remember, this isn't even leaving my network so, barring some terrible config issue, this isn't related to the ISP.

While the issue occurred on both computers at the same time the signal stayed strong and the noise didn't jump. I became pretty sure that, surprisingly, this wasn't a wifi issue at all.

Next I installed a USB-C to ethernet dongle on my macbook pro and disabled the wifi. Wait an hour and same issue - 100% packet loss for 35 seconds. Ok, now things are interesting. I am connected to the puck via only an unmanaged switch in between and I can't ping the gateway!!!

I have been speaking to Google Wifi support this whole time on and off via chat and email. They are completely useless and are clearly reading a script. I tell them I have packet loss to the primary puck on my network and they tell me to change my DNS. The suggestions they gave were offensive to anyone who has the slightest clue what is going on. Nonetheless I restored my whole network to factory settings and the issue persisted. I have a bunch of servers, cameras, smarthome things, etc. running on my network with static IPs, port forwarding, etc. so the factory restore is pretty troublesome for me.

After demonstrating the simple test where I couldn't ping the gateway via ethernet I ditched the useless support and turned to this community on Reddit. I saw so many helpful posts.

This great post explained an issue with wired pucks that have poor mesh connectivity which pointed me to this google wifi support issue. I learned a lot but I couldn't tell if it was still happening in 2020 or not. The Google support people didn't know either.

This great post just did a fantastic job explaining how the wired ethernet backhaul works IMO.

More on this one later about ethernet backhaul showing as mesh.

I used Wireshark on my mac to capture anything that wasn't TCP to see if I could line up any issues when I couldn't ping the gateway. One interesting tidbit is that while I was unable to ping there were still packets flowing - ARP, etc. so the network was functioning. I saw some spanning tree comms going on leading up to the issue but I didn't feel like it was every time. Again, I wish I kept better notes and I could tell you for a fact and not a feeling.

On Friday I came up with a test and a phased approach to setting up a new network.

Modem -> Google Puck for new Network (192.168.87.1) -> unmanaged switch #1 -> Google Puck for old Network (192.168.86.1) -> unmanaged switch -> rest of child pucks and devices.

This creates the dreaded "Double NAT" issue that Google support hates so now I was really on my own beacuse if you ask them any questions they basically just respond "Double NAT" and send you a useless webpage about how to put your modem in bridge mode.

I plugged my laptop into switch #1 (the new Google network I just created). This network was now serving only 2 devices - the puck for the second network and my laptop. I ran the same script as before (pinging every second) and now things behaved like a regular network! Great news. This lasted all day. For the first time in a long time I had

After everyone was done with work and remote school on Friday I made myself a list for rebuilding my network on Saturday morning - what devices I need to check, etc. On my previous restore I gave the same SSID and wanted to eliminate that issue that there was some routing problem with a camera with bad DHCP implementation or something.

Saturday morning I factory restored all the old Google pucks so I could add them to the new network. One by one I added the switches and then the pucks to the mesh in wifi-only first and then, eventually, wired. I kept running my ping logger script throughout and it looked relatively stable. One side benefit of doing this is that, as I added each device, I could name them properly. Now I have well named devices for the thermostats, amazon echos, etc. rather than "android 1," etc.

Unfortunately, this new network started to exhibit the same issues. I'm not sure if it happened right away or not. I wish I did a better job with my experiment logging. Regardless, last night after rebuilding everything I was left with the same problems as before.

I tried some more stabbing in the dark things -> Turn off certain access points because maybe I had the weak-wifi-ethernet-backhaul firmware issue from 2018? Remove the basement point because that one was added most recently and maybe caused the issue? Turn all the wired points back into mesh points? IDK - I was desperate and nothing worked.

I was left with a setup where I had modem -> primary puck -> switch #1 -> switch #2 -> two well placed, wired child pucks + wired devices + wifi devices that could reach those pucks. Somehow the issue was worse and happening more often which I was excited about because it would be easier to test.

Since I was still having the issue in this simple setup I fired up Wireshark again. I kept adding filters for traffic I understood until I was left with basically just ARP, STP and some UPnP stuff. I was "lucky" enough to be having the issue every 15 minutes or so now and I finally saw a pattern! Sonos. I knew that most of the issues that people had with Google Wifi in an ethernet backhaul situation came down to Spanning Tree Protocol (STP) but I "knew" that there were no STP roots on my network except the primary Google puck. Well, I was wrong. Sonos was fighting with Google with some serious STP storms. It happened every time the pings stopped. Every time.

I came back to reddit and there are many posts related to Sonos+Google Wifi and some posts on the Sonos forums that point to this STP issue.

I unplugged the power on my 7 wired Sonos Connects. Got better but still had the issue. I unplugged the Sonos Player 1 in the garage. Got better but still not perfect. I removed the wifi settings in my Sonos app and turned off the Sonos Move. Perfection! The STP topology stopped changing. The packet loss stopped.

I think what was happening is that there was a loop introduced. My hunch is that happened with the addition of the Sonos Move device over the summer but I'm not sure. I have an outood AP (not google with separate SSID) that is wired into the Google network via switch #2 and the Sonos Move was connected to that. That showed up as a wired connection in Google so I think, somehow, the Sonos STP thing was getting involved.

TBH I haven't researched much how the Sonos Connects are connected - my AV installer put them in originally. Now that I understand the issue is Google Wifi + Sonos I have what I need to put the network back together and properly add Sonos back to it. For now, I'm much happier having reliable internet and no Sonos than having unreliable internet and working Sonos.

I'll update when I get the Sonos issue resolve so people know the result. A couple other things I found during my voyage that may be helpful for people:

  • When you do a mesh test there is more data than weak, ok, good. If you click the "..." in the upper right and click details down below you can see the throughput for each puck. You have to do it form the mesh test results screen and it doesn't persist when you are just looking at the wifi point screen. Why? Who knows. What do these rates mean? There is a lot of discussion of that around but think of them in comparative terms - low is bad and high is good - and not necessarily your actual wifi throughput you should expect.

  • The post above that talks about wired points showing up as mesh is important. That was an issue that I had as well. I don't know if it is just a mislabeling OR if it indicates that the puck is actually functioning as a mesh puck and not a wired puck. Regardless, the way that I was able to get it to register correctly is to go Wifi Points -> Gear -> pick any non-primary point -> Move Location. I selected the same location and just went through the steps. After doing that all of the wired points would register correctly for me.

Like I said, I'll be back when I get the whole thing working. I have to imagine that my setup of Google Wifi + wired pucks + sonos is very common in new construction homes that are pre-wired and hopefully this helps some of you.


r/GoogleWiFi • • May 29 '25

Finally Did It. I drilled vent holes in my Google Wifi Pro 6e's.

Post image
72 Upvotes

r/GoogleWiFi • • Feb 21 '21

With Apologies To Google, I'll Be Eating My Crow Now...

71 Upvotes

...and whatever else is warranted. On an earlier post, I blamed Google for my wifi problems. Believing the issues were related to the "Google update in November", and having replaced my Cox modem twice since then, I had it in my mind to blame Google. u/XRaptor29 offered a few ideas, particularly regarding my modem. I followed that up with a search of modems and came across "List of 71 Bad Cable Modems" and found my Cox ARRIS TM34O2A on the list along with 26 other ARRIS modems. I ordered my own (Netgear) modem and went about re-installing my Nest. What I immediately found was speeds and greater connectivity than I had with the ARRIS. U/XRaptor29 describes a "Puma chip" as potential for problems- something waaay over my head. What apparently I was doing was replacing my new bad-make modem with a newer bad-make modem.

Google, I'm sorry.


r/GoogleWiFi • • Jun 16 '20

Google and Nest Wifi update will improve network performance on slow connections

Thumbnail
9to5google.com
69 Upvotes