Nest Wifi Thread border routers: Pro, 2019 and Google Wifi

Which Google routers carry the radio#

From Google's own tech specs page:

The second and third rows are the ones people get wrong. The 2019 Nest Wifi is widely described as having no Thread support, and Google's spec sheet says otherwise for both the router and the satellite points. Google's release notes back it up: the September 2022 update, firmware 14150.376.32, is listed as "Thread border router support on Nest Wifi router and point". Nest Wifi Pro got the same capability at launch two months later, in the November 2022 release, firmware 1.63.318999.

Google Wifi, the 2016 and 2020 product, is the clean exception. Its spec sheet lists Bluetooth Low Energy and nothing in the 802.15.4 band. The radio is not in the box.

If you are not sure which product you own, the model name on the underside settles it, and the border router finder will tell you what that model does. The cross-vendor picture, including Apple, Amazon and SmartThings hardware, is in the border router guide.

Border router is not the same job as Matter hub#

This is the part worth slowing down for, because Google's spec page states it plainly and almost nobody reads it that way.

A Thread border router is a routing function. It has an 802.15.4 radio and a LAN connection, it moves IPv6 packets between the Thread mesh and your home network, and it advertises the mesh so controllers can find the devices on it. It does not hold your device list. It does not run your automations. It does not know or care which app you use.

A Matter controller is the thing that owns devices: it commissions them, holds the credentials, and exposes them to your home app. Google's controller function lives in Google Home, on specific hardware.

Nest Wifi Pro is both. The 2019 Nest Wifi router and point are, per Google's own spec sheet, border routers whose Matter support is still described as coming. So a 2019 Nest Wifi can carry Thread traffic for devices that a Nest Hub or a Google TV Streamer actually commissioned and controls. It participates without owning.

That is not a defect. It is the architecture working as designed, and it is the same reason a house can have several border routers and one controller. If the words still feel interchangeable, hub, bridge, controller, border router is the page that separates them properly, and what Matter is covers the controller side.

What Google does not publish#

No Thread version. Google's release notes for the Wi-Fi products describe Thread border router support and, in the July 2025 release, firmware 3.76.479819, "Improved and more reliable whole-home coverage with Thread support". Neither statement carries a version number.

That matters because Thread version is not cosmetic. It governs how well multiple border routers cooperate and how credentials move between ecosystems. Elsewhere in Google's range the versions are known and they are not uniform: the border router guide records the Google TV Streamer (4K) moving to Thread 1.4 in June 2026, while Nest Hub 2nd gen and Nest Hub Max were still on Thread 1.3 as of September 2026.

For the Wi-Fi products, treat the version as unconfirmed. If you see a specific Thread version claimed for a Nest Wifi product, check whether the claim traces back to Google, because the release notes do not state one.

The same caution applies across vendors. Amazon publishes no Thread version diagnostics for its hardware either, which is covered in eero as a Thread border router.

What the July 2025 firmware changed, and what it did not#

Firmware 3.76.479819, July 2025, is described by Google as improving whole-home coverage with Thread support. Read that carefully: it is a coverage statement, not a feature statement. It does not announce a new Thread version, a diagnostics view, a device list, or any change to how credentials are handled.

If your Thread devices were dropping before that update and they are still dropping, the update was not aimed at your problem. Coverage improvements help when the failure is distance and signal. They do not help when the failure is two separate Thread networks, which is the most common cause and is covered in why you have three Thread networks and Thread devices dropping, or a split network.

Practical consequences#

If you own a 2019 Nest Wifi, you have more Thread coverage than you probably realised, because the points carry the radio too. That is useful: border routing follows the mesh rather than sitting in one room. What you do not have, per Google's spec page, is a finished Matter controller on that hardware.

If you own Nest Wifi Pro, you have both functions in one box, and credential sharing by QR code, which makes cross-ecosystem commissioning less painful than on hardware that shares nothing.

If you own Google Wifi, updating will not produce a border router. Adding Thread means adding hardware, another border router on the same credentials, not a replacement router unless you were replacing it anyway.

In all three cases, adding a second border router from a different ecosystem is what creates a second Thread network, unless credentials are shared between them. Hardware arriving in the house is the event that usually precedes devices going quiet. Google Home covers what that ecosystem does well and where it stops.