Verification Request: homebridge-ring-secure-video

Abierto
#1,367 5 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
12/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
firebase, nodejs, typescript
Área
api, backend

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
TypeScript
Estrellas
371
Forks
26
Merge medio
1 h
PR fusionados (30 d)
5

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de homebridge/plugins

Todos los issues de homebridge/plugins

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.