Direct answer
For the Ring Video Doorbell Pro 2, trigger, conditions, controller/hub, permissions and action chain should be tested separately. First, review activity history and trigger the action manually.
What this covers
- Ring Video Doorbell Pro 2 (5AT2S2)
- Ring device; wired/battery power, Chime/Alarm integration, subscription and Wi-Fi band vary.
- The specific fault this record addresses: routine, schedule or automation is not running
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 trigger never fired
What separates it Nothing appears in the activity history at the expected time. Running the action manually works perfectly, which is what convinces people the automation is broken when the action is the one part that is fine.
How to confirm Check the history first. No entry means the trigger, not the action — and every minute spent on the action is wasted.
- 2
A condition was false at the moment it fired
What separates it The history shows the automation evaluated and did nothing. Conditions on presence, time of day, sunset, another device's state or a household member's location fail silently by design.
How to confirm Remove conditions one at a time and re-run. A routine that works with no conditions and fails with one identifies that condition exactly.
- 3
Time zone or location is wrong on the home, not the phone
What separates it Everything runs, at the wrong time — often by a whole number of hours, or with sunrise and sunset offset. The home's location is a separate setting from the phone's, and it defaults to wherever it was created.
How to confirm Check the home or hub's own time zone and address rather than the phone's. Sunset-based automations firing at a consistently wrong hour is this and almost nothing else.
- 4
Presence detection is the trigger and it is unreliable
What separates it Arriving and leaving automations fire late, early, twice, or not at all — and worse for one household member than another. Geofencing depends on the phone's location permission, its background activity allowance and its power state.
How to confirm Compare each member's phone permissions. A geofence needs 'always' location rather than 'while using', and battery optimisation defeats it silently.
- 5
One action failed and stopped the chain
What separates it The first part of a routine happens and the rest does not, consistently at the same point. Actions run in order and a failure partway leaves a half-executed result.
How to confirm Run each action individually. The one that fails alone is the one that is stopping the chain, and it usually has its own separate fault.
- 6
The automation belongs to an account that lost access
What separates it It stopped on a date that matches someone leaving the home, a password change or a device being re-added. Automations are owned, and ownership is not always transferred when a device changes hands within the household.
How to confirm Check which account created the routine and whether that account still has permission to the devices it touches.
- 7
Two automations are fighting
What separates it The result flickers, or the last state does not persist. A schedule and a sensor rule that disagree will each keep applying their own outcome.
How to confirm Look for another routine touching the same device at an overlapping time. This is invisible from either routine's own screen.
- 8
The device was renamed or moved to another room
What separates it The automation exists and references something that no longer resolves. Renaming a device or moving it between rooms breaks rules that referenced it by name or by room.
How to confirm Open the routine and confirm each referenced device still resolves rather than showing a placeholder.
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.
- Whether the automation appears in the activity history at all at the expected time — this single check splits trigger problems from action problems.
- The exact time it should have run and the exact time anything happened, because an offset of whole hours is a time-zone answer.
- The full list of conditions attached to it, before any are removed.
- Which account created the routine, and whether that account still has access to every device it touches.
- Whether it fails always, or only overnight, or only when nobody is home — each points somewhere different.
- For presence triggers, each household member's location permission and background activity allowance.
Read the activity history before changing anything
ReversibleAn entry at the expected time means the trigger fired and the problem is downstream. No entry means the trigger never fired and nothing about the actions is worth investigating. This one look decides which half of the work is real.
Run every action manually, one at a time
ReversibleActions execute in order and a failure partway leaves a half-run routine. Running each alone identifies which one stops the chain, and that action almost always has its own separate fault worth fixing on its own terms.
Check the home's time zone and location, not the phone's
ReversibleThe home has its own location setting and it defaults to wherever it was created. Everything running at a consistently wrong hour, or sunrise and sunset landing wrong, is this and very little else.
Remove conditions one at a time and re-run
ReversibleConditions fail silently by design — presence, time window, sunset offset, another device's state. A routine that works with none and fails with one has told you exactly which condition is false at the moment it matters.
Verify presence permissions on every phone involved
ReversibleA geofence needs 'always' location rather than 'while using', and background activity has to be allowed. Battery optimisation defeats both silently, and the symptom differs per household member because the settings do.
Look for a second routine touching the same device
ReversibleTwo rules that disagree each keep applying their own result, which shows as flicker or as a state that will not persist. This is invisible from either routine's own screen and has to be looked for deliberately.
Confirm every referenced device still resolves
ReversibleRenaming a device or moving it between rooms breaks rules that referenced it by name or room. The routine still exists and still appears valid; it simply points at nothing.
Run it twice at the intended time and state
ReversibleOnce proves it can work. Twice, at the real trigger time and in the real household state, proves it does. Automations that pass a manual test and fail in life are failing on a condition that manual testing never reproduces.
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
- 5AT2S2. Ring device; wired/battery power, Chime/Alarm integration, subscription and Wi-Fi band vary.
- Video
- 1536p Head-to-Toe HD video with colour night vision and Advanced Pre-Roll. The vertical framing is the reason this model is chosen for parcels left on the step, and it is also why a mount angled for a conventional doorbell wastes most of the frame.
- Field of view
- 150° horizontal and 150° vertical. The vertical figure is unusually large and matters when zones are drawn: a zone sized for a 57°-vertical camera covers a fraction of what this one sees.
- Motion detection
- 3D Motion Detection with customisable motion zones — a radar-assisted range measurement rather than pixel-change analysis alone. That is why this model's detection behaves differently from Ring's battery cameras for a subject approaching head-on.
- Power
- Hardwired, either through the included DIN Rail Transformer (24V DC, 0.42A, 10W) or an existing doorbell system at 16–24V AC, 10–40 VA, 50/60Hz. Ring states explicitly that halogen and garden-lighting transformers must not be used, and that third-party DC supplies must not be used.
- Wi-Fi
- 802.11 b/g/n/ac at 2.4 GHz AND 5.0 GHz, with 5 GHz support limited to channels 100 and above. This model is dual-band — the usual 2.4-GHz-only advice for smart-home hardware does not apply to it, and a router whose 5 GHz radio sits below channel 100 will not offer it a usable 5 GHz network.
- Bandwidth
- Ring recommends a minimum upload speed of 2 Mbps per device. Video that is soft or stuttering on a connection below that is behaving as specified rather than failing.
- Operating range
- −20.5°C to 48.5°C, weather resistant. Behaviour outside that range is outside specification, which matters when a fault is seasonal.
- 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.
- 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 Pro 2 when it routine, schedule or automation is not running. 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.
- !The automation is relied on for anything safety-critical — heating for a vulnerable person, medication reminders, access for someone who cannot let themselves in. Consumer routines are best-effort and are not specified for that.
- !The controlling account is inaccessible and the routines cannot be edited or reassigned.
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 "Using Linked Devices". Linked Devices is Ring's automation mechanism; this is the article for one that does not fire. Probed 2026-08-21: title-verified. What that article does not carry is the model boundary — it is written for a product line, and 5AT2S2 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
Does the Video Doorbell Pro 2 work on 5 GHz 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.
What transformer does the Video Doorbell Pro 2 need?+
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.
Why does the Pro 2 detect approaching visitors better than my other Ring cameras?+
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.
How much upload speed does the Pro 2 need?+
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.
What is the temperature range for the Video Doorbell Pro 2?+
−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.
Why does so much of the picture look like empty wall?+
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.
The action works when I run it by hand but the routine never fires.+
That is the clearest possible evidence the action is fine and the trigger is not. Check the activity history — no entry at the expected time means nothing downstream is worth investigating, and running the action manually only confirms the part that already worked.
Everything runs an hour off.+
Check the home's own time zone and address rather than the phone's. The home has a separate location setting that defaults to wherever it was created, and an offset of a whole number of hours — or sunrise and sunset landing wrong — is almost always this.
My arrival routine fires late, or twice, or not at all.+
Geofencing depends on the phone, not the home. It needs 'always' location permission rather than 'while using', and background activity has to be allowed — battery optimisation defeats it silently. That is also why it behaves differently for different household members: their phone settings differ.
Half the routine runs and the rest does not.+
Actions execute in order, and one failing stops the chain. Run each action on its own to find which one fails alone — it will usually have a fault of its own worth fixing independently, and the routine will then complete.
It stopped working and nothing changed.+
Something usually did. Check for a device renamed or moved to a different room, a household member who left, a password change, or a device removed and re-added. Routines reference devices by name and room, and reference the account that owns them.
The light flickers between two states.+
Two automations are fighting over the same device — commonly a schedule and a sensor rule that disagree. Neither routine's own screen shows the other, so it has to be looked for deliberately by checking everything that touches that device in the same window.
Should I delete and rebuild the automation?+
Not before reading the history. A rebuild that happens to work teaches you nothing about which of the four parts failed, and the same cause will take out the next routine you build. Diagnose first, rebuild only if the routine is genuinely corrupt.
Can I rely on this for something important?+
No consumer automation platform is specified for safety-critical use. Trigger, condition, controller and action each fail independently and silently, and none of them alerts you when they do. Anything that matters needs a layer that is designed to fail loudly.
Why did it work when I tested it and not in real life?+
Because a manual test skips the conditions. Presence, time window, sunset offset and another device's state are all true when you are standing there testing and frequently false at the real trigger moment. Test at the intended time, in the intended household state, twice.
Does this answer apply to every Ring model?+
No. It is scoped to 5AT2S2. Ring device; wired/battery power, Chime/Alarm integration, subscription and Wi-Fi band vary.
What should I record before troubleshooting routine or automation?+
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 routine, automation. The ordered checks preserve that evidence.
When should I stop and use qualified service?+
Do not use consumer routines as the sole safety-critical control.
Answer for the exact device and software version shown above.