Default weather module stuck loading after latest MM update

[sdetweil]

@karsten13 dang I get that wrong EVERY time!

[karsten13]

@sdetweil said in Default weather module stuck loading after latest MM update:

@karsten13 dang I get that wrong EVERY time!

one of the reasons I wrote my own njk …

[pritikin71]

@karsten13 Wow… you kill me… what a Shame jaja Sorry for the misunderstood and great idea your config/

@sdetweil thanks too

[Sampleswow]

@pritikin71 said in [Default weather module stuck loading after latest MM

  {
  	module: "weather",
  	CalendarClasses: "current",
  	position: "top_right",
  	header: "Weather Forecast",
        disabled: false,
  	config: {
  		weatherProvider: "openweathermap",
  		weatherEndpoint: "/onecall",
  		//updateInterval: "20",
  		type: "current",
  		tempUnits: "imperial",
  		degreeLabel: "false",
  		location: "XxXxX",
  		locationID: "XXxXXX", //ID from http://bulk.openweathermap.org/sample/city.list.json.gz; unzip the gz file and find your city
  		apiKey: "XxXXXXxxXXXXxXXxXXxX",
            showFeelsLike: "false",
  		lat: "2XXXX350",
            lon: "-8X.3XXxX915"	
  		
  	}

My code looks exactly like this i even generated a new api key paid setup payment and i am still only getting loading on my npm start i have Zero Errors im so confused

[sdetweil]

@Sampleswow weather is done all in browser, so you have to open the browser developers window condole tab to see any errors

ctrl-shift-i

[Sampleswow]

@sdetweil
Thanks for your reply i have found the error it is,
Failed to load resource: the api.openweathermap
server responded with a
status of 401 (unauthorized)

how do i adjust this?

[sdetweil]

@Sampleswow said in Default weather module stuck loading after latest MM update:

status of 401 (unauthorized)

your api key is incorrect

the 3.0 apikey requires a credit card, right?

see this too
https://github.com/MagicMirrorOrg/MagicMirror/issues/3574#issuecomment-2423544713