Blink Camera Relay

Blink Camera Relay is an unofficial bridge that exposes Blink cameras as Real-Time Streaming Protocol (RTSP) and Open Network Video Interface Forum (ONVIF)…

  • Home Automation
Blink Camera Relay is an unofficial bridge that exposes Blink cameras as Real-Time Streaming Protocol (RTSP) and Open Network Video Interface Forum (ONVIF) streams, with a web dashboard for onboarding and camera settings, giving homelab users local, self-hosted feed access while Blink cloud login remains required.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

49/100 Fair

Maintained
79last commit 34 days ago
Popular
123 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
502 GB minimum RAM

Availability: platform listings confirmed today

GitHub stars
3
Open issues
0
Last commit
2026-10-18
Latest release
v0.1.5
License
MIT
Activity
stale

Checked today - source: GitHub (centauri/blink-camera-relay)

Resources & Compatibility

Minimum requirements: 2 GB RAM, 200 MB disk.

Checked 47 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Install Blink with pesde If your project uses pesde, run both commands: pesde add --dev 1axen/blink, then pesde install. The second step is important because it actually downloads the package, not just lists it, so the project can find Blink when it starts. source
  • Install Blink with Rokit If your project uses Rokit, run rokit add 1Axen/blink. This adds the Blink package to your project so scripts that depend on it do not fail because the package is missing. source
  • Network, ports, and cloud login Use host networking on a trusted LAN only. Free TCP ports 8787, 8554, 8555, and the chosen ONVIF port (default 8080) plus UDP 3702 must be available. Set the server LAN IP and a dashboard password in the web dashboard. Blink cloud pairing/login is still required, and session renewals can cause brief video gaps. Image: ghcr.io/centauri/blink-camera-relay:latest (linux/amd64). source
  • Upgrading from the edge tag Existing installations using the edge image tag can change the container Repository to ghcr.io/centauri/blink-camera-relay:latest and apply the update, retaining the existing appdata mapping. source

Fetched 44 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

What ports must be free for the container?

Host ports TCP 8787, 8554, 8555, and 8080 must be free, plus UDP 3702 for discovery. Port 8080 is the default ONVIF port and can be adjusted per camera.

Does the app still require a Blink cloud login?

Yes. Blink cloud pairing and login are still required, even though the bridge exposes RTSP and ONVIF locally.

Can I expose the dashboard or streams directly to the internet?

Do not forward these ports to the Internet because the dashboard uses HTTP Basic authentication without encrypting network traffic, and RTSP/ONVIF have no enforced client authentication. Use a trusted LAN, a trusted VPN, or a TLS proxy for remote administration.

How should I migrate a camera from the old Windows bridge?

Stop the old Windows bridge before adopting the same camera through the new installation. Do not copy its saved process or runtime files.

What app data should I back up?

Tokens and settings persist in appdata, so back up the appdata volume. Process IDs and logs are ephemeral, and enabled services resume on container restart.

Does the container need host networking?

The README specifies host networking for ONVIF multicast discovery. The appdata directory should be mounted at /data.

Answers sourced from github.com

Community

Collected 48 days ago - public community threads