<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>RTSP on Mi&amp;Bee Blog</title><link>/en/tags/rtsp/</link><description>Recent content in RTSP on Mi&amp;Bee Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>蓝宝石的傻话</managingEditor><lastBuildDate>Fri, 22 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="/en/tags/rtsp/rss.xml" rel="self" type="application/rss+xml"/><item><title>MiBeeNvr v0.3.1: Multi-Protocol Streaming and Native Xiaomi Camera Support</title><link>/en/posts/iot/mibee-nvr-v0.3-tech/</link><pubDate>Fri, 22 May 2026 00:00:00 +0000</pubDate><guid>/en/posts/iot/mibee-nvr-v0.3-tech/</guid><description>&lt;p&gt;A lot of work went into the releases after v0.2.0. v0.3.x brings several major updates: native Xiaomi camera support, recording archiving, multi-protocol streaming architecture (WebRTC/HTTP-FLV/RTMP/SRT/LL-HLS), and a wave of security hardening. The architectural evolution from external dependencies to built-in implementation, from single protocol to full protocol support, was much more曲折 than I expected.&lt;/p&gt;
&lt;p&gt;The previous post introduced v0.2.0&amp;rsquo;s 15 new features (&lt;a href="/en/posts/iot/mibee-nvr-v0.2/"&gt;v0.2.0 Update&lt;/a&gt;). If you haven&amp;rsquo;t read the first post, start with &lt;a href="/en/posts/iot/mibee-nvr-introduction/"&gt;MiBeeNvr Introduction&lt;/a&gt;. v0.3.0 focuses on deep Xiaomi camera integration, and v0.3.1 builds on that with a complete multi-protocol streaming architecture. For the full changelog, see &lt;a href="https://github.com/Mi-Bee-Studio/MiBeeNvr/releases/tag/v0.3.1"&gt;GitHub Release Notes&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>MiBeeNvr v0.2.0 Update: Docker Deployment, HLS Streaming, Recording Merging, and a Complete Installation Guide</title><link>/en/posts/iot/mibee-nvr-v0.2/</link><pubDate>Tue, 12 May 2026 00:00:00 +0000</pubDate><guid>/en/posts/iot/mibee-nvr-v0.2/</guid><description>&lt;p&gt;The previous article introduced MiBeeNvr&amp;rsquo;s basic features and design philosophy. It&amp;rsquo;s only been a week since v0.1.0, and v0.2.0 follows right behind. This update is substantial — 15 new features, some I needed myself, others from community feedback.&lt;/p&gt;
&lt;p&gt;This article covers three things: what&amp;rsquo;s new in v0.2.0, how to deploy from scratch, and some practical tips for real-world use.&lt;/p&gt;
&lt;h2 id="v020-new-features-overview"&gt;v0.2.0 New Features Overview&lt;/h2&gt;
&lt;p&gt;This update has a lot of content. Here&amp;rsquo;s a breakdown by category:&lt;/p&gt;</description></item><item><title>MiBeeNvr: A Lightweight Home NVR System I Built</title><link>/en/posts/iot/mibee-nvr-introduction/</link><pubDate>Wed, 06 May 2026 00:00:00 +0000</pubDate><guid>/en/posts/iot/mibee-nvr-introduction/</guid><description>&lt;p&gt;I have several cameras at home — a few Xiaomi cameras, some DIY ESP32 cameras, and multiple Raspberry Pi CSI cameras. I&amp;rsquo;d been using cloud storage solutions, but I was never comfortable with them: vendor lock-in, network dependency, and the costs add up. So I decided to build my own NVR system, called MiBeeNvr.&lt;/p&gt;
&lt;h2 id="why-build-mibeenvr"&gt;Why Build MiBeeNvr&lt;/h2&gt;
&lt;p&gt;To be honest, I was never satisfied with existing cloud storage solutions. Take Xiaomi cameras, for example. By default, you can only view them through the Mi Home app. Recordings are either stored on an SD card (limited capacity, frequent plugging/unplugging) or in the cloud. Cloud storage costs tens of dollars per month, and there&amp;rsquo;s the privacy concern — you never know when the manufacturer might use your video data for AI training or sell it to third parties. Not to mention vendor lock-in — switching platforms is nearly impossible.&lt;/p&gt;</description></item></channel></rss>