Read the statement by Michael Teeuw here.
2.29.0 Weather Module w/api v3.0 works, sort of…
-
-
@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” -
@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”.
-
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.
-
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!!!
-