You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We would like to inform you about our plans to complete the migration from One Call 2.5 to One Call 3.0 that started 2 years ago. In line with this, access to One Call 2.5 will be finally closed in June 2024.
One Call 3.0 provides you with significantly advanced business-demanded features such as a minute forecast for 1 hour, 4 days forecast for any timestamp, a daily forecast for 8 days, including a human-readable summary, historical data (45-year archive) for timestamps, and with daily aggregation, 1.5-year long-term forecast with daily aggregation, and others."
We have still 2.5 in the provider file as default, must be changed to 3.0.
The text was updated successfully, but these errors were encountered:
I too got the email about the change to the onecall 3.0 and have tried to do some testing and it seems that we need to change the apiVersion from 2.5 to 3.0 but we also need to change the weatherEndpoint from /weather to /onecall (at least when using the default type=current).
via mail:
"Dear OpenWeather user,
We would like to inform you about our plans to complete the migration from One Call 2.5 to One Call 3.0 that started 2 years ago. In line with this, access to One Call 2.5 will be finally closed in June 2024.
One Call 3.0 provides you with significantly advanced business-demanded features such as a minute forecast for 1 hour, 4 days forecast for any timestamp, a daily forecast for 8 days, including a human-readable summary, historical data (45-year archive) for timestamps, and with daily aggregation, 1.5-year long-term forecast with daily aggregation, and others."
We have still 2.5 in the provider file as default, must be changed to 3.0.
The text was updated successfully, but these errors were encountered: