Ring Video Doorbell Pro 2 does not respond to voice control

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.

That exonerates the microphone, the wake word and the service entirely — the problem is the device link or the name. Ask the assistant to list what it knows and use exactly the name it reports back, which is often not what the manufacturer's app displays.

You almost certainly have two devices sharing a name or a room, which the assistant cannot disambiguate. This stays invisible until a command is ambiguous. Listing the devices the assistant knows finds it, and renaming one is the whole fix.

Account links expire — commonly on a password change or a platform migration. The device is not the broken part, so unlink and relink the account rather than removing and re-adding the device, which would discard its settings for nothing.

That is intent matching, not the microphone — the words were transcribed and matched to a different action. What the assistant said back is the diagnostic here, and the exact phrasing matters, so record the command verbatim rather than paraphrasing it.

Voice profiles and household membership gate both personal results and some device control. Running the identical command as each person is the test, and the answer is a membership setting rather than anything on the device.

Where a platform allows it at all, it normally requires a spoken code, and many restrict it entirely. That restriction is deliberate: a voice command is audible through a door and by anyone in the room. Voice should never be the only way to operate a lock.

Not as a first step. Removing and re-adding a device discards its name, room, automations and shares — all to fix a link between two accounts that unlinking and relinking would have repaired without touching the device at all.

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 voice control, Alexa, Google. The ordered checks preserve that evidence.

Do not disclose voice history or account credentials.