It works. Thank you

@reilley unfortunately openweather doesnt respond with geoname but with timeszone… so it’s euroe/berlin in my case.

i am in texas and my lat is 30

in short: forecast needs

• lat/lon , locationID isn’t working for forecast
• weatherEndpoint: ‘/onecall’, must be set

This works for me;

        {
            disabled: false,
            module: "weather",
            position: "top_right",
            config:
            {
                // See 'Configuration options' for more information.
                weatherProvider: 'openweathermap',
                weatherEndpoint: '/onecall',
                apiKey: 'xxx',
                apiVersion: '3.0',
                lat: '49.8',
                lon: '8.49',
                type: 'forecast',
                colored: true,
                fade: false,
                maxNumberOfDays: 3,
                degreeLabel: 'true',
                showWindDirectionAsArrow: 'true',
                decimalSymbol: ','
            }
        },

I’d help you write yours, but I’m struggling with mine as well so you might get better assistance from the gurus here!

apiVersion: “2.5”,

to my config, now its all fine again.

documentation is linked from the top menu here

Thanks

i have same issue. I have signed up for the v3 api. Does anyone have a config for me to copy my api into?

my code:
{
module: “weather”,
position: “top_left”,
header: “Weather Forecast”,
config: {
weatherProvider: “openweathermap”,
type: “forecast”,
location: “Haverhill”,
locationID: “2647310”, //
apiKey: “LEFT BLANK”
}

Thank you for information

I see. Thank you for your quick reply. Any free API is available now? I will move

"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."

So V2.5 is only working because openwaethermap didn’t fully shut it down even the deadline is over. It can happen any day.

V3 submittion need to provide a credit information. It is bad idea. Well, I will keep using 2.5 api key and 2.28 old weather module in this moment.

I wish MM can revert it later since version 2.5 is totally free. Thanks.