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

[Richard238]

@sdetweil

With no caps? Still doesn’t work.

config: {
				weatherProvider: "openweathermap",

[sdetweil]

@Richard238 again show the whole config, xxx out the api key

Start w
position
and config
provider
type ( default is current)
apikey
lat
lon

the 3.0 apikey requires a credit card backing, right?

[Richard238]

@sdetweil

		{
			module: 'weather',
			header: 'Current zzzzzzzzzzzzz  weather: ',			
			position: 'top_right',
			config: {
				weatherProvider: "openweathermap",
				lat: 111111111111111, 
				lon: 1111111111111111111111,
				apiKey: "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
				type: 'current',
				units: 'config.units'
				//location: 'zzzzzzzzzzzzzzz',
		}
		},

I must have had that API key for aeons, don’t ever remember it having a c/card behind it.
Maybe it’s out-of-date.

[sdetweil]

@Richard238 yes they told us the old free api was being terminated. only the new api exists, so we changed the defaults

but other users have reported the 2.5 apikey still works
see the 1st post on this topic

[Rberry91]

@sdetweil hi Sam,

I have added a credit card and added the extra codes from the article and it doesn’t load.

[sdetweil]

@Rberry91 if you have the 3.0 apikey you dont add any extra parms

just type, apikey, lat and lon

[Rberry91]

@sdetweil
It still says invalid date

Sorry so many questions

[sdetweil]

@Rberry91 open the developers window, ctrl-shift-i,
select the console tab,
and enter weath in the filter field

do you see errors? like 401, 403

[Rberry91]

@sdetweil
Hi yes error 401

[sdetweil]

@Rberry91 401 means the apikey is invalid