As of now, if the BirdNET-Pi station is not connected to the internet when a detection occurs, that detection is not published to BirdWeather.
This can be an issue for some users, for example users who turn their WiFi router off when leaving home for some time (as is my case ;) ), or stations in the field with inconsistent connectivity as mentioned in this (old) post in a discussion on mcguirepr89’s repo.
One possible solution could be a dedicated service that would monitor network status change and automatically publish any past detection to BirdWeather when connectivity is restored.
I have already started working on this, and my draft is accessible here. It’s been working fine on my station for a couple of weeks. However, there are a few pending points to complete:
I have written a new birdweather_publication.py script, which currently includes code duplication, notably with reporting.py. I plan to refactor this.
Publishing detections to BirdWeather involves specifying a “soundscape” (an audio file) with its start/end datetimes, and a “detection” with its start/end datetimes. As of now, multiple detections from the same original audio file share the same timestamp in BirdNET-Pi’s DB, meaning they can’t be published as distinct detections to BirdWeather. I have already thought of a solution for this, which I describe in this issue.
If maintainers of this project agree that this would be a useful feature, I would be happy to finalize this, and then submit a PR :).
Hi,
As of now, if the BirdNET-Pi station is not connected to the internet when a detection occurs, that detection is not published to BirdWeather.
This can be an issue for some users, for example users who turn their WiFi router off when leaving home for some time (as is my case ;) ), or stations in the field with inconsistent connectivity as mentioned in this (old) post in a discussion on mcguirepr89’s repo.
One possible solution could be a dedicated service that would monitor network status change and automatically publish any past detection to BirdWeather when connectivity is restored.
I have already started working on this, and my draft is accessible here. It’s been working fine on my station for a couple of weeks. However, there are a few pending points to complete:
birdweather_publication.pyscript, which currently includes code duplication, notably withreporting.py. I plan to refactor this.If maintainers of this project agree that this would be a useful feature, I would be happy to finalize this, and then submit a PR :).
Thanks!