explaingit

borexola/neolink.net

Analysis updated 2026-05-18

111C#Audience · ops devopsComplexity · 3/5Setup · moderate

TLDR

A C#/.NET bridge that converts Reolink cameras' proprietary protocol into standard RTSP, with a built-in web viewer and Home Assistant integration.

Mindmap

mindmap
  root((Neolink.NET))
    What it does
      Bridges Baichuan to RTSP
      Web camera wall
      Home Assistant MQTT
    Tech stack
      C sharp
      dotnet
      Blazor
    Use cases
      Frigate integration
      Live browser viewing
      Two way talk
    Audience
      Home automation users

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Connect Reolink cameras that use the Baichuan protocol to NVR software like Frigate or Blue Iris.

USE CASE 2

View multiple Reolink cameras live in a browser without installing any plugins or transcoding software.

USE CASE 3

Automatically surface a Reolink camera's motion and person detection as sensors in Home Assistant.

USE CASE 4

Run a lightweight camera bridge on a Raspberry Pi without needing GPU-based video analysis.

What is it built with?

C#.NETRTSPMQTTBlazor

How does it compare?

borexola/neolink.netzethrise/spoofguityrrrz/osuhelper
Stars111111108
LanguageC#C#C#
Last pushed2023-07-16
MaintenanceDormant
Setup difficultymoderateeasyeasy
Complexity3/53/52/5
Audienceops devopsgeneralgeneral

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · moderate Time to first run · 1h+

Camera support varies by model since it is tested only against cameras the maintainer personally owns, Docker and Home Assistant add-on options are provided.

In plain English

Neolink.NET is a bridge for Reolink security cameras that speak a proprietary protocol called Baichuan instead of the standard RTSP protocol that most video software expects. It sits between your cameras and whatever software you actually want to watch them with, such as Frigate, Blue Iris, Home Assistant, VLC, or ffmpeg. Neolink.NET logs into each camera, pulls apart its video stream, and re-serves it as standard RTSP that any of those tools can understand, without needing a Reolink NVR box or modifying the cameras themselves. It is written in C# and .NET, inspired by an earlier open-source project of the same idea called Neolink. On top of the bridging, it includes a built-in web interface you view in a browser, showing a wall of camera tiles with live low-latency video and no plugins required, along with an events page and a synced timeline for reviewing footage across multiple cameras. It also integrates directly with Home Assistant over MQTT, so each camera shows up automatically with motion, person, vehicle, and animal sensors, plus controls, all based on detections the camera's own hardware already performs. Because Neolink.NET does not run any of its own video analysis or object detection, it adds very little processing load and can run comfortably on something as small as a Raspberry Pi. Other features include two-way audio so you can talk through cameras that have a speaker, such as doorbells, several different layout modes for viewing multiple cameras at once, and a settings panel that reads a camera's own capabilities, like pan-tilt-zoom controls, zoom and focus, siren, and night mode, letting you stage changes before applying them. The project is maintained by one person in their spare time, and the README is upfront that it has only been tested against the cameras the maintainer personally owns, asking users with other camera models to report issues or contribute fixes. The full README is longer than what was shown.

Copy-paste prompts

Prompt 1
Walk me through setting up Neolink.NET in Docker to bridge my Reolink cameras to RTSP.
Prompt 2
Explain how Neolink.NET's Home Assistant MQTT integration surfaces motion and person detection events.
Prompt 3
Show me how to enable two-way talk on a Reolink doorbell camera through Neolink.NET's web UI.
Prompt 4
Help me configure Neolink.NET so Frigate can connect to a Reolink camera that isn't natively supported.

Frequently asked questions

What is neolink.net?

A C#/.NET bridge that converts Reolink cameras' proprietary protocol into standard RTSP, with a built-in web viewer and Home Assistant integration.

What language is neolink.net written in?

Mainly C#. The stack also includes C#, .NET, RTSP.

How hard is neolink.net to set up?

Setup difficulty is rated moderate, with roughly 1h+ to a first successful run.

Who is neolink.net for?

Mainly ops devops.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.