About 2,800 square feet over three floors. Usually around 25 devices connected at any given time. Only one wifi router which can’t be moved due to where the cable enters the house.
This is clearly a job for Google Wifi.
I switched from an Apple AirPort Extreme to a Google OnHub router about a year and a half ago, and while I didn’t like it very much at first, a steady cadence of software upgrades improved it to the point where I was glad I switched. When Google Wifi came out late last year, and I found out that I could use mesh networking to extend the range of my OnHub, I pre-ordered a three-pack right away.
Mesh networking is relatively simple in theory, but in practice, robust mesh networks are complex. Mesh networks obviate the need to have multiple wifi routers with hardwired connections throughout your home or office. Instead, routers create individual, overlapping zones of coverage capable of relaying network traffic through their peers back to a single hardwired connection. Devices connect to whichever node has the best signal and/or the least amount of congestion, and then traffic is routed through the mesh, to your primary wifi point (the one with the actual connection to the internet), and then back again to the device — entirely seamlessly. Not only can mesh networks dramatically extend the range of your network without requiring you to run additional cables (all they need is power), but they are also extremely durable and robust since the network can route around any problematic nodes which may be temporary unavailable due to software updates or malfunctions.
I’ve had Google Wifi set up for a couple of weeks now, and I’d say that I’m generally happy with the results — though with some qualifications. Here are my overall thoughts so far:
Setup was relatively easy, but surprisingly time-consuming. The first thing you do is install the Google WiFi app on your phone (I used a Google Pixel XL), and then you follow a set of simple instructions which generally involve connecting a Google Wifi device to power (reversible USB Type-C!), scanning a QR code on the bottom, and waiting. And then waiting some more. And then, while you’re at it, doing a little waiting.
If the process goes smoothly, your patience is rewarded with a fairly painlessly upgraded network. However, the process rarely went smoothly for me. There were software updates, unexplained errors, and worst of all, ambiguous results. (I was told setup didn’t complete properly, yet the device seemed to be functioning. What do I do? Leave it alone and hope for the best? Perform a factory reset and start again? No way to know.)
Not counting the time it took me to run out to Best Buy so I could replace a surge protector I discovered was blown, it took about an hour from the time I opened the three-pack of Google Wifi devices to the time I had every corner of my home awash in a beautiful overlapping patchwork of 2.4 and 5GHz spectrum. Not too bad.
If the story ended there, my review would have been as glowing as the Google Wifi’s Cylon-like LED diagnostic strip. But sadly, the tale continues.
We have very reliable power where I live, but during a recent and particularly energetic thunderstorm, it flickered a few times. Every device in my house is plugged into a high-quality surge protector and/or a UPS so nothing was damaged, but none of my Google Wifi devices came back up properly. Both my modem and my OnHub wifi router recovered just fine, but all my Google Wifi nodes were pulsating red.
To make a very long story short, using the Google Wifi app to restart them fixed two of the three, but the third — the one closest to the network drop — wouldn’t reconnect. And then, after a factory reset, I kept being told that it couldn’t connect to my network because it was out of range of my primary wifi point (it was not). Acting purely out of instinct, I factory reset all three devices, and re-added them again one-by-one (the one closest to the primary router first). After a great deal of waiting and a few more unexplained errors (mostly failed tests), all three devices were back online, and my mesh network was restored to its former glory.
For a network that is supposed to be highly durable, I was pretty disappointed that I had to spend about an hour and a half trying to bring it back up after a fairly routine power flicker. And while I feel the quality of my network justifies the time I put into it, I can’t imagine how someone without early-adopter patience would have handled both the initial setup process, and then having to set everything up again a week later. (Actually, I can imagine it, and it looks a lot like several frustrating hours on the phone with support.)
In other words, Google Wifi currently meets my expectations and standards, but it does not pass the “parents” test. (If you buy this for your parents, or recommend they buy it for themselves, be prepared to provide plenty of tech support.)
If you have clear wifi-hypoxic zones in your home, and if you have the patience to deal with a system that clearly still has some bugs to work out, then I definitely recommend that you give Google Wifi a try. I consider $299 (for a three-pack) a reasonable price to pay for sophisticated networking equipment that solves a very real problem without having to run any additional cables throughout your home.
But unless you have a very clear need for something like Google Wifi, I would recommend waiting. Consumer-grade mesh networking is still relatively new, and while $299 isn’t bad ($129 for a single device), as with most new technology, the longer you wait, the cheaper it becomes — but more importantly, the less of your precious time it will demand.
Update (3/27/2017): My experience with customer support, and all connection issues finally resolved.
I’ve had Google Wifi for exactly one month now, and I’ve continued having problems with individual nodes going offline, usually after some kind of network event (power outage, reboot of my router, etc.). Sometimes restarting the affected nodes worked; someones I had to go so far as to factory reset them, and configure them from scratch; and once I had to factory reset all three.
I was engaged in just such an exercise yesterday when I found that the third and last node would not connect. The error message claimed that the node was too far from the primary wifi point, though I knew it wasn’t. I also knew that once you get that particular error, no amount of factory resets will make it work again. So I decided to do something I’ve only done a handful of times in my entire life: call support.
You can initiate a support call right from the Google Wifi app, and after a surprisingly tolerable interactive voice response system, I was talking to a polite and attentive human. I was initially worried when he began suggesting a series of workarounds (sometimes it works when you connect to the setup network manually; try turning bluetooth off until the app turns it back on; let’s try connecting your Google Wifi directly to your router with an ethernet cable; etc.).
After all of his tricks were exhausted, and after I approved an authorization prompt sent to my phone, he brought up my network’s configuration (which I found simultaneously unsettling and impressive). That’s when we finally started to make some progress. He realized very quickly that my OnHub had a non-standard IP address, and that a device I hadn’t used in over a year was configured for priority access (which shouldn’t be possible; priority access is supposed to time-out after one hour). My OnHub had clearly fallen victim to multiple as-of-yet unpatched bugs.
At that point, there was no question that the best way to proceed was to factory reset everything: my OnHub, and all three of my Google Wifi nodes (everything but my modem). Perhaps in anticipation of just such measures, the Google Wifi app has a single button to do just that.
About five minutes later, I was setting up my entire wireless network from scratch, and this time, everything went smoothly. Each node connected relatively quickly, and twenty-four hours later, all diagnostic lights are still white (which means everything is healthy).
My best guess is that if you’re setting up a brand new Google Wifi network from scratch, you probably won’t have any problems. But if you’re using Google Wifi to extend an existing network whose primary wifi point is an OnHub that has been accumulating misconfigurations over the course of a year and a half with only a handful of reboots, you should probably nuke everything, and set it all up from scratch.
My main concern was that I would have to reconnect all my devices to my network — an incredibly frustrating and mind-numbing exercise — but using the same network name and password allowed all my devices to seamlessly reconnect. (I’ve found that I can get away using the same SSID and password without any of my devices noticing as long as I’m not actually changing networking hardware. If you’re installing a new router, you’ll probably find that some devices will reconnect while others will have to be set up again.)
Although I need to add several hours of my life to the $299 cost of a Google Wifi three-pack, I intuitively knew what I was getting into by investing in such complex technology so early on. And now that it’s all properly set up, and every single device in my house is reporting a strong wifi signal, I finally feel like it was worth it.
Update (4/29/2017): Whatever you do, don’t directly connect more than one of your Google Wifi nodes to your network.
If one of your Google Wifi extension nodes (as opposed to your primary Wifi access point) happens to be close to a network drop, you might be tempted, as I was, to use the included network cable to connect it directly to your network thinking that it will extend your wireless network and route traffic through the wired network simultaneously. Take my advice: do not do it.
There are two reasons why this is a terrible idea:
- It doesn’t actually work. It seems reasonable to me that if a node has a direct connection to the network, it would route traffic that way rather than through other wireless nodes since a physical cable would clearly be faster. But a mesh speed test indicates that assumption does not hold. In fact, the node that I connected directly to my network (the one in my office where I ran a gigabit Ethernet cable into a router so I’m not using wireless on my main computers) has the slowest connection of all my nodes. Apparently mesh networking — at least Google’s implementation of it — only routes traffic wirelessly until that traffic gets to your primary wifi point. No end-arounds allowed.
- But an even better reason not to try this is that it screws your networking up in a big way, and in fact, might be responsible for most of the problems I’ve been having with Google Wifi. After my entire wireless network went down yet again, I finally made the connection that any configuration I did before plugging the node in my office into the router worked fine, and any configuration I did afterwards was prone to failure. Apparently other nodes sometimes thought that the node in my office was the primary node — even though it was explicitly configured as an extension. What ensued were nonsensical error messages, and IP address madness. After noticing the pattern, I went down to my office, removed the cable, and I was immediately rewarded with a flawless setup experience. And my guess is that the next time a software update or power failure causes the network to reboot, everything will come back online as expected, and I won’t come home to a house-full of Cylon-red error LEDs.
In other words, when it comes to Google Wifi, don’t try anything fancy. Mesh networking is already fancy and complex enough. All my attempts to make it fancier and more complex only made things worse. Which is basically the story of my life, and a lesson I seem to have to keep learning over and over again.