github Jellman86/YetAnother-WhosAtMyFeeder v2.24.0
YA-WAMF 2.24.0

one hour ago

YA-WAMF 2.24.0 makes your feeder's history easier to read and to trust. Settings is organised by
what you came to do and has a search, the record shows the bird and the decision side by side, the
Leaderboard keeps its counts after cleanup removes old photos, and you can choose how far apart two
captures can be and still count as one visit. Status and Health now say only what was measured, and
the release fixes several Safari and iPhone layout problems.

What's new

  • Find any setting, and read Settings at a glance. Settings now has six sections in place of
    twelve tabs: Cameras & connection, Identifying birds, Alerts,
    Sharing & integrations, Storage & upkeep and Display. Each opens with what most people
    need, and the rest waits under More options. A Find a setting box finds a setting by its
    name, what it does or a word such as "password", "GPU" or "backup", in your language, and opens it
    for you. Press / on Settings to reach it. Every setting is still there, and old links and
    bookmarks such as /settings/models still open the right place. See
    How Settings is laid out.
  • Your Leaderboard keeps its history after cleanup. Before cleanup removes a day's captures, it
    now saves how many captures and visits each species had that day. The Leaderboard's chart and each
    species' weekday and month charts count those days from the saved totals, so seasonal trends
    reach back past your retention period. The photos and clips for those days are still deleted, and
    the charts mark the days whose counts come from daily totals. Totals start when you update.
    See Daily totals.
  • Choose how long a gap still counts as one visit. On a busy feeder, birds of one species that
    come back every few seconds used to merge into one long visit. Set the gap under
    Settings → Identifying birds → Counting visits, from 5 to 300 seconds. It stays at 60 unless
    you change it. The Dashboard, Explorer, Leaderboard, statistics and Garden visits all follow it
    from the next page you open, with no restart. A shorter gap gives you more, shorter visits, but it
    cannot count individual birds.
  • The record shows the bird and the decision together. On a laptop or desktop the photograph,
    the name, the score and Confirm sit in one column, with the family tree, the description and
    nearby sightings in a reading column beside them. A tall crop is shown whole, no longer between
    black bars. Rarely used actions such as Hide and Delete this visit permanently wait
    under More actions. On a phone the identification comes straight after the photograph.
  • System status never disappears. Where the sidebar's System status card does not fit, a
    one-line summary takes its place, such as "2 issues need attention", linking to Health. Each state
    is said in words with a shaped dot, so it never depends on colour alone, and amber appears only
    when something needs you. On the Health chart, the CPU and each accelerator keep their own colour
    in every theme.
  • Audio history reads like the Leaderboard. Calls heard are shown by weekday and hour in the
    Leaderboard's activity grid, in your own time zone, with the same window bar, figures and chart
    layout. The busiest hour is now your local hour; before, it was the hour in UTC.

Smoother everyday use

  • A Garden bird that sat still keeps its photo. Frigate often throws away an event whose object
    never moves, snapshot and all, so a chicken moved to Garden used to read "Photo expired". Garden
    now keeps YA-WAMF's own copy of the frame its bird model classified when Frigate has no snapshot.
    The clip is still Frigate's, and the capture says so when Frigate kept none.
  • Safari and iPhone behave properly. With Reduce Motion on, a new Text size now reaches
    every word in Safari straight away, without a reload. The record's photograph fills its frame,
    notification rows keep their words inside the row at large text sizes, and opening another page in
    Safari while one is still loading goes where you asked, without a surprise reload. Scrollbars on a Mac hide when idle again.
  • Health no longer fails on a busy feeder. /health and the diagnostics page could answer with
    an error while detections were arriving. That is fixed, and your detections were never affected.
  • Health raises fewer false alarms. A snapshot Frigate deliberately discarded, a short Frigate restart or
    a single recovered GPU decode no longer shows as a problem. You can Dismiss a warning you have
    read; it comes back if it happens again. Health also names the setting that really dropped an
    event, such as the minimum confidence floor.
  • Tests tell the truth. A Discord, Telegram or Pushover test now passes only when the channel
    accepted the message, and otherwise says why and what to check. Model and connection states read
    the same everywhere and never call a model running when its files are missing.
  • Record the light level with each detection, if you want to. Name a lux sensor as the
    Illuminance entity under Settings → Sharing & integrations → More options → Home Assistant
    weather
    , and each new detection keeps its reading in the record's Conditions row and in the
    API. It is only ever a measurement, never an estimate. See
    Home Assistant.
  • The Intel GPU reading stays right on the xe driver. It no longer sinks towards zero after a
    while when the GPU is busy.
  • Less work for your server. A quiet page makes far fewer requests, pages open with a few files
    instead of dozens, and on the Intel image Garden motion photos are decoded on the GPU, using about
    a third of the CPU they did.
  • Easier API scripts. /api/events and /api/visits accept start_date=today, one
    /api/visits request returns up to 500 visits, and dates are calendar days in your time zone. See
    Calendar days.

Before you update

  • Back up /config and /data first. This update applies four database migrations to your
    detection history on startup: the daily totals, the light reading, a flag on cached species
    descriptions, and a new photo source for Garden. The species catalogue is unchanged. No settings
    need changing. Wait for the container health check to pass after the update.
  • Going back to v2.23.2 loses the new values. A downgrade keeps your detections, but it deletes
    the daily totals, which are the only copy of the counts for days cleanup has already removed. It
    also drops the stored light readings, and relabels Garden's kept frames as Frigate snapshots.
    Updating again restores the tables, not those values. Changing only the tag is not a rollback;
    see the
    upgrade and rollback guide.
  • Check the browser on a wall tablet. The dashboard now needs Chrome or Edge 111, Firefox 128,
    or Safari 16.4 or newer. On an iPhone or iPad that means iOS or iPadOS 16.4. An older device, such
    as an iPad that stopped at iPadOS 15, still opens the page but draws colours, borders and focus
    rings wrongly. See
    supported browsers.
  • Check scripts that read the API or /health. A date you pass is now a calendar day in your
    time zone rather than a UTC day, so a bird at 23:30 is no longer counted on the next day.
    /health now reports degraded while the MQTT broker is disconnected or Frigate does not answer;
    it still answers with HTTP 200. A settings save that is refused answers 422 with the field
    named, where a missing address scheme used to answer 400.
  • Keep your image family unless you mean to change it. Unsuffixed tags remain the full
    compatibility image. The images now run Python 3.13, with identical results on CPU, Intel GPU and
    Intel NPU. The Intel image is about 26 MB larger and decodes motion recordings on the GPU when
    /dev/dri is passed through; without it, it decodes on the CPU and says so. See
    Hardware Acceleration
    before choosing an optional CPU, Intel or CUDA image.

Privacy, retention and public access

  • Daily totals outlive your retention period. They hold one count of captures and visits per
    species per day, with no photo, clip, time of day or camera. Guests never see a day that began
    before their own history window. Delete all history deletes the totals too, and its
    confirmation says so.
  • Garden may keep one more photo. A domestic bird in Garden can keep YA-WAMF's own copy of the
    frame it was classified from. Like other kept Garden media, it counts towards your storage limit,
    shows in Space used, and ages out with your media retention.
  • A clearer delete choice for missing Frigate events. The policy is now labelled
    Delete records YA-WAMF has no photo for. A record whose photo YA-WAMF still holds is marked
    missing instead of deleted, so the media integrity scan can no longer remove the only photo left.
  • Your Frigate address stays private. When Frigate cannot be reached, guests see "Could not reach
    Frigate" with no address at all. As the owner you see only scheme://host:port, and logs drop
    user names, passwords and tokens from addresses.
  • About lists what really leaves your network. It is built from when each request is made, says
    what each one sends, and now includes Google Fonts, Wikipedia and map tiles. Guests see requests
    that depend on owner settings marked Owner only.
  • The visit gap applies to guests as well, so shared pages count visits the same way you do.

Good to know

  • Health dismissals are kept in memory. A restart, or Clear error history, brings dismissed
    warnings back with the rest of the error history.
  • The light level is only recorded from now on. Older detections have no reading, and changing
    the sensor later leaves recorded readings as they are.
  • Totals for days before the update may be low. A day that started before you updated may
    already have lost captures to an earlier cleanup, so its charts say it may be low.
  • Safari was checked in a browser engine, not on an iPhone. The Safari fixes were tested in
    WebKit on Linux, which covers the layout but is not the same as a physical iPhone or Mac.
  • Not in this release. Running several models together
    (#804) and feeder refill
    markers (#946) are still
    being reviewed.

Thanks

  • @aav7fl for pinning down why the Intel GPU reading sank on the xe
    driver in #944, with the
    counter-wrap diagnosis, a diagnostics bundle and several days of retesting. Also for the request
    to keep history past retention in
    #949 and the request for
    "today" in the API in #950,
    and for confirming both on the development image.
  • @darkslen1 for the visit gap request in
    #1044, explained with a busy
    feeder's numbers and a working stopgap, and for the fix to duplicate rows in the species picker in
    #1043.
  • @zobe123 for the light level request in
    #945, which set out exactly
    how it should behave, and for the feeder refill idea in
    #946, which is still being
    reviewed.
  • @giulianob for the multiple-model proposal in
    #804, which is still being
    reviewed.

See everyone who has helped,
the full changelog
for the complete technical record, and
every change since v2.23.2.

Don't miss a new YetAnother-WhosAtMyFeeder release

NewReleases is sending notifications on new releases.