-
-
Notifications
You must be signed in to change notification settings - Fork 200
Common Feature Requests
This project is maintained by a small group of volunteers, and most work goes toward keeping the existing Ring API integration working as Ring changes things upstream. Some feature requests are reasonable, but still not something we plan to build in this repo.
The sections below cover common requests that are not planned at this point. Pull requests may still be considered when they are maintainable, tested, and do not create a large support burden.
HomeKit Secure Video is not planned.
The main issue is not just Ring subscription overlap. A useful HKSV implementation would require a full video processing pipeline, and likely a continuous stream with pre-buffering. That is expensive to run, hard to make reliable across the many networks and devices users have, and not a good fit for how this plugin currently handles camera streams.
Many Ring cameras also do not behave like always-on cameras. Battery devices, network conditions, Ring server behavior, and HomeKit expectations all make this much more complex than exposing an existing stream.
We understand why users want this, but the maintenance and support cost is too high for this project right now.
If HKSV is a priority for your use case, take a look at Scrypted. It has a Ring integration and proper HomeKit Secure Video support, and it is built specifically around a video processing pipeline.
Ring Intercom support is intentionally limited.
The maintainers do not have broad access to these devices, and intercom behavior varies enough that it is difficult to test safely. Audio, video, call accept, and fake video-doorbell behavior would require more reverse engineering, more HomeKit modeling, and more device-specific testing than we can reasonably support.
Pull requests may be considered, but they need to be small, tested, and clear about which device models and account configurations they support.
We do not plan to add features that automatically unlock a door when an intercom or doorbell event occurs.
That behavior can be unsafe if it fires unexpectedly, if Ring sends duplicate or delayed events, or if HomeKit automations are configured incorrectly. If you want this behavior, it is better handled as a personal HomeKit automation where you own the risk and can tune the exact conditions.
This project does not plan to become a general RTSP server, DVR, or video processing system.
ring-client-api and homebridge-ring focus on exposing Ring devices to JavaScript and HomeKit. Building and supporting a stable recording or restreaming pipeline means owning FFmpeg options, codec compatibility, buffering, network behavior, file output, and client compatibility. That is a much larger scope than this project is trying to cover.
If your goal is a dedicated video pipeline, Scrypted or ring-mqtt may be a better fit.
We generally do not plan to add video transcoding features just to adjust aspect ratio, resolution, or quality.
The plugin tries to forward Ring's stream with as little processing as possible. Transcoding would add CPU cost, more FFmpeg complexity, more latency, and more platform-specific failures. For most users, that tradeoff is not worth the added maintenance burden.
HomeKit and the Home app may provide some display-side controls, such as pinch zooming, depending on the client.
Requests for very granular controls, such as exposing only one part of a combined sensor, hiding individual generated entities, or adding highly specific switches, are usually not planned.
The plugin already has some broad device hiding and configuration options. Adding a setting for every device-specific edge case makes the config harder to understand and increases the chance of breaking existing setups. We need enough demand and a clean HomeKit model before adding more entity-level controls.
The plugin can expose supported events to HomeKit, but it does not control how Apple Home, HomePods, or Apple TVs decide to present notifications or chimes.
If the event appears in the Homebridge logs, the plugin has done its part. From there, notification routing, HomePod chimes, Apple TV display, and per-device notification settings are controlled by HomeKit.
For notification troubleshooting, see Notification Troubleshooting and Apple TV Notifications.
New Ring devices may be supported if someone can provide enough data to understand how the device appears in the Ring API.
If you are requesting support for a new device, please run Data Discovery and include the sanitized output in the issue. Without that data, most new-device requests are not actionable.
Please do not include your Ring email, password, refresh token, or any other credentials.