Verification Request: @sealad886/homebridge-blink-cameras-new-api

Open
#1,374 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
release

Research direction

Read the plugin verification requirements in the Homebridge plugins repository and compare them with the linked plugin, release receipt, publication workflow, and validation evidence in the issue. The issue asks for verification of a published plugin and describes its functionality and release; done means the maintainers review the evidence and decide whether to verify it.

Written by the indexing model from the issue text.

Description

awaiting-final-review request-verification
Plugin Name

@sealad886/homebridge-blink-cameras-new-api

Link To GitHub Repo

https://github.com/sealad886/homebridge-blink-cameras-new-api

Plugin Icon (Optional)
plugin-icon
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

I am requesting verification of @sealad886/homebridge-blink-cameras-new-api 2.0.0, published on npm and running on my Homebridge installation.

What the plugin does

The plugin brings Blink cameras and security controls into Apple Home through a dynamic Homebridge platform. Its main features are:

  • HomeKit Secure Video from native Blink recordings. Motion events drive acquisition of the corresponding completed Blink Local Storage USB clip. The plugin downloads and prepares that clip, then delivers its video and audio through the existing camera accessory's HomeKit recording delegate. Users keep one camera accessory for live viewing and recordings.
  • Snapshots, live video, and one-way audio through the camera accessory.
  • Security-system arm/disarm, motion events, and per-device controls, with temperature reporting where supported by the device.
  • Homebridge UI configuration and Blink-hosted sign-in, including OAuth and MFA on Blink's own pages, persisted sessions and normal child-bridge startup.

HKSV uses native Blink Local Storage recordings, a connected Apple home hub and an eligible iCloud+ plan. Home's recording permissions govern recording requests and retention.

Distinct recording functionality

Completed native-clip delivery into HKSV is the distinguishing workflow for this request. The recording delegate supplies the prepared recording through the camera's existing HomeKit service.

The verified alternatives identified in #990 provide overlapping Blink controls and streaming features. The camera controller in @jackietreeh0rn/homebridge-blink-security configures streaming without a recording controller, and the recording callback in homebridge-blink-for-home-new returns no recording media. This request centers on the working native-clip recording path alongside the camera's live-view functionality.

Installation and operation

The plugin installs through normal Homebridge package management and is configured through the Homebridge UI. It uses standard Homebridge startup, with no TTY or special startup flags. Unconfigured and tokenless startup stays idle.

Media processing uses an externally installed FFmpeg 6.1 or later. The package does not bundle or install FFmpeg. If FFmpeg is missing or unsupported, the plugin logs recovery guidance and keeps arm/disarm, motion, and settings available while media functions are disabled.

Runtime authentication, cache, and recording state are stored under Homebridge's storage directory. Diagnostics use bounded, redacted Homebridge logs. The plugin has no author-operated analytics or tracking; functional network traffic serves Blink APIs/media and Google/Firebase push registration and delivery. The package has no install or uninstall lifecycle hooks. Configuration migration is an explicit command with preview, guarded application, and a private recovery backup.

Release and validation

The stable 2.0.0 release, public release receipt, and publication workflow identify the published package and source.

CI covers Node.js 22, 24, and 26. The same immutable package passed installed media/runtime qualification on Linux arm64/x64, macOS arm64/x64, and Windows x64, including FFmpeg 6.1.1 on Linux and 9.0.2 on Windows. Independent registry readback verified all 318 packaged files. A fresh installation, import, and platform registration also passed with FFmpeg absent.

On my Raspberry Pi, the exact registry release is installed and running through the normal Homebridge service, with stored-session startup, polling, and push delivery initialized. Live-account use is in the EU region; the other supported regions have API contract and routing coverage.

Related to #990.

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.