-
-
Notifications
You must be signed in to change notification settings - Fork 8
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
All locations searched show "Weak or No WiFi connection" #46
Comments
I tried to change the search provider to open metro and it works slightly better. I can now search, but using my current location, I get the same error. |
Interesting. With some more testing, I've found that some search terms are fine but some error! Maybe it's a rate limit of sorts? |
I think it must be a rate limit issue. I got this sometimes, but waiting 20 seconds, and then reloading solved it. The reason some places load and others don't is because of caching. So the ones it could load before, it saved the data for 15 minutes for those, so even if after that you got the error, going back to them it will still loaded them. Switching search providers probably wont do anything, because after you press enter it will try to fetch the weather data too for that place, and that's probably where the rate limiting comes in. So i suggest waiting a bit, and seeing if that helps. If waiting doesn't help and you still get the error, then maybe i'll have to add some code to see what is timing out, and then maybe try to fix it) |
Awesome, thanks. Do you think it would be a good idea to have an easy way to allow people to use their own API keys? That could help solve the rate limiting problem. |
Yeah, so i guess i could do that, for some providers, but for example if you look at open-meteo or met-norway neither have any api keys. |
Hi,
When I search any location and try to view the weather, it takes a long time to load, then shows a weak or no WiFi connection message. I currently have perfectly fine WiFi. The default of "New York" loads fine as well.
Thanks!
The text was updated successfully, but these errors were encountered: