-
-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BirdWeather stops BirdNET-go #114
Comments
I see that BirdNET-Go is reporting BirdWeather upload failures due to timeout, these are quite common for me also. I think BirdWeather is often running out of capacity and just running too slow for it to be able to process any uploads, even birdweather.com map is often refusing to load. Can you be more specific what you mean by "the system stops after some time.", do you mean that in your case BirdNET-Go stops processing new detections or just BirdWeather uploads are stopped? |
Mhmm okay, The webpage stopped working (birdnetgo...:8080), no access for a few minutes Is there a difference between the birdnetpi BirdWeather Id and BirdNET-Go Id ? It never uploaded any data to BirdWeather- or better said- it never appeared on BirdWeather. |
After almost 6 months of trouble free use I just had this happen to myself, long lasting network connectivity errors to BirdWeather caused birdnet-go process eventually get stuck. I'll fix this soon. Hangup that is, I can't fix network connectivity errors. |
Ursprünglich gepostet von @tphakala in #68 (comment)
Edit: the config.yaml doesnt get lost, i just couldn't access it when it "crashed" (birdnet-go)
If I fill the BirdWeather Id and enable BirdWeather upload, the system stops after some time.
The BirdWeather Id is fine, it works on birdnetpi (I haven't used it for a week or so)
On birdnetgo- BirdWeather doesn't show anything (yep, I waited for an hour)
Website config (set it up on website)
No output for a few minutes- restarting the console and logging back in and it works again for a few minutes.
Config.yaml
Some of the output of webui.log
The text was updated successfully, but these errors were encountered: