Skip to content

bug: After update the range filter is not working #3932

Closed

Description

@Lenbok

BirdNET-Go version / build date

2026-07-13T17:06:31Z

Install method

Docker via install.sh (recommended installer script)

Device type

Raspberry Pi 4

Operating system and version

Debian Linux

Audio source

Network audio stream - RTSP / RTSPS (e.g. IP camera)

Hardware details

Version: 20260713
Build date: 2026-07-13T17:06:31Z
Operating system: Debian Linux
Architecture: aarch64
Hardware: Raspberry Pi 4 Model B Rev 1.4
Environment: Docker

Description

I updated my working birdnet go instance ( version nightly-20260429) to 20260713, and after the update I started getting detections for weird species. I haven't changed any settings so I expected the update to preserve the detection characteristics.

If I go into species settings there's this warning/error:
Image

And in the analysis settings there is this:
Image
It's showing over 6000 species (normally for my location there are around 100 species)

My location in general settings looks fine:
Image

Steps to reproduce

Be on the old version mentioned above
Update the the new version mentioned above

Expected behaviour

Detection behaviour (including range filters) should be preserved after the update.

Actual behaviour

No range filters seem to be in place

When did this start?

Worked before, started after I updated

Relevant log output

Support dump (optional, but the single most helpful thing you can add)

No response

RTSP source (only if the bug is RTSP related)

No response

Pre-submission checks

  • I am running the latest release or have tested with the :dev container image.
  • I have searched existing open and closed issues and this does not appear to be a duplicate.

Additional context

No response

Activity

  1. tphakala commented on Jul 15, 2026

    @tphakala
    Owner

    See this issue #3932, but in short, make sure BirdNET v3.0 Geomodel is installed and active

  2. Lenbok commented on Jul 15, 2026

    @Lenbok
    ContributorAuthor

    OK thanks, that seems like something that should have happened automatically!

  3. tphakala commented on Jul 15, 2026

    @tphakala
    Owner

    Yes it is a regression in 20260712 which removed tflite support for range filter, new geomodel is ONNX so it works fine. I will fix this.

  4. heidar commented on Jul 15, 2026

    @heidar

    I had the same issue, just had the default model. I manually installed the v3.0 Geomodel and it's all fixed now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions