Full Changelog: https://github.com/billacuda/LarisVMS/compare/v0.211.0-beta...v0.213.1-beta

LarisVMS 0.213.1

This release rolls up 0.212.0, 0.213.0 and 0.213.1. The headline: live AI boxes and the Zones motion overlay now line up with the live video. It also adds per-node health on the dashboard and fixes footage that outlived its retention.

Upgrading

• Run the new Web MSI on the server. Database changes apply automatically when it starts.
• Approve the new node build under Admin → Node builds. Recorder nodes update themselves once it's approved.
• No settings need changing. Old footage records left behind on a node clean themselves up over the next few hours (see below).

0.213.1

Changed

• Zones editor: a note now explains that changes can take up to 30 seconds to reach the recorder node.

0.213.0

Fixed

• Zones editor: the motion overlay on grid cells and polygon zones no longer trails moving objects. Motion is now timed by when each frame arrived from the camera, the same way the AI boxes are.

0.212.0

Added

• Dashboard node cards: each recorder node shows CPU, memory and network load, plus total recording fps. With object detection on, it also shows events and human, vehicle and animal counts for the last hour, 24 hours, 7 days and 30 days.
• Drag-to-zoom on live and View tiles: drag a box to zoom in, the same as Playback. While zoomed, use the reset button in the tile's lower right, or right-click the video, to return to 1×.
• Settings → Events: a "Reset all object colors to defaults" button.

Changed

• AI boxes stay on objects through pauses: a moving object keeps its box and badge until it has been still for the detection idle timeout, instead of blinking off every time it stops.
• Playback "Now": jumps to the newest recorded footage instead of the current time, which usually had nothing playable yet.

Fixed

• Live AI boxes line up with moving objects instead of trailing behind them.
• Footage outliving its retention: recordings left outside a node's current storage folder, after a storage path change or a camera moving to another node, were never deleted. The server now tells the owning node about overdue footage wherever it is, and removes the record only once the node confirms the file is gone. Nodes also remember unreported deletions across restarts.
• Admin → Nodes leftover-footage warnings: they now handle keep-forever and archive retention correctly, flag footage a node hasn't confirmed deleting, ignore a failover backup's own recordings, and let you forget records left on a deleted node.
• IPv6: live view, playback, snapshots, exports and node controls failed for nodes and media proxies that check in over IPv6 (#4).
• Playback drag-to-zoom: after zooming out or leaving fullscreen, dragging panned instead of selecting a new area. Panning also stays within the frame now.
• AI box labels: they no longer run off the right edge of the video or overlap each other.
• Live tile badges: object badges no longer cover the Motion badge.
• Fewer vision frame drops: the vision service causes far less memory churn, and a startup-counting error that inflated the drop figure is fixed.
• GPU-batched slicing: some custom ONNX models were rejected over tiny rounding differences. Models that can't be verified safely now fall back to per-tile detection.
• Settings → Events: a color's Reset button now counts as an unsaved change.

For administrators

• New setting Vision:MaxCamerasPerSession (default 1): lets cameras on the same model share one AI session, trading some detection speed for lower memory use.
• Hardware recommendations: the README now includes minimum and recommended specs and a GPU guide.