Ring Web Motion Alert Digest

WHAT IT DOES

This tool monitors your Ring device history and provides a digest of motion alert events. It scans the page for alerts—timestamp, camera name, event type, and video links—and displays them in a compact panel. Alerts are grouped by camera and date, with counts showing which cameras are most active. The panel calculates alert frequency (alerts per hour) and highlights unusual activity patterns. A camera stats breakdown shows each camera's alert count and percentage of total alerts. Quick "View" buttons open event videos in new tabs. Desktop notifications alert you when alert volume spikes above typical levels.

WHERE IT RUNS

The script activates on Ring pages (ring.com), including device history pages, event logs, and alert history views. It automatically detects motion alert data using multiple extraction strategies that work across different Ring layouts. The panel appears as a draggable overlay that stays accessible as you review your alerts.

HOW TO USE

Navigate to your Ring device history page. The panel will appear showing a digest of motion alerts. Set the "Window (hrs)" input to control how many hours of alerts to include in the digest (default 24 hours). Set the "Spike threshold" to control when a spike notification is triggered (default 5 alerts above average). The "Refresh" button manually updates the data, and the panel automatically refreshes at your configured interval. The summary shows total alerts, camera count, frequency, and the digest window. The camera stats show each camera's alert count and percentage. The alert list shows individual events with timestamps and camera names. Click "View" to open an event video. Spike notifications alert you when activity is unusually high.

THE TECHNICAL MECHANISM

The script employs a multi-strategy DOM extraction approach for Ring's history interface. It first attempts structured selectors targeting known class names like .alert-item, .motion-item, and .event-item, then falls back to heuristic detection of alert containers based on content patterns including "motion", "ring", and "doorbell" indicators. Timestamps are extracted from time patterns with support for 12-hour and 24-hour formats. Camera names are extracted from camera/device indicators. Event types are detected from text patterns (motion, doorbell, ring). Alert grouping uses JavaScript Map objects to aggregate alerts by camera, hour, and date. Frequency is calculated as total alerts divided by the digest window in hours. Spike detection compares the current period's alert count against the average of the last 5 days (stored using GM_setValue) and triggers if the count exceeds the average plus the user-defined threshold. The auto-refresh uses setInterval with a user-configurable interval, and a MutationObserver watches for page updates. All settings and history are persisted using GM_setValue.

THE PANEL

The panel is fully draggable by its header and remembers its position on the page across sessions. It can be collapsed to a small bubble using the minimize button, then restored by clicking the bubble. The panel resizes automatically to fit its content and can be closed with the Escape key or by clicking the close button. The panel's position and state persist globally, so it returns to the same location on subsequent visits.

PLEASE NOTE

Requires the free BotGentz extension to run. Ring may update its site structure, which could affect the script's ability to detect alert data — updates will be released as needed. All alert data and history are stored locally in your browser and are never transmitted externally. The script reads data from the visible page and does not access any data beyond what is visibly presented. The script does not modify your Ring account or device settings. Spike detection is based on historical data stored in your browser and may not reflect real-time activity. Desktop notifications are sent only when the page is active and the script is running. This tool is for informational purposes only and is not affiliated with Ring.