Google Nest Devices Receive Silent Thread 1.4 Update to Simplify Smart Home Pairing

According to Android Authority, Google is quietly rolling Thread 1.4 across its Nest Hub family and the Nest WiFi Pro — a silent, unannounced firmware push that users first surfaced on Reddit, and one that finally drags Google's smart displays onto the same networking standard the Google TV Streamer picked up earlier this summer. If you've ever fought a stubborn third-party device refusing to commission into a Google mesh, this is the upgrade you've been waiting on without knowing it.

The credential handshake from hell

Anyone who's tried to onboard a Matter-over-Thread device into a Nest-branded mesh knows the ritual: the sensor gets enrolled, the commissioning token gets generated, and then the whole thing stalls. The device sits in limbo because the existing mesh refuses to hand off its security credentials in a format anything outside Google's garden can parse. The root cause is Thread 1.3, a standard Google has been stubbornly clinging to while the rest of the industry moved on. Thread 1.4 standardizes credential sharing at the protocol layer, so an Eve sensor, an Aqara actuator, and a Nanoleaf strip can negotiate the same auth payload without the mesh operator having to babysit the handshake. No more manual re-commissioning after a router swap. No more orphan nodes that show up in the Google Home app but refuse to talk to anything else in the house.

What's actually shipping

Per the Reddit reports captured by Android Authority, the devices picking up the upgrade include the original Nest Hub, the Nest Hub Gen 2, the Nest Hub Max, and the Nest WiFi Pro — which doubles as the Thread border router for most Google-centric setups. The rollout is silent: no changelog, no blog post, no support page, just a firmware push flipping the Thread stack to 1.4 in the background. Beyond easier pairing, the spec also trims response latency and cuts down on random device dropouts — two complaints that have dogged Thread meshes since the protocol went mainstream. Google hasn't commented, and one commenter nailed the mood: "You think they would announce this somewhere."

What to check in your own stack

If your home runs a Nest Hub or a Nest WiFi Pro as the border router, open Google Home, dive into the device settings, and verify your Thread radio version has ticked over to 1.4. The push is staged, not simultaneous, so if it hasn't landed yet, force a check by rebooting the hub and giving it a few hours. And if you've been holding off on commissioning non-Google Matter devices because the pairing flow was a coin flip, this is the moment to retry. With credential exchange standardized at the protocol layer, the walled garden excuse just got a lot thinner — and the automation blueprints that depend on mixed-vendor Thread devices finally have a clean foundation to run on.