In the visual editor, open Doorbell features and select either your official
Ring Ding event entity, for example event.front_door_ding, or a Ring-MQTT Ding
binary sensor such as binary_sensor.front_door_ding.
A fresh ring event, an off to on Ding transition, or a newer Ring-MQTT
Ding timestamp while the sensor remains on displays the bell alert for
twelve seconds. If Live is not running, Ring View also offers Open live
view in the shared centered message area. An already active Live session
is left untouched. The alert expires from the original event time; rebuilding
the card does not restart its twelve-second lifetime.
A dashboard card cannot reliably notify your phone while the dashboard is closed. The included Ring View doorbell notification blueprint runs in Home Assistant instead.
-
Import the blueprint and create an automation from it. If it is already installed, import it again and choose Overwrite; existing automations keep their configured inputs.
-
Under Ring View sources, select:
- For official Ring: the Ding event and matching Last recording camera.
- For Ring-MQTT: the Ding binary sensor and matching Snapshot camera.
-
For Ring-MQTT, set the camera's Snapshot Mode to an option that includes Ding. Choose Interval + Ding if you also want periodic dashboard images.
-
Choose the phone registered with the Home Assistant Companion app.
-
Set Dashboard path to the actual view containing your Ring View card, such as
/lovelace/entrance. Replace the example/test path; the blueprint does not create or configure a dashboard for you. -
Select the same Ring View Live camera and Ring View recording source used by the card. The recording source is the official Last recording camera or the Ring-MQTT Event Select—not the Ring-MQTT Snapshot camera selected for the notification preview.
-
If iOS shows an attachment-error thumbnail, set External image address to the full HTTPS address used to reach Home Assistant remotely, for example
https://example.ui.nabu.casa. Ring View then saves the fresh frame under/config/wwwand gives iOS an absolute/local/...image URL. Leave this field empty when authenticated camera-proxy thumbnails already work. -
Choose Notification language (English or Deutsch) and optionally enter a Doorbell name to identify the entrance in the title. Existing automations default to English when these new inputs are not set.
-
Save, then test with a real doorbell press. Confirm phone notification permission is enabled.
- An official Ring or Ring-MQTT Ding sends an immediate Someone is at the
door notification. Repeated Ring-MQTT presses are detected even while its
Ding sensor remains
on. - Tapping the immediate alert or choosing View Live opens Ring View directly in fullscreen Live mode. The viewer retains its normal controls, including Hold to talk when the official Ring Live view camera and two-way audio are configured.
- The automation waits up to two minutes for a new official recording ID or a newer Ring-MQTT Ding snapshot timestamp.
- When a new recording is detected, the same notification says Recording ready and offers View Live and Watch Recording. A fresh snapshot or generic camera update instead says New image available and offers only View Live: an image alone does not confirm a recording is ready.
- Tapping the notification always opens Live, before and after its image update. Watch Recording opens recording mode separately when offered. The preview does not start an extra Ring live session.
- German notifications use Jemand ist an der Tür, Live ansehen, and Aufnahme ansehen, with Aufnahme verfügbar for recordings and Neues Bild verfügbar for other images. An optional doorbell name is appended to the title in either language.
- By default the preview uses Home Assistant's authenticated camera proxy. If
External image address is configured, the blueprint instead writes one
current JPEG per selected camera to
/config/wwwand sends its absolute HTTPS/local/...URL. This works around iOS notification-extension setups that can open the expanded camera view but cannot resolve an authenticated or relative compact thumbnail. If saving the public snapshot fails with a handled Home Assistant service error, the update continues using the authenticated camera proxy. This fallback may retain the original iOS thumbnail limitation, but the text and Live/recording actions remain useful. - If the camera does not publish a new image within two minutes, the immediate notification remains unchanged; an older image is never attached as if it were current.
- Another ring restarts that automation's wait. Both stages use a tag derived from the doorbell entity, so separate doorbells do not overwrite each other's notifications. Automations for the same doorbell still share its tag. After upgrading, dismiss any old alert using the previous shared tag once.
On iOS and macOS, the Companion app automatically appends its configured Snooze actions to notifications. To show only the Ring View actions, open Settings → Companion app → Notifications → Snooze Actions in the app and turn off the durations you do not want. This is a device-wide Companion app preference, not a setting that Ring View can disable for only this notification.
The blueprint requires Home Assistant 2026.7 or newer, a supported Ding entity, a camera preview entity, the Ring View Live and recording sources, and a working Companion app notification device. The optional backend patch is not required for this automation.
Ring-MQTT snapshot timing depends on the camera and its Snapshot Mode. For the most useful doorbell preview, choose a mode that includes Ding snapshots. Low-power cameras may not always produce a snapshot while recording; in that case the immediate alert still arrives and the blueprint safely leaves it without a stale preview.
The optional external-image method deliberately stores the latest notification
preview in /config/www. Home Assistant serves that file without
authentication. Its camera-derived filename is stable and the next successful
doorbell notification overwrites it; it is not automatically deleted. Use this
option only when you accept that anyone who learns the full URL can view the
latest saved frame. Clearing External image address returns the blueprint to
the authenticated camera-proxy method, but does not remove an existing file
from /config/www.
On some newer wired Ring cameras using 24/7 recording, an
upstream Home Assistant issue
can leave the recording entity's last_video_id stuck on an old event. The
immediate doorbell notification still arrives, but the blueprint cannot detect
a new recording and therefore leaves the notification without a recording
preview after the two-minute wait. The issue reporter found that disabling
24/7 recording and using periodic snapshots restored recording updates.
You can use the doorbell signal in additional Home Assistant automations to:
- Turn on an entrance light after dark.
- Announce a visitor on a speaker.
- Choose different notification behavior depending on who is home.
These are extension ideas; the shipped blueprint does not control lights, speakers, or presence logic. Keep those actions explicit in your own automations. Neither the blueprint nor a notification grants microphone permission or starts transmitting audio.
Card configuration · Talkback help
For an official Ring recording preview, enable and select the same device's Last recording timestamp sensor in the blueprint's optional timestamp field. A changed recording ID must then also have a valid recording timestamp no more than five seconds before the doorbell press or ahead of the current time. The five seconds are a comparison tolerance, not a delay. The immediate alert and Live action are sent first; the check runs within the existing preview wait. If the selected sensor is unavailable, no recording preview is attached until it becomes valid within that wait. Leave the field empty to retain the recording-ID check alone; Ring-MQTT snapshot previews retain their existing checks. The timestamp does not prove that the camera serves the corresponding clip, so the recording-ID check remains in place.