Read the statement by Michael Teeuw here.
2.29.0 Weather Module w/api v3.0 works, sort of…
-
@Peter no, unfortunately not
-
@HeikoGr what does it show in the header?
And do you see the right weather for your location?
Peter -
@Peter it shows the timezone „EUROPE/BERLIN“, but the weather is correct.
-
@HeikoGr can you share your config?
Without the key and only the weatherpart.
Thanks!
Peter -
@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: ',' } },
-
@HeikoGr thanks.
I will try tomorrow.
I will let you know!
Peter -
@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?
-
@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
-
@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.
-
@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!