Google Nest Wifi Pro setup process and errors

[Toiesvold]

Had a terrible time setting up the Nest Wifi Pro 3 pack to replace my old Google Wifi.
Setting up the first unit (router) went smooth - no issues.
But when trying to add additional units and create the mesh network, this failed several times. Units were not able to connect. Tried everything I could think of, including restarting wifi on my phone, rebooting and even resetting the units. They just wouldnt talk to each other.
Eventually I tried setting them up with an ethernet cable between them, and then I was able to add them and create a Mesh network without error message.
But even if Google Home now claims that all three units are part of a Mesh network, I only get internet connectivity from the main router. The other two units are blinking orange, and no devices are able to connect to them - Except if I connect a device to the LAN port on the unit.
Example: Main router is located in the living room. Approx 20 feet away the next unit is located in the hallway. I have a Eufy Homebase hardwired to the Hallway AP (and Homebase is not configured for Wifi)
But the Eufy Doorbell and homebase is working as is should, and I get notified and can view video from the doorbell.
Wireless devices have good coverage in the living room, but not anywhere else in the house, even if in close proximity of the two access points. It seems the two Access Points are not transmitting the wireless network at all. In the basement, where the last unit is placed, I have no wifi coverage, but if I connect a switch to the LAN port, I can hardwire my stationany computer and NAS.
I cannot see any way to fix this. The two AP's are blinking orange, even after restarts (with or without LAN port in use)
And the Mesh network, even if Google Home is claiming that it is healty, does not work.
How can I fix this without spending another 7-8 hours troubleshooting and trying (and failing)?

[Odsy]

I am also on Altibox, using my ISP provided Zyxel FMG-3542 router in bridge mode.

[Odsy]

I am also experiencing issues pairing my 2nd and/or 3rd Access Point (bought in a 3-pack) to my network when using an Android device.

As OP describes the issue, I am seeing the exact same thing. 

• Setting up my primary access point is no problem at all, and I get a good wifi connection once this is set up.
• I have verified that all three devices in the 3-pack I bought can be set up as the primary access point, they all work with an initial set up, and they all provide a good wifi connection individualy, so at least this indicates that they all work.
• When trying to pair up my 2nd access point (which is approximately 25 feet away) I run into problems.
• When I start to configure the 2nd access point, it is detected in the Google Home app, and I am prompted to scan the QR code.
• Once the QR code is scanned, the app starts to configure the wifi-mesh.
• When this configuration is going on I have noticed that my primary access point drops in and out of the wifi. I have also noticed that the status LED on the primary access point also goes from solid white to blinking slow yellow (about 1 second on, and 1 second off), then goes back to solid white, this behavior repeats several times while my phone app states "configuring wifi-mesh".
• While this configuration is going on, my 2nd access point is slowly pulsing a blue status light.
• After a few minutes of the above-described behavior, the phone app says, "something went wrong", and I can click the "try again" button.
• If I click the “try again” button, the process restarts, and now it seems that the wifi mesh is created, as the process on my phone goes further, and my primary access points maintain a solid white LED, and the wifi does not drop out.
• All looks good until I get to the step in the Google Home app where the process states "Adding the wifi point to your wifi network" (or something very similar).
• Now my 2nd access point is pulsing rapidly blue, indicating that it is pairing.
• My primary point maintains a solid white status LED
• After a few minutes of this my 2nd access point goes from rapid blue pulsing to a few rapid yellow blink, then starts to slowly pulse blue again, and my phone states that my “wifi point is out of range”, and I am prompted to make sure the 2nd access point is within range of the primary access point.
• This also happen if I have the two access points in the same room.
• I have also tried adding the 2nd access point with a wired connection to the primary access point.
• This works well as long as I have them wired, once I disconnect the cable, it starts flashing yellow, and I do not have any wifi through it.

I am using this as a reference to interpret the different LED status indications:

https://support.google.com/googlenest/answer/6191584?hl=en#zippy=%2Cnest-wifi-pro-router 

If it is wroth anything in debugging this, I am also locted in Norway, as the OP and others in this thread is

[Vegus]

Are you using an iPhone with iOS 16 or above? If so, have you tried turning off the "iCloud Private Relay"-setting?  

[Odsy]

What i describe above is using an Android device with the latest software updates done (did that yesterday)

When i try with my Apple device, this one is running a 15.7 version of the IOS

[Odsy]

To add to this, when trying with my Apple device, i have tried everything described in this thread with no luck.

https://www.googlenestcommunity.com/t5/Nest-Wifi/Google-Nest-Wifi-Pro-Wi-Fi-6E-unable-to-create-mesh...

[KongRøreks]

Exactly same problem I have... 

[Vegus]

It can be found searching for it under settings on your phone. 

 

[CobraBergan]

I was setting up using Samsung S21 and also tried setting up with my IPAD. Same type of struggle when connecting the points. And when I finally manage to connect the points through multiple retries and hacks. The points ends up blinking yellow, but the router seems fine (solid white), but in the google home app everything looks great. . My ISP is Altibox as well with Zykel home central.. Tried both with bridge mode on and off on Alibox equipment. Had 2 several hour long conversations with Google Chat about this. So starting to loose my patience here. Very eager to understand if should go ahead and return the Set of three Google Nest WiFI Pro. Or whether a fix for this is around the corner. 

[Odsy]

Anyone had any luck in finding a work-arround?

I am still not able to add my 2nd and 3rd device to my network.

[KongRøreks]

Hi I have not have time to look at it but I got this mail this weekend:

Thanks for reaching out to the Google Nest Customer Care Team.

Our Senior Specialists are suggesting that you wire a laptop\desktop direct to your additional Google Nest Wifi Pro using an Ethernet cable. Make sure WiFi on the laptop\desktop is turned off and only connection is via the Ethernet cable. Check if you get internet access on the laptop\desktop. If yes, please open this page to get the status report of your child Google Nest Wifi Pro: Status report pade. Please do the same steps on the other child point and send me a screenshot of your status report page. Thank you. 

I don´t think this will help me since I also having problems to get my Mesh network up. I got it up one time with cables between the Nest router and Nest Point, but with no internet an still the yellow flashing light...

[Odsy]

As long as I am not able to get my 2nd or 3rd access point up and connected to the mesh, I will not get any inthernet access with a laptop hardwired to the access point, so I dont really see the point of trying this out, but thanks for the feedback

[KongRøreks]

Same for me, but I will try to get the Mesh up again trough cables between the points just so they may get some more information, I will keep you posted...

[leifarneb]

Hello. Another Norwegian here... with Altibox as ISP. After several very long calls with Google Support. I was turned away (referred to Altibox) As per info from Google support, after they had gone through my network log dumps etc, they believe its a Altibox Zyxel home central issue. Basically an IP allocation issue of some sort. I find it abit hard to believe... since i have full internet access... if i connect manually to the "setup network" of one of the mesh nodes (whilst it is hardwired to the master)

[Sigvald]

Hi and Thank you for sharing.

Sorry for my long rant/read, but I really want to find a working solution.

I am also a customer of Altibox with Zyxel VMG 8825 in bridge mode. The Access points blinks yellow slowly indicating a "Network Error". I have asked multiple times what kind of network error that can trigger this state, without a single bit of information in return from Google Support.

I have switched the TV traffic to an other VLAN while the internet traffic is connected directly to the Nest Wifi Pro master node.

Below is a diagram of the planned network. This works great with to other access points, an old Netgear and a old Linksys, but these device have low wife acceptance factor (ugly).

I have tested a very simplified variant where all but the Google devices are gone, and all devices placed on the same floor. The result were exactly the same. I have rebooted all devices so many times that I more or less know on the second when it will be back.

I find it extremly unlikly that the Zyxel box in bridge mode should be involved in any address allocation protocol beyond allocating the single ip address for the Master Node, when it is in bridge mode. In bridge mode it should be completely transparent regarding the internet traffic, while it handles TV related traffic (multicast stuff) a bit differently. The Zyxel box must still have it own ip-address so that Altibox can reach it.

In the second diagram above there is no other equipment involved, so it is possible to start debugging.

1. There are several sources of possible problems due to the fact that we need Google Home on a mobile to install the devices, we have the devices, we have some cloud services from Google, we have the ISP and we have the Zyxel device.
   
   
2. At least my mobile ended several times up on mobile network, instead of the wifi network. The time and the resilient effort Google Home took during the installation indicates connections to cloud services. Default fail-timeout tends to be 30s. Connections between the inhouse devices should technically be below 1ms range.
   
   
3. Altibox did send me a SMS during the installation of the Nest Wifi Pro devices, telling me that I had to set the zyxel device in bridge mode. Which tells me that Altibox did detect that installed the Google Nest Wifi devices. Which is possible because the ethernet MAC address of the master device ends up in the ARP table of the Altibox device on the other side of the fiber.
   It can be that Altibox intercepts some traffic ment for Google cloud services, due to support for the old Google Nest Wifi, but that is speculation.
   
   
4. Wireshark is freeware, that can listen and decode most protocols used. The problem is that the number of devices possible involved in the faulty transactions. Again Google Support completely fails giving relevant information of what causes the Access point to signal "Network Error".
   
   
5. I am no expert in Wireshark, but can find myself around in the application, and told Google Support as much, but I do not know what to look for. I can set a switch interface in mirror mode and technically see all traffic between the Access Node and the Master Node, but if I have no clue what to look for, I can stare at the error for hours without seeing it.

I work for a pan-scandinavian ISP and have equipment developer experience with ethernet for 30+ years.

[leifarneb]

I agree.... makes no sense that it should be related to ISP isseus.

After posting the issue with Viken Fiber (Altibox) Facebook page... "Is Altibox incompatible with Google Nest Wifi Pro?" I got the following reply:

"Dette er en fellesfeil vi arbeider for å løse. Desverre ingen rettetid enda" - vh Sigve.

This makes, some sense, as it corresponds with other google wifi issues with Altibox. Currently google wifi service for tv set top boxes is offline. I suspect it has something to do with temporary or multiple WAN IPs. And that this is blocked/not allowed by Altibox.

While I wait for a fix... Altibox will send me a new home fiber terminal/modem.

[Jflaten84]

I have the exact same issue with Altibox. Do they think that the new home fiber terminal/modem will solve the problem, or why else are they sending a new device if they are working on a fix?

[leifarneb]

I don’t know… but after posting on Viken fibers Facebook page… I got this reply:

 

[KongRøreks]

Vi kan vel like godt fortsette på Norsk siden det ser ut til å hovedsakelig gjelde oss 🙂 Jeg har hjemmesentral/modem av type Zyxel fmg3542. Ser denne er fra 2015. Bør jeg også be om nytt modem? Kanskje ZyXEL P2812ac fungerer bedre. Noen som har den med samme problemer?

[leifarneb]

Jeg hadde, frem til igår en Zyxel p2812ac. Fikk ny hjemmesentral idag, Zyxel (ny versjon) Desverre samme feil med Google Nest Wifi Pro. Såvidt jeg kan se fra Facebook, så er dette en større feil som påvirker alle kunder som har gamle Nest Wifi og Q22 dekoder… de har prøvd å løse feilen i snart 3 uker….

[KongRøreks]

Akkurat, da er det nok bare å vente til Altibox og Google finner ut av dette...

[KongRøreks]

Last update...

I got an update from our Senior Specialists and they said that the issue you are experiencing might be related to a possible emerging issue with the Google Nest Wifi Pro. We are aware of the issue and are currently working on a fix. There will be several software enhancements rolling out through the end of the year that will improve a variety of stability and performance issues. We encourage you to hang tight and wait for the next firmware update. Thank you.

[leifarneb]

Who sent you this update?

[KongRøreks]

Google support. Got a massage on another tread that a New update is out today but have not tried any update today...

[KongRøreks]

*message 😂😂

[leifarneb]

😂😂 haha. Good one

[KongRøreks]

BTW, prøvde å oppdatere nå uten noe hell... Så ut som punkt 2 fikk ny firmware når det var koblet til routeren med kabel men akkurat det samme som skjedde under installasjon. Feiler første gangen med kabel også, så klarer den å lage mesh-nettverket men uten internett.. Så må nok vente på neste oppdatering og 😞

[Odsy]

Thanks for your updates.

I ended up retruning my Google Nest Wifi Pro 3-Pack last thursday.
Will await further updates to see if I will re-purchase at a later stage.

[Jflaten84]

Jeg så beskjeden om dette på Altibox sine sider. Men vet vi om dette er samme type feil som de opplever med gamle Nest WiFi?

[Vegus]

Etter firmware-update og restart fungerer nå min 3-pack veldig bra. Måler opptil 710Mvps trådløst koblet til hovedenhet, og rundt 450Mbps koblet til nodene (750-linje fra Telia). Det er en god del raskere en ASUS RT-AX92u Mesh jeg hadde tidligere, men den største forskjellen er stabilitet. Mye lavere jitter, lavere Ping og null packetloss.

[leifarneb]

Hvilken FW versjon har du?

[Vegus]

1.63.324946

[leifarneb]

Samme her… men funker desverre ikke

[Jflaten84]

Hvilken ISP har du? Jeg har samme FW, men her fungerer det heller ikke med mesh points, kun router. Her er det Altibox som er ISP.

[Vegus]

Har Telia hybridfiber 750/25.

[KongRøreks]

Han skriver vel at han har 750 linje fra Telia så da ser det vel mer og mer ut som problemet ligger hos Altibox...

[Jflaten84]

Jeg var tydeligvis litt trøtt i øynene her, så overså helt det med Telia i forrige post 🙂 Ser ut til å fortsatt være Altibox-relatert problem ja.

[KongRøreks]

Har sendt en forespørsel til Altibox nå om det er kjent hos de... Will keep you posted 🙂

[KongRøreks]

Fikk raskt svar om at de er kjent med problemstillingen, men at de strengt tatt bare har support/service på den gamle Nest varianten da de vel selv ikke selger Pro enda... Så vi får se om det er Google eller Altibox som finner ut av dette først...

[Odsy]

I got a tip from a friend who has also struggled with Altibox as ISP,

He was setting up a Ubiquity UniFi network, but also had issues with IP allocation through hes Zyxel home central.

He told me to try the following:

• Put the Zyxel router back into "router mode", not in bridge mode.
• Turn off Wifi (both 2,4Ghz and 5Ghz)
• Connect the Google Nest Wifi Pro to the routher through a wire
  • This will make the Google router the only wifi router
• Try running the normal mesh setup through the Google Home app with node 2 and 3.

Not sure if this will solve the problem, but at least it is another stone to turn.

Please provide insight on this proposal, even if it did not work it would be nice with some feedback! 🙂

[KongRøreks]

Thanks for the information, my problem is that I have firewall behind the modem. And so need the modem to stay in bridge mode. What I find strange is that the Nest router works just fine so I really don´t understand why it can´t make the Mesh network work. It make no sense that you have to have the Nest router directly to the Altibox router/modem. The Nest are just helping with wireless network and you should be able to secure your network...