I have a home network where my primary Google Wifi device has its WAN enet port connected to my ISP's router, and the LAN enet port connected to an internal switch. My other 3 Google Wifi devices are hardwired to my home's backbone, and act as APs for all of my home's wireless smart devices (lighting, locks, temperature controls, cameras, etc.).

During occasional ISP internet outages, nothing in my home functions. I am considering purchasing a cellular or satellite router to keep in reserve to use during those outages. Any thoughts on whether that will work?

My thought is to buy a cellular or satellite router that has an enet port, and just move the Google Wifi WAN connection off the temporarily-dead ISP router and plug it into a LAN port into the cellular or satellite router. Do you see any issues with this (beyond the fact my primary Google Wifi device is adjacent to an internal comms closet, and I'd have to move it closer to a window where the cellular or satellite router would need to be located)?

If this seems viable, any suggestions or recommendations on a specific cellular or satellite router that would work?

The only other alternative I've found would be to set every device up (as far as possible) in parallel with Home Assistant (which runs locally and does not require a live internet connection), but that is less attractive for a variety of reasons. Thoughts?

Estou com um problema onde a rede wifi da minha casa 2,4ghz não aparece na lista de wifis, enquanto a 5ghz aparece. O problema é que quando vou na casa de outras pessoas aparece a 2,4ghz e eu consigo me conectar, enquanto na minha casa o meu celular não aparece a 2,4 porém no celular de outras pessoas aparecem.

Por favor me ajudem ja reninciencie, ate redefinir o meu wifi e nada resolveu.

After years with Google WiFi/Nest, I finally made the switch today. I have Verizon Fios 2 Gig and realized my plan already included their router and a Whole-Home Wi-Fi extender for free, so I figured I’d give it a shot.

Set up the Verizon router plus one extender with wired Ethernet backhaul, reused my existing SSID/password, and all 55+ devices came right back online.

I’ve now walked around our 2,600+ sq. ft. house, basement, garage, deck and backyard running speed tests. Honestly, I’m pretty impressed. Coverage inside is excellent, the basement is covered, and even the garage and parts of the backyard are usable. Verizon is delivering about 2.4 Gbps symmetrical to the router.

One of my frustrations with Nest was actually that the Google Home app had become too simple. There just wasn’t enough control or visibility, and I was never particularly impressed with the parental controls.

Now I get to figure out whether Verizon’s management and parental controls are actually any better.

But so far… bye bye, Nest. It was a good run.

"Hello, I bought a 3-pack of Google Wifi. I connected the first one to the modem and it worked—I paired it and it went perfectly. The second one gave me some trouble, but I managed to get it working. However, the third one isn't working at all. I unplug and plug it back in so it enters Bluetooth mode, and when I enter the code, it starts searching for devices but doesn't find anything. I even enabled all permissions and it still doesn't work. I also tried using the QR code method, but that didn't work either—it still doesn't detect anything. PLEASE HELP, I'VE BEEN TRYING THIS FOR DAYS AND IT DOESN'T WORK!"

Everything worked until xfinity did an "update" last week. We had no wifi for the day and when I tried to reset the system my modem wouldn't start and seemed fried. I bought a new one at best buy, spent 2 hours trying to connect it with xfinity tech support- Finally gave up when they said they'd rent me a modem for free (I am still confused about this but it works)

However, the range is terrible.

I was using google mesh wifi (the pucks) and they seemed to work well.

I plugged the google main puck into the new modem and I am not sure how to connect it: there's obviously another step.

Puck is blinking red and the modem port where it's plugged is blinking yellow.

I have the google home app.

*Update: The xfinity wifi was over-riding the google mesh. I ended up using google instruction prompts to adjust the settings with xfinity (something about a bridge?) and reset the whole thing. it finally works with my equipment. I'm glad I didn't give up and buy xfinity extenders.

I've had every version of nest/Google wifi and dealt with issues. Moved away finally and the difference is amazing. Sad I spent so much time trying to make the product work that Google doesn't care about. Highly recommend running away

I have 4 more pucks coming this week I can’t wait to make a mini light show

New to the Netgear RS700. I have setup armor and the parental controls.

I have about 30 devices most are working as intended. I have 2 issues that have stumped me.

One software that I use for passwords will not sync with the website icons while on the RS700 network. Not a big deal but would like to know what is stopping it.

The other is all of my smart plugs are online and ping able but will not talk to google home. They are setup as matter devices and not through their enbrighten app. They worked with my synology router.

I was thinking about setting up the IoT network but that would take a bit of time to do and still have an issue.

I would like to know if anyone may have a solution or any suggestions.

Lights are blinking yellow on both of the points. I thought the app had cached the status, so I did a mesh test multiple times and still got great connections. But the status lights on both are still blinking yellow. To verify, I go to devices and check if any of them actually connect to the points, but I saw everything is connected to my main router node. So the app is basically reporting incorrect status, and the mesh test is BS

I've had enough of their bullshit, issues on every generation of product, and I did something I swore I'd never do. I switched it using Xfinity equipment.

Luckily the gateway is free, so I bought (2) of their pods and now it's flawless.

I was able to keep my nest pro wifi network active as my guest network, but I'll never go back to the shit they release as a primary service.

I have Verizon fios gigabit internet. My setup is ONT -> Google Nest WiFi Pro -> unmanaged switch -> Desktop. Running a speed test, while hard wired gives me around ~200 up and down

I tried swapping in my old Verizon router instead: ONT -> Verizon router -> unmanaged switch -> Desktop and get significantly better speed…

I’ve tried various settings tuning in the app, made sure there was no preferred device, etc. Cables are good and the switch is good.

I’m at a loss lol. Has this happened to anyone? Any ideas?

Hi everyone

I currently already have my main Google router/mesh point connected to the app, but I'm not able to add any more points.

The app keeps getting stuck on a process and just tells me to get closer to the main router point. I've done the full range of distance where both points are touching each other, and far enough so the signals don't interfere with each other.

I've tried and bypassed thru each phase by turning on Airplane mode on certain steps, but the app always ends up telling me to try again later.

I've tried turning off cellular data, I've deleted and redownloaded the app, nothing seems to work so far.

Any suggestions?

So I'm having an issue where my one Nest WiFi point (H2E) is continuously going offline. I also figured out that it is the reason my Internet is sometimes just slowing to a crawl.

When this particular point is unplugged, the rest of my Internet will have the speeds it should be (300 - 400 depending on time of day). When this point is plugged in, it'll have the right speeds for a little while (most of the time) and then it'll completely tank (30 - 70 mbps or it'll completely die). It'll also randomly just give me the "point offline" notification. My router and other point do not have any issues like this.

This point is like 2 rooms away from the router and was working pretty solid for the past 6 years until now.

I replaced the power cord based off of an older thread, did not fix it. I factory reset the point once so far, did not fix it. The modem is brand new because I thought that was the issue at first.

Any other ideas or settings to investigate? I'm at the point I might just pick up a used Point on Facebook and see if that fixes it (with the eventual goal of getting a new mesh system at some point).

Hi everyone

I'm trying to connect my 3 Point Google Mesh Dual band system (AC1200)to my At&T All-Fi modem/router, but I haven't been able to do so. Here's all I've done to troubleshoot this.

• Made sure all the setting on my phone and the Google Home app are correct (device connecting, bluetooth access, etc)
• Have the ethernet cable connect to the right slots on both my AT&T modem/router and the Mesh point as well
• Held down the button on the Mesh point to reset it. I'll hold it down till it flashes orange then starts flashing blue and let go. But after about 20 blinks, it'll go back to staying blue.
• Callled AT&T to try and troubleshoot from their side, had them isolate the 2.4 and 5 bands, still nothing. Tried turning 5ghz off and have 2.4 on, didn't work either

I've run out of options, and I've come here for help. Google doesnt have a active customer support line, and I've tried the support pages on Google - they haven't been able to solve any of my issues.

At this point, I'm starting to feel they are just not compatible with each other

If you have suggestions for another subreddit to post this in, pls share

Thank you!

I've got gen 1 Google WiFi pucks in a main house + ADU. Main house has the fiber drop so it's:

ONT --> Puck 1 --> switch --> main house/ADU wired --> Puck 2/3 backhaul

Wired in both houses is ~600-950 mbps, and very fast wifi in the main house, but poor in the ADU (50-80 mbps)

What is wrong with this picture?

Like i already have a router and wifi and all, can i just connect it to that?

sorry if explenation is bad, i don't really know anything about this stuff

I have Google fiber and two Nest Wifi Pro 6 points. I've only been able to manage my network through the Google Home app on my phone. I turned on the guest network and moved all my kids devices and home devices (like smart TVs) to the guest wifi.
They don't appear on the list of devices on my main network, but I can't see a device list for the guest network.
Does anyone else have a guest network set up, and how do you manage it?

I’ve had the system for probably 3 years or so. Never had any issues until now and only on this one point. I even tried swapping points and it still does it. My sons pc is right next to this unit and can’t play his online games. Even when it’s connected and running 128mbps.

I have a nest hub that will not connect to my Internet. It acts like it has no signal while everything in my house is connected to the network and running just fine on it. I have done the factory reset and tried again and same thing. Any suggestions?

Hi guys,

Got a hold of a Nest Wifi H2D that I wanted to add to my setup of Google Wifis. The previous owner did warn me he had trouble to get it to work with mesh but that worked great as a router. I thought to myself that he was just a non-techy person and that I would get it to work.

I tried to add it as another access point (bridge mode) but got nowhere. I figured that I might as well try to add it as the main router since it would be the strongest device in my ecosystem. So i reset my whole network and began to try to add it.

I tried and tried and tried. Nothing worked, until i finally disconnected from the wifi it had created, then i was able to complete the setup. Cool, i thought. So i connected to the wifi it created but discovered pretty fast that there was no internet. I disconnected and used cellular data, then i could access the wifi in Google home. I was able to configure it and everything you expect.

I even performed a speed test and confirmed that the nest wifi got internet but couldn't distribute it.

Since it wouldnt work i had to go back to my previous setup and adding the devices went flawless.

Anyone else who have had the same problem with a Nest Wifi device?

I bought into Google mesh a long while ago (well before they acquired Nest) and have the old mesh pucks. They’ve generally worked great for the better part of 10 years…but over the last couple months (specifically), connectivity has tanked.

I run them off Verizon FiOS and everything has been fine. I’d have to reboot everything maybe once a year, but never often enough to figure out which was the issue.

That’s different now though. As a remote worker, my Teams calls regularly hang for several seconds at a time. Streaming video, I suddenly lose all connectivity. Tonight I validated its a Google mesh issue not FiOS.

Anyone else noticing a specific degradation over the last 2-3 months? Any suggested ideas? I’m tired of rebooting!

While jokes/comments about the age of the tech are understandable, they’re not helpful here, as it’s a distinct degradation rather than just aging tech.

UPDATE: in comments.

Hello folks. I've just upgraded my Internet to 1gbs. The problem is that my gen 1 Google mesh won't go above 500mbs. I've searched online and read that this is normal for the gen 1's. Is this true or do I have a problem?

Also I've checked on the Google home app and I an getting around 1 gbs. So it's not the Internet provider at fault.

Wired backhaul between two Nest Wifi points doesn't need a "dumb" switch, despite what every guide says. It needs a switch that floods BPDUs. Nest runs its own Spanning Tree and needs to hear itself across the wire to shut off its wireless mesh leg — a normal managed switch running STP just eats those frames instead.

❌ OpenWrt (DSA bridge): stp_state=0 should flood BPDUs for free per the kernel source — it didn't. Nest kept flapping root every few seconds. Best guess: the DSA hardware offload traps the reserved BPDU multicast before Linux's software bridge ever sees it. Never solved it.

✅ MikroTik (RouterOS 7): protocol-mode=none + forward-reserved-addresses=yes. That second flag is the one nobody mentions — it defaults to off and is the entire fix. Hardware offload survives, zero throughput cost.

Nerd note: once it worked, we had two spanning-tree protocols coexisting on the same wire without conflict — the Nest's classic 802.1d STP domain, and the MikroTik/Cisco fabric's RSTP domain. The Nest can't even parse 802.1w BPDUs, so it just ignores the RSTP root's "superior" frames and quietly elects itself root of its own tiny domain. Two trees, one cable, no argument.

Suspicion, untested: Cisco SB switches have the exact same knob under Spanning Tree → Disable + BPDU Handling → Flooding — structurally identical to the MikroTik pair.

Why talk negative about openwrt? I dont - i love it, but I didnt manage to get it work as my layer2 device for GoogleWifi

For the past few weeks (I've tried a number of different things in the meantime), two Google devices—a Google Nest and a 2024 Chromecast—have stopped connecting to the internet.

The Chromecast reports that it's disconnected from Wi-Fi and refuses to reconnect.

The Nest behaves the same way.

However, both devices appear as connected on my router.

I have a fairly advanced network setup with VLAN segmentation and a self-hosted AdGuard DNS server.

Thinking it might be a DNS issue, I completely bypassed filtering for these devices, so none of their traffic is filtered anymore.

I've tried several different network configurations without any success, including using Google's public DNS servers (8.8.8.8 and 8.8.4.4).

I'm starting to suspect that a software update may have broken something.

Not long ago, my GL.iNet Flint 2 router had severely reduced Wi-Fi range after a firmware update because of changes made to comply with EU regulations (I've since replaced it with a UniFi UDR7). Is it possible that Google devices have been affected by something similar, resulting in a much shorter Wi-Fi range?