YA-WAMF 2.20.2 makes Frigate-backed visits more dependable from first detection to final playback,
and makes Settings → Health clearer about what happened when a frame did not become a visit.
What's new
- Health explains every detection outcome. The What happened timeline is now distinct from
the Dashboard field log and clearly marks recorded visits, policy-filtered frames and pipeline
faults. Recorded rows open the real visit record, while filtered previews work with touch,
pointer and keyboard input. - Resource use shows the accelerator each worker actually loaded. The process table now keeps
CPU, accelerator and memory separate. A worker is labelled NPU or GPU only after its runtime
reports that provider, so a CPU fallback is never disguised as accelerated work.
Smoother everyday use
- Frigate video seeks and plays across Safari, iOS, Chrome and Firefox. YA-WAMF uses Frigate's
HLS stream where available and retains the existing MP4 path for downloads, cached media and
older Frigate versions. Thanks to @kevingrubbs for reporting the progressive-stream failure and
helping trace its browser-specific symptoms. - Bird crops stay useful after a Frigate event expires. Event-time crop coordinates and media
retention hints are preserved, the MQTT and REST coordinate formats are handled explicitly, and
a late refresh keeps the existing bird crop unless it has a trustworthy replacement. - Completed detections stay completed—and notify you. Saving and notification queuing now
finish before slower Frigate and media follow-ups. Final-mode notifications run for terminal
events again and can use the cached photograph after the upstream event has gone.
Before you update
- No special steps. This release has no database migration, removed setting or changed
default. Update the image normally and wait for the health check to pass. - Unsuffixed image tags remain the full compatibility image; see
hardware acceleration if you use a provider-specific
flavour.
Good to know
- Fleet-health summaries include older reporting clients again. Legacy issue detail and current
replay-safe telemetry are combined without double counting, while the existing three-install
privacy floor remains in place.
See the full changelog
for the complete technical record.