BirdNet-Go: reviewing detections not possible

[Sonnenfleck]

Creating a bug report/issue

• I have searched the existing open and closed issues

Required Information

• DietPi version | 9.19 and 9.20 beta
• Distro version | Trixie
• Kernel version | PVE-DietPi 6.12.57+deb13-amd64
• SBC model | Proxmox VM

Additional Information (if applicable)

• Software title | Birdnet-Go, freshly installed
• Can this issue be replicated on a fresh installation of DietPi? - Yes

Problem

When I try to either approve a bird detection or mark it as a false positive, I get the error message "The requested resource was not found". The detection status remains unchanged ("unverified").

[JappeHallunken]

Probably the same issue as here:
tphakala/birdnet-go#1504

[Sonnenfleck]

Yep, exactly. Commit 385dbc5 seems to be the fix for this?

[JappeHallunken]

Yes, but I just see right now that the version we pull in our script is hardcoded. Why is that @MichaIng ?

So a reinstallation via dietpi-software would not update the App, the install script needs a fix I think.
You could just edit dietpi-software by yourself on your device and bumb it to nightly-20251214

[Sonnenfleck]

You could just edit dietpi-software by yourself on your device and bumb it to nightly-20251214

If anyone is looking for a quick fix: I just exchanged the executable in /opt/birdnet with the nightly-20251214 executable and ran patchelf --set-rpath /opt/birdnet/ /opt/birdnet/birdnet-go so it makes use of the libtensorflowlite_c.so. When dietpi-software is adapted to the new (or latest) nightly, it should update just fine.

[MichaIng]

How lucky we are that this release happened 1 hour after the DietPi release 🙄. And I was relieved to only see a small list of 3 enhancements around the sound card selection in the release notes. Seems that was a WIP, seeing the 1+ page formatted release notes now.

Shall we push a life patch for this?

EDIT: Was my post yesterday lost or did I not send it properly? Anyway, I was suggesting to check server logs, but that is obsolete now.

And yes, I agree that auto-detection of latest release would be better. Was a contributor decision to keep the tag hardcoded until next stable release. But such has usually more downsides than upsides, which is why we auto-detect the latest tag/release in almost all other cases.

EDIT2: Our CI covered it already, just come one day/one hour too late: https://github.com/MichaIng/DietPi/pull/7865/changes

[oturn]

What's the current recommended fix for this? Should I exchange the executable, or bump the version in diet pi-software and reinstall? If bumping the version is best, could someone please detail that process?

[JappeHallunken]

Execute the following

sed -i "s/\(local bnet_vers='nightly-\)[0-9]\{8\}\('\)/\120251214\2/" /boot/dietpi/dietpi-software
dietpi-software reinstall 127

[oturn]

Thank you. This installed the latest nightly perfectly, but the error "The requested resource was not found." when reviewing a detection still occurs.

[Sonnenfleck]

Thank you. This installed the latest nightly perfectly, but the error "The requested resource was not found." when reviewing a detection still occurs.

Same here.
-> tphakala/birdnet-go#1504 (comment)

Even with a fresh install.