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

[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

[Richard238]

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

ionToHeader: false

default config sample works, but that’s using openmeteo, not openweathermap, is that correct?

		{
			module: "weather",
			position: "top_right",
			config: {
				weatherProvider: "openmeteo",
				type: "current",
				lat: 40.776676,
				lon: -73.971321
			}
		},
		{
			module: "weather",
			position: "top_right",
			header: "Weather Forecast",
			config: {
				weatherProvider: "openmeteo",
				type: "forecast",
				lat: 40.776676,
				lon: -73.971321
			}
		},
		{

openweathermap.js I have as

		apiVersion: "3.0",
		apiBase: "https://api.openweathermap.org/data/",
		// weatherEndpoint is "/onecall" since API 3.0
		// "/onecall", "/forecast" or "/weather" only for pro customers
		weatherEndpoint: "/onecall",

[sdetweil]

@Richard238 leave off those parms. Defaults to 3.0 etc

Just put in your 3.0 apikey and lat/lon
And of course set the provider

[Richard238]

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

leave off those parms.

Which ones, sorry?

[sdetweil]

@Richard238 all the openweather ones you showed

[Richard238]

@sdetweil

This gives the ‘undefined, invalid date’ error on the MM

		{
			module: 'weather',
			header: 'Current xxxxxxxxxxxxxxx  weather: ',			
			position: 'top_right',
			config: {
				weatherProvider: "openweathermap",
				lat: 11111111, 
				lon:   2222222,
				apiKey: "33333333333"

			}
		},

[sdetweil]

@Richard238 and you used real lat/lon

[Richard238]

@sdetweil

Yes, real Lat:Lon used

[Richard238]

@sdetweil

Do the L:L and API key live in the openweathermap.js file, or the config.js file? Or both?

[sdetweil]

@Richard238 all config goes in config.js
Never need to edit any other file

[Richard238]

@sdetweil

openweathermap.js is unchanged

WeatherProvider.register("openweathermap", {


	providerName: "OpenWeatherMap",

	// Set the default config properties that is specific to this provider
	defaults: {
		apiVersion: "3.0",
		apiBase: "https://api.openweathermap.org/data/",
		// weatherEndpoint is "/onecall" since API 3.0
		// "/onecall", "/forecast" or "/weather" only for pro customers
		weatherEndpoint: "/onecall",
		locationID: false,
		location: false,
		// the /onecall endpoint needs lat / lon values, it doesn't support the locationId
		lat: 0,
		lon: 0,
		apiKey: ""
	},


config.js shows

	{
		module: 'weather',
		header: 'Current zzzzzzzzzzzzzzzz  weather: ',			
		position: 'top_right',
		config: {
			//weatherProvider: "openweathermap",
			providerName: "OpenWeatherMap",
			type: "current",
			lat: nnnnnnnnnnn,
			lon: -nnnnnnnnnnnnn,
			apiKey: "aaaaaaaaaaaaaaaaaaaaaaaaaaa"
			//type: 'current',
			//location: 'xxxxxxxxxxxxxx',
			//locationID: 'zzzzzzzz',  //ID from https://www.openweathermap.org
			//apiKey: 'aaaaaaaaaaaaaaaaaaaaaaaaaaa'
		}
	},

[sdetweil]

@Richard238

providerName: “OpenWeatherMap”

That is not the correct property name

From the doc
https://docs.magicmirror.builders/modules/weather.html#usage

[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