Why your Nest Cam won't connect to your Wi-Fi

Start with the radio, not the router

Google Nest is the hardware brand. Google Home is the platform and the app that hardware registers with. When a camera will not join, the platform is rarely the problem and the radio inside the camera usually is. Google publishes band support per product on its support pages, and the answer changes by region.

The sourcing behind that table is not uniform, and the difference is worth knowing. For the cameras, Google's support page names us in the sentence: 'Europe, Canada, Australia: 802.11b/g/n (2.4 GHz)'. For the Nest Doorbell (battery) it does not name us at all. It puts the doorbell under 'Rest of world: 802.11b/g/n 2.4 GHz Wi-Fi', which is the same answer reached by inclusion rather than by name.

Four things that break setup on an Australian home network

Google publishes no consolidated network-requirements page for Nest setup. The closest thing is a line in a troubleshooting article about its speakers and displays, suggesting you try both bands on a dual-band router. The four causes below are not documented by Google anywhere. They come out of our own support experience, and between them they account for most of the setups we see stall.

Band steering

Your router advertises one network and decides which band each client gets. It will usually push a new device toward 5 GHz, which a 2.4 GHz-only camera cannot join. The camera either never appears in the app or joins and drops out within minutes.

One network name across both bands

Almost every ISP-supplied router in Australia ships with a single network name covering both the 2.4 GHz and 5 GHz bands. Your phone sits on 5 GHz, the Google Home app hands the camera the credentials for the network the phone is on, and the camera cannot see it.

Blocked mDNS and multicast

Device discovery on a local network runs over mDNS and multicast. Plenty of routers, mesh systems and security profiles filter both by default, and the app then reports that it cannot find the camera even though the camera is powered and broadcasting. If your router has a setting named AP isolation, IGMP snooping or block multicast, that is the one to look at.

Guest networks and client isolation

A guest network isolates clients from each other by design, which is the entire point of it. A camera set up on one is unreachable from the phone that set it up, and often from every other device in the house. Use the main network.

How to get a Nest Cam onto your Wi-Fi

This is the order we work through it on a support call.

WPA3 is not the cause

Google's camera and doorbell specification page lists WEP, WPA, WPA2 and WPA3 as supported, and it says so on the Australian version of the page as well as the international one. Two of Google's setup articles still stop their list at WPA2, which reads as a stale setup flow rather than a limit in the hardware.

Older Nest hardware is a different question and we cannot answer it from anything Google publishes. If you have a mixed-age set of devices and you have just turned WPA3 on, an older camera dropping off the network is worth suspecting. Google's own routers make the point: Nest Wifi and Google Wifi default to WPA2, and Google notes that older clients may fail to join once WPA3 is enabled.

When it isn't the network

A Nest camera or doorbell is not a hub of any kind. It cannot commission Matter devices, it carries no Thread radio, and it will not extend anything for the rest of the house. That is a separate question, covered in which Google devices are Matter hubs.

The Australian range is also not the range Google sells in the United States, so a spec sheet, a review or a setup video from overseas may be describing hardware you cannot buy here. If you have worked through the steps above and the camera still will not join a network you know is on 2.4 GHz, the fault is more likely the unit than the router, and that is a warranty conversation rather than a networking one.