Skip to content
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

Investigate behaviour for forecast_at_place #392

Open
csparpa opened this issue Jan 27, 2022 · 0 comments
Open

Investigate behaviour for forecast_at_place #392

csparpa opened this issue Jan 27, 2022 · 0 comments
Milestone

Comments

@csparpa
Copy link
Owner

csparpa commented Jan 27, 2022

If you need to access forecaster's will_have_storm(), will_have_hurricane(), etc., which one_call doesn't give access to (as far as I could find) but don't care about the frequency, "3h" instead of "daily" does the trick.

Weirdly enough, this won't work even with a new API key:

forecast = mgr.forecast_at_place('Roma', 'daily').forecast # Invalid API key

but this does work:
forecast = mgr.forecast_at_place('Roma', '3h').forecast

Not sure if this is a problem in pyowm or on the openweathermaps side, but this workaround helped me (pyowm==3.2.0).

Originally posted by @ividal in #316 (comment)

@csparpa csparpa added this to the 3.3.0 milestone Jan 27, 2022
@csparpa csparpa modified the milestones: 3.3.0, 3.4.0 Feb 14, 2022
@csparpa csparpa modified the milestones: 3.4.0, 4.0.0 Aug 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant