Skip to content

YA-WAMF 2.13.0

Choose a tag to compare

@Jellman86 Jellman86 released this 19 Jul 09:10
· 616 commits to main since this release
46bc0eb

YA-WAMF 2.13.0

YA-WAMF 2.13.0 makes everyday feeder monitoring calmer and more reliable. It adds guided, hardware-validated model setup, refreshes the main observation surfaces, and hardens long-running signed-in sessions.

What's new

  • Models are installed with proof they work on your hardware. The guided model flow downloads, validates, benchmarks, and selects the fastest passing CPU, Intel GPU, Intel NPU, or NVIDIA option before enabling a new model.
  • The application now feels like one coherent field desk. The Dashboard, Explorer, Species details, Leaderboard, BirdNET-Go History, detection details, settings, diagnostics, and first-run setup share a calmer hierarchy with fewer repeated cards and better phone and keyboard behaviour.
  • High-quality snapshots choose the strongest available bird crop. YA-WAMF compares Frigate tracking with its crop detector, keeps the best reliable result, and reconciles recent detections after restarts.

Smoother everyday use

  • Signed-in tabs stay responsive over time. Owner-only polling is single-flight, bounded by timeouts, suspended in hidden tabs, and cleaned up across authentication and deployment changes instead of accumulating requests.
  • Live camera status is honest before the viewer opens. The header reports all-live, mixed, offline, checking, or unavailable state from Frigate health, while the full camera viewer fetches only the selected camera and loops naturally between feeds.
  • Fresh installs are simpler to finish. A re-runnable setup wizard covers account, cameras, model validation, snapshot quality, telemetry, and optional integrations without exposing low-level choices that YA-WAMF can determine safely.

Before you update

  • No special steps. This release has no database migration and a normal image update is sufficient. Existing theme choices and active models are preserved; the validation gate applies when enabling a newly installed model.

Good to know

  • A fresh install now starts in dark mode. Existing appearance choices are unchanged, and Light, Dark, and System remain available under Settings → Appearance.
  • Hardware acceleration remains capability-checked per host and model. A device is selected only after it compiles and produces valid output; CPU remains the safe fallback when an accelerator does not pass.
  • Owner diagnostics have tighter trust boundaries. Integration probes validate their target and refuse redirects, artifact downloads resolve only known evaluation runs, and detailed exceptions remain in server logs.

See the full changelog for the complete technical record.