Repository navigation
0.4.3b #499
alienatedsec
announced in
Announcements
0.4.3b
#499
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
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
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.ONVIF_UIDon the Configurations page), falling back to the camera serial number when unset.Bug fixes
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.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.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".read_confhelper.rRTSPServer's key-frame check. No effect on current H.264 v5 streams; a correctness fix for future stream types.Documentation & release plumbing
For testers
Thanks to @grzesiczek1 for the RTSP fixes (#495, #496).
Full Changelog: 0.4.3...0.4.3b
This discussion was created from the release 0.4.3b.
All reactions