Ring Video Doorbell Pro 2 is offline or unavailable

Yes — it is 802.11 b/g/n/ac and supports both 2.4 GHz and 5.0 GHz, unlike most Ring hardware. There is one catch worth knowing: Ring specifies 5 GHz support on channels 100 and above. A router whose 5 GHz radio operates below channel 100 will not present this doorbell with a 5 GHz network it can join, which looks exactly like the device not supporting the band at all.

An existing doorbell system at 16–24V AC, 10–40 VA, 50/60Hz, or the DIN Rail Transformer supplied in the box at 24V DC, 0.42A, 10W. Ring states explicitly that halogen and garden-lighting transformers must not be used and that third-party DC supplies must not be used — this is a stated safety limit, not a performance recommendation.

It uses 3D Motion Detection, which measures range rather than relying only on pixel change between frames. Head-on approach is the hardest case for pixel-change analysis, which is why a battery camera misses it and this model does not. It also means zone advice written for Ring's battery cameras does not transfer directly.

Ring recommends a minimum of 2 Mbps upload per device. On a slower connection the encoder lowers bitrate to fit, so the picture goes soft and stutters — that is the specified behaviour at insufficient bandwidth, not a camera fault.

−20.5°C to 48.5°C, weather resistant. A fault that appears only in a cold snap or only in direct summer sun is worth checking against that range before it is treated as a hardware failure.

The 150° vertical field of view is the point of this model — it is framed head-to-toe so that a parcel on the step is in shot. Mounted at a height chosen for a conventional doorbell, most of that vertical range points at nothing. The mounting height and the wedge or corner kit are what recover it.

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.

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.

That is a power fault presenting as a network one. The press raises the current draw past what the transformer can supply, the device browns out, and it reappears afterwards. Check the transformer's actual rating and whether the chime needs the manufacturer's bypass kit.

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 5AT2S2. Ring device; wired/battery power, Chime/Alarm integration, subscription and Wi-Fi band 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.