Version 2.30.0 weather module, stuck loading, worked fine before upgrade

angeliKITTYx

@sdetweil I signed up for the new subscription and regenerated my API key (just to be safe). I remember it taking some time to show up the first time,so hopefully it will be back to normal in the morning! Thanks for the information.

angeliKITTYx

@sdetweil After 24 hours, I’m still stuck at “loading…” could you confirm if I have the config set up properly? I signed up for the Onecall 3.0 API subscription, and it says it’s active.

		{
			module: "weather",
			position: "top_left",
			config: {
				weatherProvider: "openweathermap",
				apiVersion: "3.0",
				type: "forecast",
				weatherEndpoint: "/forecast",
				lat: "xxx",
				lon: "-xxx",
 				apiKey: "cxxx",
				roundTemp: true,
				showPrecipitationAmount: true,
				tableClass: "medium",	
				colored: true,
			}
		},
		{
			module: "weather",
			position: "top_right",
			config: {
				weatherProvider: "openweathermap",
				apiVersion: "3.0",
				type: "current",
				weatherEndpoint: "/weather",
				lat: "xxx",
				lon: "-xxx",
 				apiKey: "cxxx",
				showWindDirectionAsArrow: true,
				showSun: false,
				roundTemp: true,
			}
		},

sdetweil

@angeliKITTYx said in Version 2.30.0 weather module, stuck loading, worked fine before upgrade:

  		apiVersion: "3.0",
  		type: "forecast",
  		weatherEndpoint: "/forecast",

for apiVersion 3.0, you can ONLY use /onecall as the endpoint

those endpoints /forecast, /… are only good with the old 2.5 apiVersion

angeliKITTYx

@sdetweil not going to lie, but I don’t see anywhere saying we have to use /onecall as the endpoint, but that worked for me for both of my current and forecast modules. The location is stating my time zone city (which is 8 hours north) , but the information seems to be correct when comparing it to a weather website. Thank you for the help.

sdetweil

@angeliKITTYx openweather only provides /onecall in v3.0
that is why the default is 3.0 and /onecall

you don’t have to specify them since this release

location? where do you see that?

angeliKITTYx

@sdetweil screenshot

you can see on the right module it says “America/New_York” which is my timezone city, but my lat/lon is set to my home many states south. They used to both say that, but I added the “appendLocationNameToHeader” parameter to the left one to see what it would look like.

Before the API update, it would properly display my home city. I’m pretty sure it’s displaying the correct weather information, but we surprisingly have similar weather to NY right now so it’s hard to confidently confirm.

sdetweil

@angeliKITTYx yes, new openweather api does not return the location info anymore. so you have to add
appendLocationToHeader: false
and add your own header

i will add that info to the top entry as well

angeliKITTYx

@sdetweil yeah that’s what I ended up doing. Thank you again for all your help the last few days! Glad to have everything back to normal.

Richard238

Ran the update, weather module failed , read this thread and can now have either weather or forecast. Can we no longer have both, like before?

sdetweil

@Richard238 two instances, type: as appropriate. NO endpoint setting. The v3 openweather api only supports /onecall (already set as default)
https://forum.magicmirror.builders/post/123079
The config.js.sample shows two instances