Nest Cam (battery) is offline or unavailable

Google specifies a single motion sensor with a 110° horizontal field of view, effective up to 25 ft (7.5 m). Beyond that distance detection is outside specification, and no sensitivity setting extends it — which is the answer to most 'it misses people at the end of the drive' reports on this model.

Up to 20 ft (6.10 m), from six high-power 850 nm infrared LEDs. That is twice the published reach of the Nest Doorbell (battery) at 10 feet, so the two models genuinely are not interchangeable for a dark approach.

It uses a proprietary magnetic connector rather than a standard USB port, so a generic cable is not a substitute. A magnetic connector that is not seated squarely is also a real cause of intermittent charging on this camera, and it looks exactly like a failing battery.

Only under two conditions together: it must be used plugged into continuous power, and you need a Google Home Premium Plus subscription. That gives up to 10 days of 24/7 history. On battery power alone, continuous recording is not available no matter what plan you hold.

Yes — 802.11a/b/g/n on both 2.4 GHz and 5 GHz, with WPA3 supported. Generic advice that smart-home cameras are 2.4 GHz only does not apply here.

Different sensors and different shapes. This camera is 2 MP, 16:9 landscape, 130° diagonal; the Nest Doorbell (battery) is 1.3 MP, 3:4 portrait, 145° diagonal. Pointed at the same scene they produce genuinely different framing and detail, and neither is faulty.

Up to 3 hours of event-based video history. A Google Home Premium subscription extends it to up to 60 days. Anything older than your tier is gone, which is worth understanding before you need to retrieve something.

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 — so older Nest troubleshooting references screens this device does not have.

At the router or the hub, not at any device. Simultaneous failure across unrelated hardware is the signature of a shared dependency, and re-adding devices one by one before that dependency is fixed is work you will have to repeat.

It rules out the router, the internet connection and the provider — all of which would take the others with them. What remains is that device's own power, its own radio path, and its own account state.

That interval is the clue. A drop that recurs on a roughly fixed schedule usually tracks the router's DHCP lease. A reservation for the device's MAC address at the router removes it permanently, where rebooting only resets the clock.

Both, in sequence. Marginal signal degrades first — slower live view, late notifications, missed events — and only then drops out. A device that went straight from perfect to absent is more likely a power or credential problem than a signal one.

Because they still hold the old network's name and password, and nothing can tell them otherwise. Setting the new router to the old network name and password is often faster than re-adding every device, and is worth doing before the first re-add.

Then the local link is probably fine and the break is further along — between the router and the provider, or at the provider itself. Check the provider's status page and the router's internet connection before doing anything to the device.

Check the manufacturer's stated operating range for Nest Cam (battery). Below it, capacity falls sharply and an outdoor device that was reliable in mild weather starts dropping off in a cold snap — which is why this failure is seasonal and looks like a hardware fault.

Not as a first step, and not during a provider outage. A reset discards local settings and, on a shared device, can discard other people's access. Establish what is actually broken first — reset is a recovery action, not a diagnostic one.

No, and it is rarely necessary. Deleting a home or hub destroys every automation, permission and share attached to it. Remove and re-add the single failed accessory instead.

Router firmware updates can turn on band steering, IoT client isolation or DNS filtering that was previously off. Compare the current settings against the defaults for those three specifically — a device that worked for a year and stopped on an update date is describing a router change, not a device failure.

Router first, fully up, then the hub, fully up, then accessories. Restarting everything simultaneously produces address conflicts and rejoin storms that look exactly like the original fault, which is how a five-minute check turns into an afternoon.

Give the router several minutes to finish handing out addresses, and battery devices longer still — several report on a duty cycle and will not check in immediately. Judging at thirty seconds produces false failures and unnecessary resets.

It can. Consumer routers have finite client tables, and a household with dozens of connected devices can exceed one. The symptom is that a device drops whenever a new one joins, which reads as random until the pattern is spotted.

That is a useful, specific result: the device joined the local network successfully, so credentials, band and signal are all fine. The break is between the router and the provider — DNS filtering, a firewall rule, or the provider's own service.

No. It is scoped to GA01317. 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 offline, unavailable. The ordered checks preserve that evidence.

Protect security devices and avoid deleting the entire home for one offline accessory.