Chrome extension that keeps Ring multi-cam live view from dying.
Ring's web dashboard (account.ring.com) drops camera tiles and shows
Reconnect. This extension clicks it for you so feeds stay up.
Repo: liveview-reconnect-ring
Not affiliated with Ring or Amazon. Unofficial tool for your own live-view
monitoring. Review the code before installing. The debugger permission is
required so reconnect clicks work; use only on a profile you trust.
- Download or clone this repo
- Chrome →
chrome://extensions→ enable Developer mode - Load unpacked → select the
extension/folder - Open
https://account.ring.com, sign in, open Multi-Cam - Click the extension icon to see camera status
Install it only on the Chrome profile that runs the live view.
Ring ignores synthetic clicks. Reloading the page also does not help: the Multi-Cam URL carries a single-use live-session token, so a reload drops you to the plain Dashboard. The only reliable restart is a real (trusted) mouse click, which an extension can only produce through Chrome's debugger API (CDP). This extension automatically:
- clicks each tile's Reconnect with a trusted click
- when Ring kicks you to the Dashboard, trusted-clicks Start Live Views
Recovery is confirmed only when video frames advance. Failed attempts back off with jitter and, after several, raise a desktop notification.
- Keep Active on and leave Multi-Cam open
- Use Refresh in the popup after you add/remove cameras
Because recovery uses the debugger API, Chrome shows a yellow bar while a click is in flight (attach, click, detach). That warning is process-wide: it appears on every open Chrome window and profile in the same browser process, even profiles that do not have this extension. Attach itself only targets the Ring tab; the warning UI is broader by design. No extension API can hide it.
Ways to avoid the bar:
- Enterprise force-install (best on machines you own). Policy-installed extensions skip the bar.
- Dedicated Chrome via script (below). Uses its own user-data-dir plus
--silent-debugger-extension-api. A normal second Chrome launch usually joins your existing process and ignores new flags, so the separate data dir matters.
Launches a dedicated Chrome process with its own user-data directory and
--silent-debugger-extension-api, so recovery clicks do not show the yellow
debugger bar. No Python required.
macOS / Linux
chmod +x scripts/open-chrome.sh # once
./scripts/open-chrome.shWindows (double-click, or from Command Prompt / PowerShell)
scripts\open-chrome.cmdThe script prints the Chrome binary and profile path it will use, then opens
https://account.ring.com/. Load unpacked extension/ in that window, open
Multi-Cam, keep Active on. Your everyday Chrome is unchanged and will not
show the yellow bar from this instance.
Optional env overrides:
CHROME_PATH: full path to the Chrome (or Chromium) binaryLVR_CHROME_DATA_DIR: custom profile folder (default is a separate LiveViewReconnectRing data dir under your OS app-support path)
Pass --dry-run to print the launch command without starting Chrome.
Local-only. Nothing is sent off your machine.
- Reads
https://account.ring.com/*to find dead tiles and Reconnect / Start Live Views controls - Uses
chrome.debuggeron that Ring tab only for the brief trusted click, then detaches - Stores the Active preference and short-lived tile health in extension storage
- No accounts, passwords, analytics, ads, or author-operated servers
- No Ring private APIs
Privacy questions: open a GitHub issue on this repository.
Supported: latest commit on main only.
Report vulnerabilities privately via GitHub Security Advisories on this repository. If that is unavailable, open an issue without exploit details and ask for a secure contact. Do not post working exploit code publicly.
The extension uses Chrome's debugger permission briefly on
https://account.ring.com/* to dispatch trusted Reconnect / Start Live Views
clicks, then detaches. It never handles Ring credentials. Review the source
before installing forks.
For keeping your own Ring multi-cam live view alive on a machine you control. Do not use this to probe, scrape, or abuse Ring's services. Forks that change host permissions or debugger behavior should be reviewed before install.