Verification Request: homebridge-ring-secure-video

Open
#1,367 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
12/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
firebase, nodejs, typescript
Domain
api, backend

Research direction

This is a verification request for a maintainer review, not a coding task, so a newcomer cannot complete it alone. Read the checklist in the issue body and compare the plugin's stated behaviour against the linked repository, zmanuel1234/homebridge-ring-secure-video, with attention to config.schema.json, the Ring sign-in custom UI, and the .ring.json storage path. Done means a maintainer records a verified or rejected decision in the thread.

Written by the indexing model from the issue text.

Description

request-verification
Plugin Name

homebridge-ring-secure-video

Link To GitHub Repo

https://github.com/zmanuel1234/homebridge-ring-secure-video

Plugin Icon (Optional)
image

Original artwork made for this plugin (a video camera with a bell and a record dot); it uses no Ring or Homebridge logo or wordmark.

The plugin does not offer the same nor less functionality than that of any existing verified plugin.

🟢 Yes

The plugin successfully installs and does not start unless it is configured.

🟢 Yes

The plugin does not require the user to run Homebridge in a TTY or with non-standard startup parameters, even for initial configuration.

🟢 Yes

The plugin does not contain any analytics or calls that enable you to track the user.

🟢 Yes

If the plugin needs to write files to disk (cache, keys, etc.), it stores them inside the Homebridge storage directory.

🟢 Yes

The plugin does not throw unhandled exceptions, the plugin must catch and log its own errors.

🟢 Yes

More Information

Ring Secure Video covers everything the verified homebridge-ring does (Ring Alarm, sensors, locks, lights, cameras and doorbells; every homebridge-ring 14.3.0 setting with the same name), and adds HomeKit Secure Video recording for Ring cameras and doorbells. It started from homebridge-ring 14.3.0 (Dusty Greif) and the HKSV pipeline of trinityhades/homebridge-ring-hksv 15.0.2, both credited in the README and LICENSE; it is maintained independently and is not affiliated with Ring.

What it adds over homebridge-ring:

  • HKSV recording with media profiles (adaptive, lowPower for a Raspberry Pi, quality) and a choice of copy, libx264 or the Pi 4 / Mac hardware encoders
  • an optional separate motion sensor per camera, for motion notifications without waiting for HKSV clip analysis
  • motion from Ring's event history when Ring's push notifications don't arrive, and automatic Ring session refresh (with an optional sensor) when they stop
  • an optional HKSV recording on a doorbell press, and Ring Intercom Video as a camera

Requirements:

  • Dynamic platform with a settings GUI (config.schema.json plus a custom UI for signing in to Ring).
  • Without a configuration block it logs "No configuration found" and stays idle.
  • Network calls go only to Ring's API and Ring's push notification service (Firebase Cloud Messaging), as in homebridge-ring; no analytics or telemetry.
  • Files: Ring's device identity in .ring.json in the Homebridge storage folder, and a renewed Ring refresh token saved back into config.json (as homebridge-ring does), written atomically.
  • Runs on Node.js 22, 24 and 26 (CI tests all three on every change), Homebridge 1.8 and 2.x. No post-install scripts of its own.
  • Every version has a GitHub release with notes; npm releases are published from those releases by GitHub Actions with provenance.

Tested on a Raspberry Pi 4 (Node 22, Homebridge 2.5) with a Ring Video Doorbell 3 Plus, Ring Alarm and 21 sensors.

Dominant language
TypeScript
Stars
371
Forks
26
Avg merge
1h
Merged PRs (30d)
5

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from homebridge/plugins

All issues in homebridge/plugins

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.