YA-WAMF 2.21.0 makes the species leaderboard easier to trust and read, clarifies what the telemetry graphs count, and gives long-running classification work safer failure handling.
What's new
- See visits instead of repeated frames. The day, week and month leaderboards count a bird that stays on the same camera as one visit. The all-time view continues to count detections and labels them as such.
- See the evidence behind a species. The leaderboard distinguishes birds confirmed by you, also heard by BirdNET-Go, heard only, and camera only. With eBird configured, camera-only species without a recent nearby report are marked for a closer look. A trend appears only when YA-WAMF has enough history to compare its full previous window.
- Explore when birds visit. The weekday heatmap can show one of your leading species, with readable counts on pointer, touch and keyboard. Temperature and wind have their own aligned charts below the timeline.
Smoother everyday use
- A struggling classifier stops a backfill sooner. Repeated classifier-unavailable results stop the job with accurate partial counts, so you can safely rerun the range after recovery. Confirmed native worker crashes can recover with the same model on CPU in an isolated process; an unhealthy accelerator remains visible in Health.
- Telemetry trends show completed days. Today's partial heartbeat count no longer looks like a sudden loss of installations. The dashboard distinguishes installations reporting in the selected window from those retained over 90 days.
- Review destructive actions in the app. Cache clearing, record purging and other destructive controls use a confirmation dialog that works in browsers and embedded views. Audio History and Species charts now use Chart.js, with keyboard controls and reduced-motion support.
Before you update
- No special steps. Back up your data and configuration as usual, then wait for the container health check to pass. This release has no new database migration or required setting change.
- Unsuffixed image tags remain the full compatibility image. See the provider-family guidance before choosing an optional CPU, Intel or CUDA image.
Good to know
- Watch long backfills with EVA02 Large on Intel GPU. On one Intel host, a short compatibility check passed but a full-history run later stalled, produced lease errors, and dropped live detections. If Health shows similar failures, stop the backfill, choose another provider verified on your host, and check Health during the rerun. A validated Intel NPU may be a better fit where supported. Issue #490 remains open while the reporter retests their installation.
- Accelerator compatibility depends on the model and host. The new recovery path limits damage from a failed runtime; a short compatibility check does not certify sustained operation.
- Nearby-report flags need eBird and are a prompt to review a sighting, not proof that the classifier is wrong.
See the full changelog for the complete technical record.