Ring Integration abandoned' lookign for dev to finish existing PR to fix snapshots - been ready since Nov 2025

Ltek · January 24, 2026, 7:13pm

Ring camera snapshots have been broken since day one… HusainCode created a fix and a PR that was never completed, and been silent since Nov 2025

PR… Fix ring camera last recording snapshot extraction by HusainCode · Pull Request #156905 · home-assistant/core · GitHub

Documented…

github.com/home-assistant/core

Ring Integration : Snapshots not working

opened 04:32PM - 04 Nov 25 UTC

Ltek

integration: ring

### The problem Ring snapshots do not work while Tapo and Blue Iris camera snap…shots work fine. It seem that HA is not capturing a snapshot from the Ring Doorbell. ### What version of Home Assistant Core has the issue? core-2025.10.4 ### What was the last working version of Home Assistant Core? _No response_ ### What type of installation are you running? Home Assistant OS ### Integration causing the issue Ring ### Link to integration documentation on our website https://www.home-assistant.io/integrations/ring ### Diagnostics information For many months I've been using Ring and other camera integrations (Tapo, Blue Iris) I have a Ring subscription and Live Video for fine with Ring and all my integrations so I know the streams work properly. Taking Snapshots work with Tapo and Blue Iris integrations but **Does Not Work with Ring** I have tried multiple HA Blueprints that do snapshots, and also some custom made YAML code using [service: camera.snapshot](https://www.home-assistant.io/integrations/camera/) ... Nothing works. HA always pulls an old snapshot, it never takes a new / current snapshot. It is returning a snapshot, but that snapshot is always old, sometimes many hours old ### Example YAML snippet ```yaml [service: camera.snapshot](https://www.home-assistant.io/integrations/camera/) ``` ### Anything in the logs that might be useful for us? ```txt ``` ### Additional information _No response_

github.com/home-assistant/core

Ring Snapshot is not actual

opened 11:15AM - 06 Jul 25 UTC

MrRamsus

integration: ring

### The problem Hi, I have created an automation in Home Assitant for my Ring …Doorbell. My suggestion is to notify me with a snapshot in the message when someone hits the doorbell. For now it works, but the only strange thing that happened, is that the snapshot is not actual. If I walk to the frontdoor, I’m visible on the Live view in HA. But when I create a snapshot via automation, I’m not visable on the snapshot. The file is created and visible on the notification. But the picture doesn’t contain the actual data. I’ve tried several things and add an timestamp as variable, that every picture has an unique filename. But same problem. My automation: [See below] Output filename: `Ring_Snapshot_30-06-25-14-25-49.jpg` Does anyone know how I can fix this issue? Edit: I’ve also tried the option camera.turn_on, before the snapshot will be taken. That looks like the solution, but when I tried to add that option, the snapshot will not be created anymore (also no notification) ### What version of Home Assistant Core has the issue? core-2025.7.1 ### What was the last working version of Home Assistant Core? _No response_ ### What type of installation are you running? Home Assistant OS ### Integration causing the issue Ring ### Link to integration documentation on our website https://www.home-assistant.io/integrations/ring ### Diagnostics information _No response_ ### Example YAML snippet ```yaml alias: Test_Ring description: "" triggers: - trigger: state entity_id: - event.front_door_ding from: null conditions: [] actions: - variables: timestamp: "{{ now().strftime('%d-%m-%y-%H-%M-%S') }}" jpg_filename: Ring_Snapshot_{{ timestamp }}.jpg jpg_path: /config/www/Ring_Snapshots/{{ jpg_filename }} jpg_url: https://HA-URL/local/Ring_Snapshots/{{ jpg_filename }} - action: input_boolean.turn_on metadata: {} data: {} target: entity_id: input_boolean.ring_motion_active - action: camera.snapshot metadata: {} data: filename: "{{ jpg_path }}" target: entity_id: camera.front_door_live_view - action: notify.mobile_app_NAME metadata: {} data: title: 🔔 Ring message: Er is aangebeld bij de voordeur. data: image: "{{ jpg_url }}" actions: - action: URI_RING title: Open Ring app uri: ring:// - action: URI_HA title: Live View (HA) uri: https://HA-URL/dashboard-ring/0 mode: single ``` ### Anything in the logs that might be useful for us? ```txt ``` ### Additional information _No response_

… and several other HS forum threads documenting this bug

I’m not a dev so asking ANY kind dev, including sdb9696 (integration owner) to help the thousands of HA users that have Ring cameras.

If you have the skills, please do a PR for this so we can have a fix.

thank you

From HusainCode’s post…

What was wrong:
The Ring integration kept showing old images because it was grabbing a frame from the last recorded video instead of requesting a fresh snapshot from the camera.
async_camera_image() used ffmpeg.async_get_image() on self._video_url, which always pointed to the most recent motion recording not a live image.
So if the last recording was hours old, the snapshot was also hours old.

What the fix does:
The ring-doorbell library (v0.9.13) already provides async_get_snapshot(), which tells Ring’s API to take a new, real-time photo.
The integration simply wasn’t calling it.

Now:

live_view cameras use async_get_snapshot() → always get a fresh snapshot.

last_recording cameras still use video frame extraction → correct behavior for that camera type.

PR / ticket summary version:
Fixed by switching live_view cameras to use async_get_snapshot() instead of extracting frames from old recordings. The integration was previously pulling from cached videos instead of requesting new snapshots from Ring’s API.