2.29.0 Weather Module w/api v3.0 works, sort of…

[reilley]

Updated MM2 today to v2.29.0. Learned quickly that the api change forces you subscribe to the One Call v3.0 and provide a payment method but no big deal as long as you stay under 1000 calls per day.

It took some configuration editing to get the current and forecast sections working, specifically adding the apiVersion parameter and of course the new api key. It still didn’t work, so I added weatherEndpoint ‘/onecall’ and this resolved the problem, but now the location header reads “America/New York”. If you use One Call , the location and locationId parameters are ignored. Just not sure why the first shows incorrectly.

Anyone else having this issue?

[reilley]

OK, it would appear when /onecall is used, the OpenWeatherMap.js script controls the header and you’re either going to get:

${data.timezone}

or

${data.city.name},${data.city.country}

I’m see the first option, timezone. It’s correct, but I don’t want timezone. I want city/country. Booooo!!!

[dawookie1979]

@reilley Hi, i cant get mine to load!!

[sdetweil]

@reilley for the doc

note MagicMirror is case sensitive

locationId is incorrect

[reilley]

@sdetweil - Hi Sam! I’m not even calling locationID in my script.

Here’s what I have:

module: “weather”,
position: “top_center”,
config: {
weatherProvider: “openweathermap”,
type: “current:,
weatherEndpoint: ‘/onecall’,
lat: ‘34.17188’.
lon: ‘-84.57056’,
apiVersion: ‘3.0’,
apiKey: 'nunya”

[reilley]

@sdetweil - Oh okay - I was wondering why you mentioned case. That was just a typo here on my part. When I was using it, it was “locationID”.

[HeikoGr]

forecast need lot / lan set. locationID as in api 2.5 isn’t working anymore (with api 3.0) sorry, didn’t read your post properly…

openweather doesn’t add geoname in response. so i guess it’s the timezone.

[reilley]

OK, it would appear when /onecall is used, the OpenWeatherMap.js script controls the header and you’re either going to get:

${data.timezone}

or

${data.city.name},${data.city.country}

I’m see the first option, timezone. It’s correct, but I don’t want timezone. I want city/country. Booooo!!!

[Peter]

@reilley did you get it working with city, country?
Peter

[reilley]

@Peter - Unfortunately, not yet. I’m wondering if anyone has been able to using the 3.0 API!

[HeikoGr]

I got it working and think there are a few tricky typos in your config.

module: “weather”,
position: “top_center”,
config: {
weatherProvider: “openweathermap”,
type: “current:,
weatherEndpoint: ‘/onecall’,
lat: ‘34.17188’.
lon: ‘-84.57056’,
apiVersion: ‘3.0’,
apiKey: 'nunya”

Line 5: closing quotation marks are missing
Line 7: point as line ending instead of comma
Line 10: wrong quotation mark

Your config entry type is from line 5 - 10.

[Peter]

@HeikoGr does it show country and city in the header?
Peter

[HeikoGr]

@Peter no, unfortunately not

[Peter]

@HeikoGr what does it show in the header?
And do you see the right weather for your location?
Peter

[HeikoGr]

@Peter it shows the timezone „EUROPE/BERLIN“, but the weather is correct.

[Peter]

@HeikoGr can you share your config?
Without the key and only the weatherpart.
Thanks!
Peter

[HeikoGr]

@Peter of course

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

[Peter]

@HeikoGr thanks.
I will try tomorrow.
I will let you know!
Peter

[reilley]

@HeikoGr - so as it was said before, we’re not going to see our city the way we did under v2.5 of the API. That’s going to likely need a response from the MM2 dev team because if /open call is used, it’s timezone/city only. It seems api 3.0 broke the location/locationID functionality when using “current” or “forecast”. Or did someone else get it to work?

[sdetweil]

@reilley that’s open weather 3.0 is /onecall only

nothing we can do but force you to specify the header yourself
does that work or get overridden by the weather data?

i am not where i can test

[reilley]

@sdetweil - sure, I’d be happy to force my header if that’s possible. So for example, with forecast I would want it to say:

Forecast - Canton, GA

Or similar, of course. I could test it if you could let me know where to insert that line of code.