@HeikoGr - lol, adjusted my headers and saw that the timezone was concatenated to the header. Snapped a photo to post and saw your comment. That fixed it!!! Thank you and Sam both!!!
Read the statement by Michael Teeuw here.
Posts
-
RE: 2.29.0 Weather Module w/api v3.0 works, sort of…
-
RE: 2.29.0 Weather Module w/api v3.0 works, sort of…
@HeikoGr - sorry, I didn’t copy/paste from the actual editor. I typed all that in and made a few errors! Sorry for the goose chase!
-
RE: 2.29.0 Weather Module w/api v3.0 works, sort of…
@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.
-
RE: 2.29.0 Weather Module w/api v3.0 works, sort of…
@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?
-
RE: 2.29.0 Weather Module w/api v3.0 works, sort of…
@Peter - Unfortunately, not yet. I’m wondering if anyone has been able to using the 3.0 API!
-
RE: 2.29.0 Weather Module w/api v3.0 works, sort of…
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!!!
-
RE: v2.29.0 weather module issue
@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.
-
RE: 2.29.0 Weather Module w/api v3.0 works, sort of…
@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”.
-
RE: 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” -
RE: v2.29.0 weather module issue
@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!