Repository navigation
Verification Request: homebridge-blink-for-home-new #861
Description
Plugin Name
homebridge-blink-for-home-new
Link To GitHub Repo
https://github.com/Flomentum-Solutions/homebridge-blink-for-home-new
Plugin Icon (Optional)
No response
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
Why this new package exists
The original Blink plugin for Homebridge was archived and has PRs/issues disabled. That prevents any security fixes or compatibility updates from landing. Blink’s backend changed (regional shard routing, stricter rate limits, fussier headers), so users on the archived package face frequent breakage. This fork is a clean, maintained successor, published under a new npm name to continue support.
Old repo: archived, PRs closed → no path to ship fixes
New repo: actively maintained, semver releases, UI schema, and ongoing compatibility updates
Summary of improvements
-
Shard-aware API routing (prod → u00x)
- Login (and
/api/v1/account/tier_info) stay onrest-prod.immedia-semi.com. - After login we automatically pivot all other requests to the discovered shard (e.g.,
rest-u003.immedia-semi.com). - Eliminates cross-region flakiness and aligns with current Blink app behavior.
- Login (and
-
Rate limiting + 429 backoff (stability under load)
- Central request wrapper with a conservative limiter (~1 req/sec) and retries that honor
Retry-Afteron HTTP 429. - Prevents the “Too Many Requests → accessories offline” spiral many users saw.
- Central request wrapper with a conservative limiter (~1 req/sec) and retries that honor
-
FFmpeg reliability (explicit path + bundled fallback)
- New
ffmpegPathoption; if unset, we auto-resolve a managed ffmpeg binary (ffmpeg-for-homebridge) before falling back to system ffmpeg. - Clear logging on ENOENT and safer spawn handling.
- New
-
Header / User-Agent refresh
- Updated to a current mobile Blink client fingerprint.
- Matches what stable community clients send today; reduces 401/406 auth loops.
-
Traffic smoothing
- Optional staggered thumbnail refresh to avoid burst calls when multiple cameras update at once.
-
Homebridge UI integration
config.schema.jsonincluded for a proper Settings screen (no manual JSON).- Clear field names for email/password/2FA PIN, region override (optional), and
ffmpegPath.
-
Engines + docs
- Tested on Homebridge v1.11.x and Node 22.x (supports current LTS lines).
- README updated with limitations (Blink live view constraints), troubleshooting, and migration notes.
No breaking changes to core configuration. Existing users can copy their credentials over; PIN flow is unchanged.
Why a new package name (and verification)
- The upstream maintainer archived the project and disabled PRs, so we cannot ship fixes under the original name.
- Publishing under a new name allows timely updates, security fixes, and user support.
- We meet Homebridge verification expectations:
homebridge-pluginkeyword and proper namingconfig.schema.jsonfor UI- clear README, CHANGELOG, LICENSE (MIT; original authors credited)
- semver releases; active maintenance policy
Maintenance & support commitment
- Ongoing compatibility with Blink API changes (headers, auth, endpoints, rate limits).
- Issue triage within 7 days, patch releases for regressions.
- No telemetry; credentials stay in Homebridge config; tokens only held in memory.
- CI checks (lint/build) and semver tagging for each release.
Migration notes for users (from the archived plugin)
- Uninstall the archived package in Homebridge UI.
- Install homebridge-blink-for-home-new (this repo).
- Open Settings and enter the same Blink credentials and (once) the 2FA PIN after approving the device via email.
- Optional: set
ffmpegPathif your system ffmpeg is non-standard.
Ask to the Homebridge team
- Please verify this new package as the maintained successor to the archived Blink plugin so users can find the stable option in search and trust it will receive updates.
- If the original maintainer returns and wants to revive upstream, I’m happy to coordinate and, if appropriate, deprecate this package in favor of a unified path.
Activity
github-actions commentedon Aug 12, 2025
🔴 The following checks failed:
homepagemissing or does not start withhttps://bugs.urlmissingengines.nodeproperty is not compatible with Node 20🟢 The following checks passed:
keywordsexist and contain'homebridge-plugin''preinstall'inscriptsis not present'install'inscriptsis not present'postinstall'inscriptsis not presentengines.nodeproperty is compatible with Node 22engines.homebridgeproperty is compatible with Homebridge 1.11.0pluginAliaspluginTypeis set to'platform'nameschema propertyhomebridgewas not installed as a dependencyhap-nodejswas not installed as a dependency/checkto run the checks again. Let us know if you need any help.If updating your
package.jsonandconfig.schema.jsonfiles, don't forget to publish a new version to NPM.MBRO95 commentedon Aug 12, 2025
/check
github-actions commentedon Aug 12, 2025
🔴 The following checks failed:
🟢 The following checks passed:
homepageexistsbugs.urlexists and seems a valid URLkeywordsexist and contain'homebridge-plugin''preinstall'inscriptsis not present'install'inscriptsis not present'postinstall'inscriptsis not presentengines.nodeproperty is compatible with Node 20engines.nodeproperty is compatible with Node 22engines.homebridgeproperty is compatible with Homebridge 1.11.0pluginAliaspluginTypeis set to'platform'nameschema propertyhomebridgewas not installed as a dependencyhap-nodejswas not installed as a dependency/checkto run the checks again. Let us know if you need any help.If updating your
package.jsonandconfig.schema.jsonfiles, don't forget to publish a new version to NPM.These checks were run against v0.0.2 of the plugin.
MBRO95 commentedon Aug 12, 2025
/check
github-actions commentedon Aug 12, 2025
🟢 The following checks passed:
homepageexistsbugs.urlexists and seems a valid URLkeywordsexist and contain'homebridge-plugin''preinstall'inscriptsis not present'install'inscriptsis not present'postinstall'inscriptsis not presentengines.nodeproperty is compatible with Node 20engines.nodeproperty is compatible with Node 22engines.homebridgeproperty is compatible with Homebridge 1.11.0pluginAliaspluginTypeis set to'platform'nameschema propertyhomebridgewas not installed as a dependencyhap-nodejswas not installed as a dependency🎉 All checks passed successfully, nice work! Your plugin and/or icon will now be manually reviewed by the Homebridge team.
These checks were run against v0.0.2 of the plugin.
19 remaining items
github-actions commentedon Dec 1, 2025
🟢 Passed Checks
homepageexistsbugs.urlexists and seems a valid URLkeywordsexist and contain'homebridge-plugin''preinstall'inscriptsis not present'install'inscriptsis not present'postinstall'inscriptsis not presentengines.nodeproperty is compatible with Node 20engines.nodeproperty is compatible with Node 22engines.nodeproperty is compatible with Node 24engines.homebridgeproperty is compatible with Homebridge 1.11.1typepropertypropertiesfor object typepluginAliaspluginTypeis set to'platform'nameschema propertyhomebridgewas not installed as a dependencyhap-nodejswas not installed as a dependency🔍 For Manual Review
The following items were detected and require manual review. We understand that these items may be false positives.
ℹ️ Check Details
v0.2.1of the plugin.https://api.oauth.blink.com/oauth/tokenMethods:
POST| Count:3| Scenarios: full config, network resiliencehttps://rest-test-value.immedia-semi.com/api/v3/accounts/1/homescreenMethods:
GET| Count:1| Scenarios: full config📋 Next Steps
All checks passed successfully, nice work! Your plugin and/or icon will now be manually reviewed by the Homebridge team.
bwp91 commentedon Dec 1, 2025
Hi @MBRO95
out of interest, what is the call to
https://rest-test-value.immedia-semi.com/api/v3/accounts/1/homescreenfor?MBRO95 commentedon Dec 1, 2025
Hey @bwp91, that call is made as part of the simulated user agent flow to not have the Blink servers flag this as bot activity. The plugin emulates an iPhone running the Blink iOS app and that's the expected call flow.
github-actions commentedon Dec 1, 2025
Congratulations! Your plugin has been verified!
You can now add one of the Verified by Homebridge badges to your plugin's README:
Your plugin is now also eligible to display a ❤️ Donate button on its tile in the Homebridge UI. See https://github.com/homebridge/homebridge/wiki/Donation-Links for instructions.
Interested in getting a
@homebridge-plugins/scope for your plugin? See our Homebridge Scoped Plugins program.If for any reason in the future you can no longer maintain your plugin, please consider transferring it to our Homebridge Plugins organization.
Don't forget to join the official Homebridge Discord server, where plugin developers can get tips and advice from other developers and the Homebridge project team in the #plugin-development channel!
As a verified plugin, you can request a channel in the Discord server to discuss your plugin with users and other developers. Just ask in the #plugin-development channel.
Thank you for your contribution to the Homebridge community.
verify: homebridge-blink-for-home-new
bwp91 commentedon Dec 1, 2025
thanks for the clarification there!