Skip to content

0.4.3b

Pre-release
Pre-release

Choose a tag to compare

@alienatedsec alienatedsec released this 19 Nov 10:35
· 2 commits to test-0.4.3 since this release

0.4.3b (pre-release)

Second pre-release of the 0.4.3 cycle. Everything from 0.4.3a, plus fixes to the firmware status and pre-release check in the web UI, and the file-based update moved to the Service page.

New features

  • Firmware install from the web UI (#329) - a Firmware Package section on the Service page accepts a yi_dome_x.x.x.tgz upload, 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_UID on 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.

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 with jq (bundled in the package, built via src/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_files carried correct timestamps but an empty files array. 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.1 equality 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".
  • 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_conf helper.
  • 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.

Documentation & release plumbing

  • README: documents the web-UI package install and clarifies that the SD card remains mandatory.
  • Version bumped to 0.4.3 (package name, in-tree version file, README links).

For testers

  • On the Service page, confirm the Pre-Release field shows a tag (0.4.3b 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.

Thanks to @grzesiczek1 for the RTSP fixes (#495, #496).

Full Changelog: 0.4.3...0.4.3b