YA-WAMF 2.20.3 makes reviewing visits clearer, keeps accelerator validation from being lost to unrelated runtime updates, and gives you control over incorrect BirdNET detections in your local history. Thank you to everyone who reported problems, shared examples and helped test the fixes.
What's new
- Remove an incorrect bird call from YA-WAMF and undo it if needed. Owners can hide a BirdNET detection locally. Hidden calls leave audio history, summaries and future matches, and a repeated MQTT message cannot bring them back. Undo restores recent calls to live correlation immediately.
- Accelerator validation survives unrelated runtime updates. Eligibility is tracked for each provider. When its own runtime changes, a previously validated active accelerator gets one automatic recovery check, with the Dashboard showing the check and any CPU fallback.
Smoother everyday use
- Photographs and frame choices stay tied to the recorded species. Fallback crop selection avoids promoting another bird, frame previews stay consistent with the chosen photograph, and regenerating choices preserves existing selections when source media is unavailable.
- Review the bird without labels or controls covering it. Detection titles, playback controls and frame choices sit below the photograph. Work through the queue also shows the species name on desktop and phones, respecting your common/scientific-name preference.
- Health previews stay visible. Rejected-frame previews escape the activity card and remain inside the viewport, with clearer outcome labels in the timeline.
Before you update
- Back up your data and configuration, then update normally. Startup applies a reversible migration that adds local hide state to audio detections. Existing detections remain visible, and there is no required setting change. Wait for the container health check to pass. Downgrading that migration removes the hide state, so previously hidden audio detections can reappear.
- 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
- Local audio removal affects YA-WAMF only. It does not delete a detection from BirdNET-Go or automatically follow deletions made there.
- Accelerator compatibility remains model- and host-specific. This release does not make ConvNeXt Large compatible with Intel GPU; use a supported provider and the built-in validation flow.
See the full changelog for the complete technical record.