v2.29.0 weather module issue

[kent79]

@MarcLandis

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.

[MarcLandis]

@kent79 from openweathermap.com:

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

[kent79]

@MarcLandis

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

[MarcLandis]

@kent79 V3 is free for 1000 calls a day and unless you update the weather every minute you probably won’t reach that limit.

[kent79]

@MarcLandis

Thank you for information

[dawookie1979]

Hi,

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”
}

[reilley]

@dawookie1979 - Be sure to add apiVersion: ‘3.0’ to your config

[dawookie1979]

@reilley Hello, where do i add it? can you help me edit my script?

Thanks

[sdetweil]

@dawookie1979 see the documentation. its a property in the config section of the weather module configuration

documentation is linked from the top menu here

[Andreas1956]

@MarcLandis
i only added

apiVersion: “2.5”,

to my config, now its all fine again.

[sdetweil]

@Andreas1956 tgat means you gave the old apikey, which will fail ‘soon’

[Peter]

@sdetweil Sam, do you know how many calls the default weather module makes per day?
Am I right: default is every 10 minutes, so 24x6 per day?
I have two Magic mirrors (1 for me and 1 for my daughter) using the same API.
I would like to use the API (3.0) for free, so use not more than 1000 calls per day.
Thanks for your answer in advance.
Peter

[reilley]

@dawookie1979 - just add it somewhere in the config for your weather module. I added "apiVersion: “3.0"” just above the apiKey.

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

[HeikoGr]

@kent79 @dawookie1979
it’s all in the docs - but you need to read it carefully.

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: ','
            }
        },

[reilley]

@HeikoGr - What are you seeing for the header? Does it say [country]/[city] and if so, is it correct? Mine is saying “America/New York”, when I’m in Canton, Georgia.

[sdetweil]

@Peter yes, every 10 minutes, 6 times per hour

[sdetweil]

@HeikoGr is that gepos right?

i am in texas and my lat is 30

[HeikoGr]

@sdetweil yes, lat/lon is correct as I am in Germany :-D

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

[kent79]

@reilley

It works. Thank you