Ring Video Doorbell Pro 2 will not stay connected to Wi-Fi

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.

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.

Then this is not a Wi-Fi fault. The press raises current draw past what the transformer supplies, the device browns out and rejoins afterwards. Check the transformer's actual rating at the transformer, and whether the installed chime requires the manufacturer's bypass kit.

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.

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 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 Wi-Fi, disconnecting. The ordered checks preserve that evidence.

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