Direct answer
For the Ring Video Doorbell Wired, zone geometry, travel direction, sensitivity, lighting, battery sleep and network delay matter. First, walk a repeatable path and compare event timestamp/first frame.
What this covers
- Ring Video Doorbell Wired (5AT3T5)
- Ring device; wired/battery power, Chime/Alarm integration, subscription and Wi-Fi band vary.
- The specific fault this record addresses: misses motion or records too many events
What it does not cover
- ×The same symptom on a different Ring product line, which has its own record and its own cited source
- ×An on-screen error code whose meaning has not been checked against this exact model's manual
- ×Live electrical, gas, sealed-system, internal battery-cell or structural repair — a technician boundary, not a self-service step
Differential
What actually causes this, and how to tell them apart
These are ordered by how often each one is the answer, not by how easy it is to try. The point of the middle column is that two causes producing the same headline symptom rarely produce the same detail — that detail is what tells you which one you have before you change anything.
- 1
The subject travels toward the camera rather than across it
What separates it People walking past are caught reliably; people walking straight up the path are missed or caught late. Motion analysis measures change between frames, and approaching movement changes far fewer pixels than crossing movement.
How to confirm Walk the same distance across the view and then directly toward it. A large difference in reliability confirms geometry, and aiming the zone across the travel path fixes it.
- 2
The zone excludes where the event actually happens
What separates it Events are missed consistently in one part of the frame. Zones drawn to reduce false alerts frequently cut out the approach as well.
How to confirm Compare the zone outline against the first frame of a missed event, if one exists. Where nothing was recorded at all, walk the path and check which part of the frame the zone covers.
- 3
Distance beyond the reliable detection range
What separates it Subjects are detected close in and missed further out, at a fairly consistent distance. Every motion system has a range at which a person occupies too few pixels to register.
How to confirm Walk the same path at two distances. A consistent cut-off is range, and it is fixed by moving the camera or narrowing the view, not by raising sensitivity.
- 4
Environmental triggers rather than people
What separates it Too many events, clustered by time of day or weather. Headlights, shadows tracking the sun, rain, snow, moving foliage and insects drawn to the infrared illuminator are all genuine detections of things nobody wants.
How to confirm Open the first frame of several unwanted events. What is in that frame names the trigger, which is far faster than reducing sensitivity blindly.
- 5
Insects at the illuminator
What separates it Night events only, often many, with a blurred pale shape crossing very close to the lens. The infrared illuminator attracts insects and a moth inches from the lens fills the frame.
How to confirm Check the first frame of the night events specifically. This is a night-only, close-range pattern and does not respond to zone changes.
- 6
A person-detection tier is filtering events out
What separates it Motion happens and no alert arrives, but the event exists in the history. Person, package and vehicle filters suppress everything they do not classify.
How to confirm Compare the recorded events against the alerts received. Events present without alerts is filtering, not detection.
- 7
Low contrast between the subject and the background
What separates it Detection is unreliable in specific lighting — dusk, snow, a subject in dark clothing against a dark background. Motion analysis needs contrast, and contrast is a property of the scene.
How to confirm Compare reliability in daylight, at dusk and at night for the same path. A dusk-specific failure is contrast, and adding light at the subject addresses it where settings do not.
- 8
A cooldown period between events
What separates it The first event of a sequence is captured and the next few are not, then detection resumes. Several devices enforce a minimum interval between recordings to protect battery and storage.
How to confirm Trigger events a few seconds apart and check how many are recorded. A fixed gap is a cooldown setting, not a missed detection.
- 9
A passive infrared sensor rather than video analysis
What separates it Detection depends on heat crossing the sensor's field, so it misses subjects behind glass, is unreliable in hot weather when the background approaches body temperature, and is triggered by heat sources rather than movement.
How to confirm Check whether the device detects through a window at all. A total failure through glass identifies a passive infrared sensor and reframes every other symptom on this list.
Before you touch a setting
Record this first — changing settings destroys the evidence
Every item below stops existing the moment a reset, re-pair or settings change is made. Written down first, they are what separates the causes above; recovered afterwards, they are guesswork.
- One repeatable walk — same path, same speed, same time of day — because comparing two different walks proves nothing about a setting change.
- Whether the missed events appear in the history at all. Missing entirely is detection; present without an alert is filtering or notification.
- The first frame of several recordings, which shows whether events start late rather than being missed.
- The direction of travel through the frame — across the view or toward the camera — for the events that fail.
- The distance at which detection becomes unreliable, walked and noted rather than estimated.
- The time of day and the weather for clusters of unwanted events.
- The current zone outline, saved or photographed before it is changed, so a worse result can be reverted.
Walk one repeatable path before changing any setting
ReversibleSame route, same speed, same time of day. Every comparison below depends on the trigger being constant, and two different walks cannot tell you whether a setting change helped.
Check whether the missed events exist in the history
ReversiblePresent in the history but not alerted is a filtering or notification problem and belongs on a different page. Absent entirely is genuine detection failure. This single check prevents most of the wasted effort on this symptom.
Look at the first frame of several recordings
ReversibleIf the subject is already mid-frame, the event was detected late rather than missed — that is wake latency, and raising sensitivity does not shorten it. If the subject is at the edge, timing is fine and the problem is elsewhere.
Test travel across the view against travel toward the camera
ReversibleMotion analysis measures change between frames, and approaching movement changes far fewer pixels than crossing movement. A large difference between the two confirms geometry, which is fixed by aiming rather than by settings.
Establish the distance at which detection becomes unreliable
ReversibleWalk the same path close in and further out. A consistent cut-off is range: the subject occupies too few pixels to register. Moving the camera or narrowing the view addresses that; sensitivity does not.
Aim zones across the travel path, not along it
ReversibleA zone drawn over the approach catches a subject who barely changes pixel to pixel. A zone drawn across their route catches them in the first frames. Same sensitivity, materially different result.
Open the first frame of several unwanted events
ReversibleFor too many alerts, what is in the first frame names the trigger — headlights, shadow movement, rain, foliage, or an insect at the illuminator. Each has a specific fix, and blanket sensitivity reduction loses the events you wanted.
Change one variable at a time and re-walk the same path
ReversibleZones, sensitivity, range and filters interact. Changing several together produces a result that cannot be attributed to any of them, which is how a working configuration gets tuned into a broken one.
Verify at day, at night and at the original distance
ReversibleDetection that works in daylight at ten feet is not detection. Contrast falls at dusk, illumination limits range at night, and the distance you actually care about is the one you started with.
Confirm the change did not silently narrow coverage
ReversibleA configuration that ends the false alerts by no longer detecting anything is not a fix. Walk the path you originally cared about, at the distance you cared about, and confirm it is still caught.
Model-specific
What is true of this model and not of its siblings
Generic advice for the product line fails here. Each item below is a property of this specific model family that changes which of the steps above apply to you.
- Model scope
- 5AT3T5. Ring device; wired/battery power, Chime/Alarm integration, subscription and Wi-Fi band vary.
- Power — HARDWIRED (needs doorbell wiring)
- This is the WIRED Ring doorbell — it has NO battery and MUST be connected to existing doorbell wiring (8–24V AC transformer) to work. So 'it won't charge' does not apply (there is no battery), and a dead doorbell is a wiring/transformer issue: check the transformer voltage and that the existing chime/wiring supplies enough power.
- Wi-Fi — 2.4 GHz
- Connects to 2.4 GHz Wi-Fi (not 5 GHz on this model). Offline/setup problems are usually the phone on the wrong band or a weak signal at the door.
- Recording needs Ring Protect
- Live view and alerts are free, but video HISTORY (recorded events) requires a Ring Protect subscription — 'my videos aren't saved' is usually no subscription, not a fault.
- Power path
- Low-voltage transformer through the existing doorbell circuit. The transformer's VA rating, not its age, decides whether the device can transmit at full power; an under-rated one supplies standby current and browns out during events. A mechanical chime in the circuit may require the manufacturer's bypass kit.
- Wi-Fi
- Joins on 2.4 GHz. A phone on 5 GHz cannot hand credentials to it reliably during setup, and a router that steers clients between bands under one network name will produce intermittent joins that look like a hardware fault.
- Siting
- Rated for outdoor installation. Water ingress at the cable entry, corrosion at the contacts and temperature at the extremes of the rated range all present first as intermittent electrical faults, not as visible damage.
- Service tier
- Some capabilities are subscription-gated. A feature that stops working on a date with no other change is worth checking against the plan's renewal before it is treated as a fault.
- Symptom boundary
- This record covers Ring Video Doorbell Wired when it misses motion or records too many events. A different symptom on the same hardware, or this symptom on a different Ring product line, has its own record with its own causes and its own cited source.
Stop boundary
When this stops being a self-service repair
Continuing past any one of these costs more than the repair saves — in safety, in warranty, or in evidence a technician needs.
- !Detection is unreliable at all distances, in all lighting, on a device with good signal and full charge — the remaining variable is the sensor.
- !Aiming the camera correctly would require mounting work at height or on a surface you cannot safely reach.
- !The coverage you actually need would point the camera beyond your own property. Privacy law limits this and it is not a settings question.
- !The device is relied on as the sole detection layer for a security or safety purpose, which no consumer motion system is specified for.
Evidence ledger
Sources behind this answer
Visible sources support the visible claims. Home Product Support records the publisher, the fact used and the review date; community reports can suggest an issue but do not become a published fact on their own.
Where the manufacturer's article stops. Ring publishes this as "Setting up Smart Alerts". Smart Alerts is Ring's control for missed motion and for too many events. Probed 2026-08-21: title-verified. What that article does not carry is the model boundary — it is written for a product line, and 5AT3T5 is the scope applied here. Where a control label, terminal, indicator pattern or reset sequence differs on your unit, the manual for that exact model is the authority, not this page and not the article.
Exact questions
Common follow-ups
My Ring Video Doorbell Wired is dead / won't power on.+
This model has no battery — it runs entirely on your existing doorbell wiring, so a dead unit is a power problem, not a flat battery. Confirm the doorbell transformer supplies 8–24V AC and that the wires are securely connected at the doorbell and the transformer. A transformer that is too low-voltage, a tripped breaker, or a loose wire is the usual cause. It requires wiring by design; if you have no doorbell wiring, a battery Ring doorbell is the alternative.
Why does it miss people walking straight up to the door?+
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.
Should I just turn sensitivity all the way up?+
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.
I get dozens of alerts every night and nothing is there.+
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.
Why does it trigger every time a car goes past?+
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.
It detects fine in summer and badly at dusk in winter.+
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.
Events appear in the history but I get no alerts.+
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.
Two people arrive together and only one is recorded.+
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.
Will it detect through a window?+
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.
Does distance matter more than sensitivity?+
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.
How do I test a change properly?+
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.
I fixed the false alerts and now it misses real ones.+
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.
Can I point it at the pavement outside?+
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.
Does this answer apply to every Ring model?+
No. It is scoped to 5AT3T5. Ring device; wired/battery power, Chime/Alarm integration, subscription and Wi-Fi band vary.
What should I record before troubleshooting motion detection or missed events?+
Record the complete model identifier, exact message or indicator, software/firmware where visible, the operating stage and what still works.
Why is a factory reset not the first step?+
A reset can erase accounts, networks, maps, schedules or preferences without distinguishing motion detection, missed events. The ordered checks preserve that evidence.
When should I stop and use qualified service?+
Follow privacy laws and do not aim beyond authorized property.
Answer for the exact device and software version shown above.