Ring Battery Doorbell Plus misses motion or records too many events

Yes, to an existing doorbell system at 8–24 VAC, 50/60Hz, 5VA to 40VA — note the 5VA lower bound, which is lower than the wired Pro models require. Hardwiring trickle-charges the pack rather than replacing it; the battery remains the device's power source and still needs to be healthy.

No. It is 802.11 b/g/n at 2.4 GHz only. This is a real difference from Ring's wired Pro doorbells, which are dual-band — so advice that a Ring doorbell can use 5 GHz does not apply to this model, and a phone on 5 GHz will fail to hand over credentials during setup.

Ring specifies the Solar Charger at 5.2Vdc, 100mA or 109mA and the Solar Panel at 5Vdc, 380mA, 480mA or 800mA. Ring warns that incompatible power sources can damage the device and cause electric shock, so this is one of the places where a generic third-party accessory at the right nominal voltage is genuinely not equivalent.

Ring states 2.5 Mbps for optimal performance — more than the 2 Mbps quoted for the wired Pro. A battery device throttles its radio to protect runtime and so has less margin, which is why the same connection can be adequate for a wired Ring doorbell and marginal for this one.

This model uses Advanced Motion Detection — pixel-change analysis — rather than the radar-assisted 3D Motion Detection in Ring's wired Pro doorbells. Head-on approach changes the fewest pixels, so it is the hardest case for this model in particular. Aiming zones across the approach rather than along it is the fix available here.

Yes — it is a Quick Release Battery Pack, so it can be charged indoors while the doorbell stays mounted, and a second pack removes the downtime entirely. That is a meaningful difference from Ring models with an internal battery, where the whole device has to come down to charge.

−20.5°C to 50°C, weather resistant. Usable battery capacity falls sharply toward the cold end, so runtime that collapses in a cold snap and recovers afterwards is the battery behaving as expected rather than failing.

Because motion analysis measures change between frames, and someone approaching changes far fewer pixels than someone crossing. It is the hardest case for this kind of detection. Aiming the zone across the path they travel — rather than along it — fixes it at the same sensitivity.

That is a late start, not a miss, and it is wake latency on a battery device rather than sensitivity. Raising sensitivity does not shorten the wake time. Where the first seconds matter, a continuously powered camera is the actual answer.

Rarely. High sensitivity produces more events of the same things you already do not want — headlights, shadows, rain, foliage — while doing little for the geometry problems that cause genuine misses. Establish why events are missed before changing the setting that governs how easily they trigger.

Open the first frame of a few. Night-only events with a pale blur very close to the lens are insects at the infrared illuminator — the illuminator attracts them, and a moth inches from the lens fills the frame. That does not respond to zone changes.

Headlights sweeping the scene are a genuine change in the image, and at night they are a large one. This is what activity zones and vehicle filtering exist for — and it is worth confirming from the first frame that headlights, rather than the car body, are the trigger, because the fixes differ.

Contrast, not sensitivity. Motion analysis needs the subject to differ from the background, and dusk plus dark clothing against a dark background is the worst case there is. Light at the subject addresses it where settings cannot.

Then detection is working and something downstream is filtering. Person, package and vehicle detection suppress everything they do not classify, and notification settings suppress the rest. Neither is a detection problem.

Check for a cooldown interval. Several devices enforce a minimum gap between recordings to protect battery and storage, so a second event moments after the first is not recorded at all. A fixed gap between captures is the tell.

Not if it uses a passive infrared sensor, which detects heat and is blocked by glass entirely. Testing whether it detects through a window at all is worth doing early — a total failure identifies the sensor type and reframes every other symptom.

Usually yes. Beyond a certain range a person simply occupies too few pixels to register as motion regardless of how sensitive the setting is. Walking the same path at two distances finds the cut-off in two minutes.

Re-walk the identical path — same route, same speed, same time of day — after changing exactly one thing. Two different walks compared against each other prove nothing, and changing two settings at once produces a result you cannot attribute.

That is the usual outcome of reducing sensitivity or shrinking zones to solve a trigger problem. The trigger had a specific cause worth identifying from the first frame; suppressing everything to suppress it costs the events you installed the camera for.

Privacy law limits how far beyond your own property a camera may record, and it varies by jurisdiction. This is a legal boundary rather than a settings question, and it is worth resolving before mounting rather than after.

No. It is scoped to 5F77E9. 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 motion detection, missed events. The ordered checks preserve that evidence.

Follow privacy laws and do not aim beyond authorized property.