<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>MiBeeOSS on Mi&amp;Bee Blog</title><link>/en/categories/mibeeoss/</link><description>Recent content in MiBeeOSS on Mi&amp;Bee Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>蓝宝石的傻话</managingEditor><lastBuildDate>Fri, 05 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="/en/categories/mibeeoss/rss.xml" rel="self" type="application/rss+xml"/><item><title>MiBeeNvr v0.6.0: Timelapse + Transcoding UI + ONVIF Enhancements + Documentation Restructure</title><link>/en/posts/mibee-oss/mibee-nvr-v0.6-promo/</link><pubDate>Fri, 05 Jun 2026 00:00:00 +0000</pubDate><guid>/en/posts/mibee-oss/mibee-nvr-v0.6-promo/</guid><description>&lt;p&gt;After running continuous recording for a few weeks, storage became the first bottleneck. A single 1080p camera writes tens of GB per day — with a 30-day retention policy, a 1TB硬盘 is mostly consumed. Many community members reported the same issue, and during discussions, the ideas of timelapse and transcoding storage gained the most traction: most of the time the画面 is static, and compressing it with timelapse requires only 5% of the space for the same duration.&lt;/p&gt;</description></item><item><title>MiBeeNvr v0.6.0's Test Machines: Three Camera Projects Updated in Sync</title><link>/en/posts/mibee-oss/camera-test-machines/</link><pubDate>Fri, 05 Jun 2026 00:00:00 +0000</pubDate><guid>/en/posts/mibee-oss/camera-test-machines/</guid><description>&lt;p&gt;The concurrently released &lt;a href="/en/posts/mibee-oss/mibee-nvr-v0.6-promo/"&gt;MiBeeNvr v0.6.0&lt;/a&gt; brought major features like timelapse, video transcoding, and ONVIF enhancements. Unit tests alone are far from enough — the full workflow must be tested against real camera hardware. To provide reliable test machines for this release, three camera projects were updated on the same day, June 5th — both to supply testing environments for the NVR and to solve some typical embedded development engineering problems along the way.&lt;/p&gt;</description></item><item><title>MiBeeNvr v0.5.0: Full ONVIF Protocol Support + Hardware Transcoding + rpi-cam Co-development</title><link>/en/posts/mibee-oss/mibee-nvr-v0.5/</link><pubDate>Sat, 30 May 2026 00:00:00 +0000</pubDate><guid>/en/posts/mibee-oss/mibee-nvr-v0.5/</guid><description>&lt;p&gt;Less than a week after v0.4.0, another 31 commits were pushed. v0.5.0 is a feature-dense release: &lt;strong&gt;full ONVIF protocol support&lt;/strong&gt; (covering all five major services: Device/Media/PTZ/Imaging/Event), &lt;strong&gt;hardware transcoding&lt;/strong&gt; (H.265 → H.264), and recorder reconnection optimizations. 127 files changed, +24,509 / -730 lines. See the full changelog at &lt;a href="https://github.com/Mi-Bee-Studio/MiBeeNvr/releases/tag/v0.5.0"&gt;GitHub Release Notes&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;If you haven&amp;rsquo;t seen the previous versions, check out &lt;a href="/en/posts/iot/mibee-nvr-introduction/"&gt;MiBeeNvr Introduction&lt;/a&gt; and &lt;a href="/en/posts/iot/mibee-nvr-v0.4-tech/"&gt;v0.4.0 Technical Post&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id="full-onvif-protocol-support"&gt;Full ONVIF Protocol Support&lt;/h2&gt;
&lt;p&gt;v0.4.0 already had ONVIF device discovery and stream URL retrieval, but that was just the tip of the ONVIF iceberg. v0.5.0 completes the core services of ONVIF Profile S:&lt;/p&gt;</description></item><item><title>MiBeeHive: The "Hive" Toolbox I Built for My Studio</title><link>/en/posts/mibee-oss/mibeehive-introduction/</link><pubDate>Tue, 26 May 2026 00:00:00 +0000</pubDate><guid>/en/posts/mibee-oss/mibeehive-introduction/</guid><description>&lt;p&gt;Coming from an operations background, later transitioning to development, the number of projects I maintain keeps growing. Various middleware, databases, monitoring components… each version upgrade is a manual labor: go to the official site to find the download link, compare version numbers, manually download to the internal network, then distribute to each machine. I used to write a bunch of Shell scripts to periodically pull the latest versions to the LAN — functional but not user-friendly: scripts scattered everywhere, adding new software required writing parsing logic by hand, and there was nothing to check when things went wrong.&lt;/p&gt;</description></item></channel></rss>