You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Setting an absolute path for the "Export Path" leads to unavailable files in the webui
Steps to Reproduce (for bugs)
Set Export path to an absolute path (for example /mnt/NAS/Birdnet-Go/ to use an external drive mounted in /mnt)
Go in the webui
Even though the spectrogram are displayed, the files cannot play and responds with a 404 (Not Found). Example of url : http://192.168.178.23:8087/%2Fmnt%2FNAS%2FBirdnet-Go%2F2025%2F01%2Fdendrocopos_major_98p_20250117T144009Z.wav
Expected behavior
Accept usage of absolute paths, starting with /
Actual behavior
Absolute paths are accepted in the UI, but lead to impossibility to show data in the UI
Screenshots
Environment
Birdnet-Go homeassistant addon accessed through ip:port (so bypassing HA's specific elements)
$ ./birdnet-go
🐦 BirdNET-Go v (built: 2025-01-15T20:45:29Z), using config file: /root/.config/birdnet-go/config.yaml
System Information
Device:
Raspberry Pi (specify model, e.g., Raspberry Pi 4 Model B)
Other SBC (please specify)
PC/Server N100 amd64 system
OS: HA os
OS Version: based on
Hardware specs:
CPU: N100intel
RAM: 16gb
Storage type and size: 256GB SSD
For Non-Raspberry Pi Linux Users
Have you tested with the latest dev branch container image?
Yes
Additional context
Possible Solution
not sure - add a modifier to avoid "//" in the url ?
The text was updated successfully, but these errors were encountered:
Issue Type
Description
Steps to Reproduce (for bugs)
/mnt/NAS/Birdnet-Go/
to use an external drive mounted in /mnt)http://192.168.178.23:8087/%2Fmnt%2FNAS%2FBirdnet-Go%2F2025%2F01%2Fdendrocopos_major_98p_20250117T144009Z.wav
Expected behavior
Accept usage of absolute paths, starting with /
Actual behavior
Absolute paths are accepted in the UI, but lead to impossibility to show data in the UI
Screenshots
Environment
Birdnet-Go homeassistant addon accessed through ip:port (so bypassing HA's specific elements)
System Information
For Non-Raspberry Pi Linux Users
Have you tested with the latest dev branch container image?
Additional context
Possible Solution
not sure - add a modifier to avoid "//" in the url ?
The text was updated successfully, but these errors were encountered: