Google's new Nest Wifi is notable largely for two things—having a built-in smart speaker and digital assistant in every node and not using the newest Wi-Fi technology at all.
We still don't know exactly what chipsets are used in the replacement for Google Wifi; Google's not telling, and the company has submitted confidentiality letters to the FCC that kept it from needing to release photographs of the devices' boards for now, as well. All we know for sure is that the Nest Wifi Points are AC1200 (like the original Google Wifi) and the Nest Wifi Router is AC2200. Consumer AC speed ratings are largely bogus, but this should translate into one 2.4GHz 2×2 radio and one 5GHz 2×2 radio on the Points as well as one 2.4GHz 2×2 radio with two 5GHz 2×2 radios on the Nest Router.
We also know that Google decided to go with Wi-Fi 5 in the new kit rather than Wi-Fi 6. Google wasn't the first to make that call—Amazon's new Eero models also continue to use Wi-Fi 5 chipsets—but Google's rationale for the use of the older technology raised eyebrows at Ars Orbiting Headquarters. When VentureBeat asked Nest Wifi product manager Chris Chan to explain the lack of Wi-Fi 6, he pointed to both cost and performance. He said, "You do see a lot of routers with Wi-Fi 6 built in, but it charges quite a bit of a premium in order to get that, and in fact, you need to have Wi-Fi 6-compatible other devices in order for it to be a faster experience,"
So far, we're pretty much on board with Chan's explanation. We are also skeptical of the real-world benefits of a Wi-Fi 6 router in an ecosystem where both customers and their adjoining neighbor networks will be almost entirely populated by Wi-Fi 5 and 4 devices. With that said, although most of Wi-Fi 6's anti-congestion features are only applicable when all or most devices present support 6, spatial frequency reuse—Wi-Fi 6's ability to "use its inside voice" and transmit quietly to nearby devices when farther-away devices are talking—could be of real benefit both in communication with client devices and backhaul from node toRead More – Source
