Default Weather module still not displaying

[OldSunGuy]

The only thing I noticed was you’re trying to use http and the default is https for the apiBase.

Weather Options

[Jarhead96097]

@OldSunGuy thanks… I didn’t make any changes to the script before updating to 2.20.0 , but I changed to https. Unfortunately, it didn’t make a difference. Neither the current nor the forecast weather module instances are showing, and I’m still receiving the “Uncaught SyntaxError: Unexpected token.” error on line 159 of weather.js. And of course, I haven’t changed anything in weather.js.

Any other ideas? I appreciate your time!

[sdetweil]

@Jarhead96097 remove all the options except

apiKey
and
locationID

default type is current
default provider is openweathermap

[Jarhead96097]

@sdetweil thanks… Well, no change. I’ve tried that and also copied the portion of the weather module from the original config.js, which was renamed as config.js.sample during setup. Both attempts still result in the Unexpected Syntax Error: Unexpected token message coming from line 159 of weather.js.

You’re always very helpful, thanks for your time. Any other ideas?

[sdetweil]

@Jarhead96097

ok, I just did this

		{
			module: "weather",
			position: "top_right",
			config: {
				locationID: "361058",
				apiKey: "xxxxx"
				}
		},

try that with your openweathermap apiKey

[Jarhead96097]

@sdetweil no luck. Still receiving the same error on line 159, and no display on the MM.

[sdetweil]

@Jarhead96097

this is on pi, or windows, or ??

ok, do this

cd ~/MagicMirror
rm -rf node_modules
npm install 
#added
git checkout modules/default/weather/weather.js
git status

then try again

[Blackeye]

@Jarhead96097 Could be the comma after “true” on the last line of config … not necessary, and causes an error when I run a :check

[sdetweil]

@Jarhead96097

I added a command above to restore the original weather.js from the git repo

[Jarhead96097]

@sdetweil I added “npm audit fix” as there was 1 high severity vulnerability found. It didn’t solve the vulnerability (didn’t try “npm audit fix --force”), and I’m getting the same error.