Birdnet-go issue

tom_l · April 4, 2025, 1:43pm

Latest update isn’t working for me at all.

Audio device missing after update

opened 04:04AM - 02 Apr 25 UTC

## Issue Type - [x] Bug report - [ ] Feature request - [ ] Question / Support #…# Description After updating from the Feb 2025 to March 2025 release using the install script: ``` curl -fsSL https://github.com/tphakala/birdnet-go/raw/main/install.sh -o install.sh bash ./install.sh ``` I no longer have any audio capture devices available. I am using a USB sound card and a reboot did not help. ![Image](https://github.com/user-attachments/assets/5b6cb483-8b57-43d3-b056-e1bea035fefb) ## Steps to Reproduce (for bugs) 1. Update using the install script. ## Expected behavior Sound capture device to be available after the update. ## Actual behavior No sound capture devices available. ## Screenshots [If applicable, add screenshots to help explain your problem] ## Environment ### Version Information (build date) Provide the following line from your system: ``` $ ./birdnet-go [Paste the output line here, which should look like this:] BirdNET-Go build date: YYYY-MM-DDTHH:MM:SSZ, using config file: /path/to/config.yaml ``` ### System Information - Device: - [x] Raspberry Pi 4 Model B - [ ] Other SBC (please specify) - [ ] PC/Server (please specify) - OS: Raspberry Pi OS - OS Version: Raspberry Pi OS Bullseye - Hardware specs: - CPU: Raspberry Pi 4 Broadcom BCM2711 - RAM: 4GB - Storage type and size: 128GB Samsung Endurance SD - Additional hardware (if applicable): - USB Audio device: Ugreen USB 2.0 to External 3.5mm AUX Sound Card - Other peripherals: Nil ### For Non-Raspberry Pi Linux Users Have you tested with the latest dev branch container image? - [ ] Yes - [ ] No - [ ] Not applicable (Windows/macOS user) If not, first test with the latest dev branch container image and see if the issue is already fixed. ``` $ docker pull ghcr.io/tphakala/birdnet-go:dev ``` ## Additional context [Add any other context about the problem here, such as any custom configurations or specific usage scenarios] ## Possible Solution [If you have a suggestion for fixing the bug or implementing the feature]

Kyle · April 4, 2025, 2:00pm

I saw your recent discussion around this.

Just to rule out upgrade problems, did you try fully resetting the app and installing it fresh?

(not saying this is a good solution, but it could be a workaround).

Are you running it natively or through a virtualized env (like docker)?

Based on your earlier post, you mentioned your devices are connected through a USB capture device. I might not be fully able help troubleshoot as all of my devices are connected over rtsp and I’m running in a docker container.

tom_l · April 4, 2025, 8:31pm

Nope. I am not doing a full reinstall and reconfigure. If that is needed every update then I’m giving this project a miss.

I’m using docker.

Kyle · April 4, 2025, 8:48pm

I don’t really want to derail the thread too much after this comment, but is this something that has happened before with a previous upgrade?

I understand not wanting to deal with a project if it happens frequently. It could just be a bug introduced with one of the updates between versions. If you’re willing to help debug back on the GitHub issue, you might be able to pin down when the exact change happened.

tom_l · April 4, 2025, 8:57pm

Moved to a separate topic.

First time an update has gone awry.

My SD card died a couple of months ago so I tried the install script / Docker for the first time as I read it was recommended. Before that I was running native.

So the issue has only occurred since I’ve used the install script / Docker to update.

It’s also the fact that the developer is not willing to admit it may be a bug with their install script.

I’m definitely willing to supply any needed info. to fix this.

Kyle · April 5, 2025, 12:58am

Since there have been so many changes between February and March for the capture.go file, all I can guess is that some change made the stored capture device incompatible with what is stored now (probably in a way that prevents from re-saving it). So I do agree that a bug was introduced. It’s just difficult to pinpoint where.

I only found the project for the first time last week, so I haven’t had a chance to go through an upgrade (other than between branches that I was playing around in).

It does look like there are a few settings.Debug lines in the capture.go
file. So if you turn on the debug mode in the config.yaml, it might help post some more useful information back in the github thread.

github.com/tphakala/birdnet-go

internal/conf/config.yaml

e159aca6b


      
          # BirdNET-Go configuration
          
          debug: false              # print debug messages, can help with problem solving
          
          # Node specific settings
          main:
            name: BirdNET-Go        # name of node, can be used to identify source of notes
            timeas24h: true         # true for 24-hour time format, false for 12-hour time format
            log:
              enabled: true         # true to enable log file
              path: birdnet.log     # path to log file
              rotation: daily       # daily, weekly or size
              maxsize: 1048576      # max size in bytes for size rotation

But I’m not sure how much attention it will get when others have been able to get it back up and running by resetting. I agree, not a great solution, but I’d bet you can backup your database files and restore them after a reset. same with your config.yaml file. Hoping it isn’t something that happens again.

From what I’ve seen, the author has been coding in bursts, making significant development over the past few months. Which is pretty awesome to see!

But I’m going to guess that they probably have their hands full. I didn’t interpret their response as rude, but instead as busy. Though I do believe better directions could have been provided for the user on how to record debug logs for further investigation.