A Nest Hub Max with Thread border router duty is supposed to disappear into the background. When credentials mismatch, Google Home acts like your hub speaks a different dialect than your Matter-over-Thread devices — commissioning loops, devices stuck on Connecting, or accessories that work in the vendor app but not in Google Home.

Credential mismatch usually follows a predictable story: new router, renamed Wi-Fi, factory reset of one hub but not others, or adding a second Thread border router without letting the fabric settle.

Recognize mismatch vs. ordinary Wi-Fi trouble

Wi-Fi trouble affects cameras and speakers streaming video. Credential mismatch hits Thread and Matter devices first while pure Wi-Fi plugs may still respond.

In Google Home, open Devices → Hub → Settings and confirm the Nest Hub Max shows as a Thread border router where your account tier supports it. If Thread devices dropped immediately after a hub software update, note the version — mismatches sometimes clear with a follow-up patch rather than hardware replacement.

Compare behavior in the device maker’s app. If Eve, Nanoleaf, or another Thread brand shows connected there but Google Home shows Offline, the Thread dataset on the hub is the prime suspect.

Stabilize the network underneath

The phone running Google Home must share the same home LAN as the Nest Hub Max. Guest networks, VPNs on the phone, or DNS filters that block Google device endpoints can mimic credential errors.

If you use separate 2.4 GHz and 5 GHz names, keep hubs on the SSID Google documented during setup — usually the main network, not a guest VLAN.

Reboot the primary router, then the Nest Hub Max (Settings → Reboot in device settings). Wait fifteen minutes before re-adding anything.

Align Thread credentials conservatively

One fabric owner. Matter and Thread fabrics have an owner controller. If you also commissioned devices into Apple Home or SmartThings, pick which controller owns troubleshooting for this session. Sharing is possible, but fixing mismatch requires focusing on one primary app first.

Update hubs before accessories. Install Nest Hub Max firmware, then update affected accessories from their native apps. Reverse order often recreates mismatch.

Remove broken Matter entries. In Google Home, delete ghost devices that never finished commissioning. Reset the physical device only per the manufacturer guide, then recommission with the hub awake and nearby.

Avoid parallel border router fights. If you have Nest Hub Max, Nest Wi-Fi Pro, and Apple Home hubs in the same house, Thread can legally multi-home, but troubleshooting is harder. Temporarily power down non-Google border routers while fixing Google-side mismatch, then reintroduce them one at a time.

Factory reset is last. Google’s hub reset loses local preferences. Do it only after network and app cleanup failed, and only when you can recommission devices afterward.

Know when mismatch is not the real problem

Account region changes, Workspace vs. personal Google account confusion, or a home deleted and recreated under a new structure can look like Thread errors. Verify you are in the intended home in Google Home and that other household members did not remove the hub.

If the Hub Max touchscreen is unresponsive or audio distorts, service the hardware — do not chase Thread certificates on a failing board.

Prove credentials match again

Commission one simple Matter device — a plug or bulb — while standing next to the Nest Hub Max. It should finish within a few minutes. Share it to a second controller only after Google Home shows stable control for an hour. Run a routine that includes the new device and an older Thread accessory; both should execute without Delayed banners.

Official sources