-
-
Notifications
You must be signed in to change notification settings - Fork 271
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
OpenWeatherMap API 2.5 deprecation #442
Comments
When I looked into OpenWeatherMap 3.0 API they demanded credit card information even for their free tier. Therefore I decided to move to another provider with a generous tier. In a first step I rewrote the current weather report (i.e. no forecast) to use it. I haven't received any commentary on streetturtle#442 so I don't know where your mind was going. If OpenWeatherMap phases out its 2.5 API and nobody else intends to use their 3.0 one, I offer to take this implementation instead. Signed-off-by: Andr茅 Jaenisch <andre.jaenisch@posteo.de>
I've opened #448 in case someone else is relying on Weather reporting as well. No forecast yet (as I wrapped my head around how to get the current weather rendered in Lua). |
FWIW I just spotted #394 which uses another service. Opinions? |
The widget in #394 is visually different from this one, I'll ask the maintainer if they would be ok to move it in this repo. I think it would be too much work to make theese widgets look the same, as the data those two APIs (OWM and wttr) return could be different. |
Hey @Ryuno-Ki, thank you for starting this migration! |
Hey there 馃憢
I recently received an e-mail by OpenWeatherMap that they are going to sundown API 2.5 in June this year.
They were so kind to link to https://openweathermap.org/one-call-transfer for an upgrade path.
Since I'm using OpenWeatherMap myself I was wondering whether you would be open to a PR upgrading to the new API?
How can we communicate that a new API token will be required? I couldn't come up with a good way for this myself.
The text was updated successfully, but these errors were encountered: