0.4.3d (pre-release)
Fourth pre-release of the 0.4.3 cycle. Everything from 0.4.3c, plus a rebuilt web-UI upgrade flow: the install now runs detached and survives a browser refresh, the GitHub download is resilient and fully verified before any install, status checks no longer stall the page, uploads are verified for completeness, and the upgrade buttons can deliberately downgrade as well as upgrade.
New features
- Firmware install from the web UI (#329) - a Firmware Package section on the Service page accepts a
yi_dome_x.x.x.tgzupload, validates it, and runs the standard install (config backup, two-stage extract, reboot). The Service page is now the single place for all three update methods (latest, pre-release, from file); the Update page keeps the legacy home+rootfs flash and is linked from Service. The SD card is still required - the hack and the upgrade both run from it - but it no longer needs to be touched from a PC. Verified end-to-end on a yi_dome: a 12.8 MB package uploaded via the web UI installed cleanly with configuration preserved. - Stable ONVIF / WS-Discovery UID (#107) - the camera previously advertised a random UUID on every boot, so ONVIF clients could not re-identify it. The UID is now configurable (
ONVIF_UIDon the Configurations page), falling back to the camera serial number when unset. - "Delete all" on the Events page (#302) - wipes every recorded event directory behind a confirm dialog; per-directory delete is unchanged.
- Status page links follow the host you use (#255) - snapshot and RTSP links now resolve against the hostname/port the browser used to reach the camera, so they work through reverse proxies and tunnels instead of pointing at a LAN IP.
- Deliberate downgrades - the Upgrade to Latest and Upgrade to Pre-Release buttons are pins to whatever GitHub reports: a camera on the pre-release train can move back to the stable channel (and vice versa), with the page announcing "Downgrade to X started (current: Y)". The only remaining refusal is the baseline floor - a 0.4.2-baseline camera cannot take a 0.4.3 package in either direction, because the rootfs layout differs.
Bug fixes
- Pre-release field showed the branch name, not the tag - GitHub changed the layout of its releases API response, which misaligned the line-offset parsing, so the web UI displayed the default branch (
test-0.4.3) instead of the pre-release tag. The release list is now parsed properly withjq(bundled in the package, built viasrc/jq/compile.jq) after downloading to a temp file, with up to three retries - the old stdout pipe truncated the large API response intermittently. The same fix covers the matching JS field typo that kept the pre-release status line empty. - Firmware status went blank after normal use - the status check hit the unauthenticated GitHub API twice per page load, and that quota (60 requests/hour) is per IP, shared with the rest of the LAN. After a few hours of use, both the Latest and Pre-Release fields rendered empty until the hourly window reset. The status check now serves from a 10-minute local cache; the cache is only written when the API actually answered, so a rate-limited response is never pinned.
- Empty MQTT motion files list (#388) -
yicam/motion_filescarried correct timestamps but an emptyfilesarray. Two root causes in the mqttv4 component: a GMT/local time mismatch against the recorder's directory naming, and a directory-walk that aborted on the first missing minute. Verified with a 1:1 port of the lookup logic against a realistic recording tree. - PTZ "Go To Preset" never worked (#472) - the select's display text was sent instead of its value, so every request was rejected as invalid.
- Spurious "baseline is incorrect" boot warning - the baseline gates were frozen as exact
0.4.1equality checks, so every correctly flashed 0.4.2+ camera logged a boot error and the GitHub-download upgrade path refused to run. The checks now correctly mean "baseline 0.4.1 or newer". - Upgrade refused on pre-release baselines - once the check above was relaxed, a pre-release baseline such as
0.4.3bstill failed: the version gate parses each dotted field withprintf %03d, and busybox reads the non-numeric suffix (3b) as 0, so0.4.3bcomputed as0.4.0and was rejected with "Wrong baseline version" on every upgrade attempt (plus the spurious boot warning). The letter suffix is now stripped before the numeric comparison in both the upgrade gate and the boot check, so0.4.3bis treated as0.4.3. - RTSP watchdog efficiency (#496) - the MQTT guard spawned four subprocesses every 10 s (even with MQTT off) and misfired when the setting was empty; it now uses the shared
read_confhelper. - RTSP key-frame detection (#495) - restored the STAP-A and H.265 fragment offsets in
rRTSPServer's key-frame check. No effect on current H.264 v5 streams; a correctness fix for future stream types. - Web-UI GitHub download is now resilient and verified - the package download resumed from a partial file (
wget -c), aborted a dead or stalled connection after 60 s of silence instead of hanging the upgrade forever, and was fully verified (entire gzip stream + CRC) before any install. A truncated download on a flaky link was the classic way to end up with a package missing its tail files; it is now caught, deleted, and retried up to three times before the user is asked to try again. - A broken package can no longer reboot the camera into a half-written state - if the package fails to decompress or extract, the install aborts with an error message instead of rebooting. Previously a corrupt or truncated archive was extracted as far as it got and the camera rebooted into a partially updated tree.
- The uploaded package is consumed after install - a manual
x.x.x.tgzleft in the SD root was checked before the GitHub fetch on every upgrade, so a leftover file silently reinstalled the old version on the next click. The file is now removed after a successful install. - Stale package files are cleared when an install starts - packages left behind by an interrupted install or an older version (the download, the intermediate archive, the staging folder) are removed before extraction, so they can neither shadow the new download nor leave the FAT32 card half-full.
- Status checks no longer stall the web UI - the maintenance page fires its status check twice per load, and a slow WAN fetch on a cold cache used to queue every other request behind it - including the upload POST - until the browser gave up on the stalled transfer, leaving a partial file behind. A stale cache now answers immediately with the last known values and refreshes in the background; an in-flight marker prevents duplicate refreshers, and the page shows a checking state while one is running.
- Uploads are verified for completeness - the assembled upload file is checked against the declared body length; a transfer that dropped mid-way is reported as "Upload incomplete (X of Y bytes received)" and deleted, never installed.
- The upgrade survives a browser refresh - the install now runs detached from the HTTP request: the button answers immediately, and closing or refreshing the page cannot kill it. Double-clicking during an install is blocked, and the page reflects the in-progress state.
- Letter-suffix version comparisons - 0.4.3a vs 0.4.3b vs 0.4.2 are now compared correctly (numeric fields first, then the letter suffix), so the pre-release field and its button are labelled right when a pre-release is newer than the stable tag.
- SD space back after install - the downloaded package and its intermediate archive are removed after a successful extract (~13 MB on a FAT32 card).
Documentation & release plumbing
- README: documents the web-UI package install and clarifies that the SD card remains mandatory.
- Service-page upload note corrected: on a FAT32 card, a tgz install also updates the baseline (rootfs and home), not just the yi-hack tree.
- Version bumped to 0.4.3 (package name, in-tree version file, README links).
For testers
- Upgrading from 0.4.3c through the web UI is itself a good end-to-end test, and exercises the baseline fix: a pre-release baseline should no longer be refused with "Wrong baseline version".
- On the Service page, confirm the Pre-Release field shows a tag (0.4.3c or newer), not a branch name, and that "Upgrade to Pre-Release" is disabled when the installed version already matches.
- #388 is verified by logic-port tests, not yet against a live MQTT broker - worth an end-to-end check on a camera with MQTT enabled.
- The install flow is the main new surface: try an upload + install with config present (now on the Service page), and a reinstall with a different package version.
- For the hardened download: on a WAN camera, start a GitHub install and cut the camera's network (or the router's) partway through; the install should fail cleanly with a retry suggestion, not reboot into a broken state.
- Refresh or close the browser tab mid-install (GitHub path): the install should continue and the camera should reboot into the new version.
- Deliberate downgrade: with the camera on a pre-release and an older stable tag published as latest, "Upgrade to Latest" should announce the downgrade and complete the install.
Thanks to @grzesiczek1 for the RTSP fixes (#495, #496).
Full Changelog: 0.4.3a...0.4.3d