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

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.