Default weather module not showing after MM update

[01ZerosOnes01]

@Jarhead96097 Thanks for your info. Hopefully someone can come up with the fix.

[sdetweil]

@01ZerosOnes01 @Jarhead96097

how did u upgrade,and from what version?

I don’t see any significant code change here this release…

[01ZerosOnes01]

I keep the mirror updated so I am assuming it was updated from the last version.
I updated by first issuing git stash then git pull && npm install --only=prod --omit=dev
followed by git stash apply

All other default and third party modules work.

Thank for your help it is appreciated.

[mumblebaj]

@01ZerosOnes01 I had my API authorized and the module works just fine with your location data. The only change I made was not add quotes around the locationID.

locationID: 4891010,

[Jarhead96097]

@sdetweil I also upgraded from 2.19.0, which had been upgraded from 2.18.0. No problems before today.

[Jarhead96097]

@mumblebaj Well, unfortunately, removing the quotes around locationID did not resolve the issue on my configuration. I still receive “Uncaught SyntaxError: Unexpected token” in weather.js:159.

[01ZerosOnes01]

Raspberry Pi 4 2GB
Well this is what i have done so far.
Removed SD card with broken default weather module.
With new SD card installed fresh 64bit Pi OS
Fresh manual install of MagicMirror
“name”: “magicmirror”,
“version”: “2.20.0”,
“description”: “The open source modular smart mirror platform.”,
“main”: “js/electron.js”,

Entered my openweathermap credentials
and
Walla! the weather module works.
I have no idea why the weather module broke after the MagicMirror update. I will be following this thread to see if it is a problem or it was just a fluke.
Good luck and thanks to all that contribute.
Now I just have to reload my third party modules and customizations.

[Jarhead96097]

@01ZerosOnes01 @sdetweil Glad to hear you’re up and running on a fresh install… I’m hoping to avoid having to rebuild mine. Any other thoughts?

And thanks for your time in advance!

[sdetweil]

@Jarhead96097 would be interested in knowing if my upgrade script avoided this problem

[Bearded1ne253]

@01ZerosOnes01 you do not have a “ to start your string, only one at the end…