Nest Doorbell (battery) will not stay connected to Wi-Fi

Because it is not supposed to. Google states that with the Nest Doorbell (battery), your existing wired chime will not ring — the press notifies your phone and compatible Google speakers and displays instead. This catches out people who hardwired it specifically expecting the old chime to keep working, and no setting changes it.

Up to 10 feet, from four 850 nm infrared LEDs. That is a short range as published, and it is the single most useful fact about this model at night: a visitor perfectly visible in daylight at the gate can be effectively invisible after dark. It is a specification, not a fault.

No. Google states explicitly that whether it is installed on battery or on existing wiring, this model cannot record continuous 24/7 video history. Hardwiring it changes how it charges, not what it records — which is a common and expensive misunderstanding.

No. It uses a PIR sensor, which detects heat crossing its field, and glass blocks that. The same physics makes it less reliable in hot weather when the background temperature approaches body temperature — both are properties of the sensor, not settings.

Yes — 802.11a/b/g/n/ac on both 2.4 GHz and 5 GHz, with WPA3 supported and Bluetooth Low Energy for setup. Advice that Nest cameras are 2.4 GHz only does not apply to this model.

8–24VAC, 10VA, 50-60Hz. Wiring it powers the chime circuit and recharges the battery; the battery remains the device's power source and still has to be healthy.

It shoots 3:4 — portrait — at 960 x 1280 pixels, deliberately, so a parcel on the doorstep is in frame. It is why footage from this doorbell will not line up with a 16:9 Nest Cam pointed at the same scene, and why its 145° diagonal figure is not comparable with cameras that quote horizontal and vertical separately.

No. Google states it requires the Google Home app and a Google Account, and is not compatible with the Nest app or home.nest.com. Troubleshooting written for older Nest hardware routinely references screens that do not exist for this device.

Up to 3 hours of event video history. A Google Home Premium subscription extends that to up to 30 days, and an Advanced plan to up to 60. Events older than your tier are gone — which is worth knowing before an incident rather than after one.

Because they are not comparable. A phone has a larger antenna, far more transmit power and a battery sized for it. A small smart-home device — particularly a battery one, which throttles its radio to save charge — routinely reports poor signal where a phone reports full. Use the figure the device reports for itself.

Regularity that precise is almost always the router's DHCP lease. The device loses its address, fails to renew it, and drops until something forces a rejoin. A reservation against its MAC address fixes it permanently; rebooting only restarts the clock.

Not usually. Splitting them is the fastest way to prove whether band steering is the cause, and once proved, most routers allow the device to be pinned to a band without keeping the names separate. Keep the split only if pinning is unavailable.

Only if the problem is genuinely range. An extender on a congested channel adds another talker to the same congested channel and can make throughput worse. Establish whether you have a range problem or an interference problem first — they look identical from the app and have opposite fixes.

Two seasonal effects overlap. Doors and windows stay shut, which attenuates the path, and cold reduces battery capacity sharply on outdoor hardware. Both push a marginal connection over the edge, which is why a device reliable all summer starts failing in a cold snap.

It is probably associated with a different node. Mesh systems rarely force a client that has already joined to move, so a device can be inches from one node and talking to one across the house. Power-cycling it beside the intended node forces a fresh association.

Check the security mode first. WPA3-only, IoT client isolation and DNS filtering have all changed defaults across firmware generations, and a device that requires WPA2 will fail against a WPA3-only router with no message that says so.

Fewer than most people assume — consumer routers have finite client tables, and exceeding one produces drops with no error anywhere. The tell is that a device drops when a new device joins, and which one drops varies.

Considerably. Metal, masonry, foil-backed insulation, wire-reinforced glass and low-emissivity window coatings all attenuate 2.4 GHz far more than plain distance. A large change in reported signal over a short move identifies an obstruction rather than range.

Longer than the previous drop interval. A device that used to drop every two days and has now run for ten minutes has proved nothing. This is the single most common way an unfixed Wi-Fi fault gets declared solved.

Yes, and predictably. Several battery devices reduce radio transmit power as charge falls, so a connection that is fine at 90% fails at 30% with no change to the network. A drop that lands at a repeatable percentage is this.

A DHCP reservation at the router is better than a static address set on the device. The reservation keeps the router in charge of the address pool, so it cannot hand the same address to something else — which is the failure a manually set static address invites.

That is a genuinely useful result. The radio link, the credentials and the band are all fine, so everything in this page about signal and placement is ruled out. What remains is the path from the router onward — DNS filtering, a firewall rule, or the provider's own service.

No. It is scoped to GA01318. Google Nest/Home device; Matter/Thread role, wired/battery power, subscription and Google Home migration vary.

Record the complete model identifier, exact message or indicator, software/firmware where visible, the operating stage and what still works.

A reset can erase accounts, networks, maps, schedules or preferences without distinguishing Wi-Fi, disconnecting. The ordered checks preserve that evidence.

Do not weaken router security for a legacy device without isolation.