OpenWeather loaded but info is empty since update

sdetweil

@SdR see https://forum.magicmirror.builders/topic/19323/version-2.30.0-weather-module-stuck-loading-worked-fine-before-upgrade?page=1

from the troubleshooting section

SdR

@KristjanESPERANTO said:

@SdR, did apiVersion: "2.5" really still work before the MM update? That version was deprecated a long time ago (June 2024). See https://forum.magicmirror.builders/topic/18662/modules-using-openweather-api-need-review.

Yes, with the settings I posted it still worked like a charm… until the MM recent update.

SdR

@sdetweil said:

@SdR see https://forum.magicmirror.builders/topic/19323/version-2.30.0-weather-module-stuck-loading-worked-fine-before-upgrade?page=1

from the troubleshooting section

I checked this section, but couldn’t relate it to my situation. This basicly states to change to API 3.0 or change the provider.

I try to change the provider like advised by @kristjanesperanto but I really like the openweather, so I hope he is able to find and solve the issues based on the info I posted.

SdR

@kristjanesperanto I have changed it, as test, with the following copy/paste of a different topic, but got the exact same result… module is showing empty and not loading any weather info:

	{
		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
		}

KristjanESPERANTO

@SdR I tested this config on my side and it works. I only had to add one missing closing bracket in your snippet.

Do you see any errors in the terminal?

Also, after pulling the new version, did you run: node --run install-mm?

If openmeteo is also empty, this looks like a general config/runtime issue, not only an OpenWeather API issue.

Please show us the systeminformation from the terminal. Looks like this:

[2026-04-07 21:13:27.184] [INFO]  [systeminformation] 
####  System Information  ####
- SYSTEM:   manufacturer: Micro-Star International Co., Ltd.; model: MS-7D75; virtual: false; MM: v2.36.0-develop
- OS:       platform: linux; distro: Debian GNU/Linux; release: forky/sid; arch: x64; kernel: 6.19.10+deb14-amd64
- VERSIONS: electron: 41.1.1; used node: 25.9.0; installed node: 25.9.0; npm: 11.12.1; pm2: 6.0.14
- ENV:      XDG_SESSION_TYPE: wayland; MM_CONFIG_FILE: undefined
            WAYLAND_DISPLAY:  wayland-0; DISPLAY: :0; ELECTRON_ENABLE_GPU: undefined
- RAM:      total: 61881.24 MB; free: 42885.43 MB; used: 18995.81 MB
- OTHERS:   uptime: 45 minutes; timeZone: Europe/Berlin

sdetweil

@KristjanESPERANTO and a git status

SdR

@KristjanESPERANTO I have used the following command guide to update the MM :
bash -c “$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)” apply

So i’m not sure if node --run install-mm is still required then.

im not a expert so i did a little chatgpt search how to pull this info and this is what i got:

System Information

{
manufacturer: ‘Raspberry Pi Foundation’,
model: ‘Raspberry Pi 4 Model B Rev 1.1’,
version: ‘b03111’,
serial: ‘10000000f0815816’,
uuid: ‘’,
sku: ‘-’,
virtual: false,
raspberry: {
manufacturer: ‘Sony UK’,
processor: ‘BCM2711’,
type: ‘4B’,
revision: ‘1.1’
}
}

CPU

{
manufacturer: ‘Sony UK’,
brand: ‘BCM2711’,
vendor: ‘ARM’,
family: ‘Cortex-A72’,
model: ‘3’,
stepping: ‘r0p3’,
revision: ‘b03111’,
voltage: ‘’,
speed: 1.5,
speedMin: 0.6,
speedMax: 1.5,
governor: ‘ondemand’,
cores: 4,
physicalCores: 4,
performanceCores: 4,
efficiencyCores: 0,
processors: 1,
socket: ‘SOC’,
flags: ‘fp asimd evtstrm crc32 cpuid’,
virtualization: false,
cache: { l1d: 131072, l1i: 196608, l2: 1048576, l3: ‘’ }
}

Memory

{
total: 1935228928,
free: 96256000,
used: 1838972928,
active: 828510208,
available: 1106718720,
buffers: 59150336,
cached: 833519616,
slab: 339734528,
buffcache: 1232404480,
reclaimable: 298536960,
swaptotal: 1934618624,
swapused: 10747904,
swapfree: 1923870720,
writeback: 0,
dirty: 0
}

@sdetweil regarding git status i have the following info:

simon@SimPi:~/MagicMirror $ git status
On branch master
Your branch is up to date with ‘origin/master’.

Changes not staged for commit:
(use “git add …” to update what will be committed)
(use “git restore …” to discard changes in working directory)
modified: package-lock.json
modified: package.json

Untracked files:
(use “git add …” to include in what will be committed)
core.2761
core.4822
installers/
run-start.sh
splashscreen/

no changes added to commit (use “git add” and/or “git commit -a”)

sdetweil

@SdR ok. The upgrade script is mine

We meant the system-info section of the MagicMirror startup messages.

Runstart.sh is mine for when electron is not found

Can you
git diff package.json

And
ls node_modules/electron

SdR

@sdetweil tnx for the commands, this helps :)

i have:

diff --git a/package.json b/package.json
index 5cad85d…c0ae855 100644
— a/package.json
+++ b/package.json
@@ -87,6 +87,7 @@
“*.css”: “stylelint --fix”
},
“dependencies”: {

          "@electron/rebuild": "^4.0.3",
          "@fontsource/roboto": "^5.2.10",
          "@fontsource/roboto-condensed": "^5.2.8",
          "@fortawesome/fontawesome-free": "^7.2.0",

and

simon@SimPi:~/MagicMirror $ ls node_modules/electron
abi_version checksums.json cli.js dist electron.d.ts index.js install.js LICENSE package.json path.txt README.md

sdetweil

@SdR ok. Looks like something added electron/rebuild
And fonts

SdR

@sdetweil Ok, as mentioned I only did the update command as mentioned earlier.

Is there something I need to do now to make it work again?

sdetweil

@SdR can you show me the end, last 20 lines of the MagicMirror/installers/upgrade.log

SdR

@sdetweil appreciate the help!

Here they are:

magicmirror@2.35.0 postinstall
git clean -df fonts vendor modules/default

magicmirror@2.35.0 prepare
[ -f node_modules/.bin/husky ] && husky || echo no husky installed.

no husky installed.

added 379 packages in 1m

82 packages are looking for funding
run npm fund for details
npm notice
npm notice New major version of npm available! 10.9.4 -> 11.12.1
npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.12.1
npm notice To update run: npm install -g npm@11.12.1
npm notice
npm install completed - Sun Apr 5 10:07:56 CEST 2026 on base

added 594 packages in 30s

260 packages are looking for funding
run npm fund for details
fixing sandbox permissions

Checking for modules with removed libraries
downloading dumpactivemodules script
no modules found needing npm refresh
restoring custom.css
removing git alias
we stashed a set of files that appear changed from the latest repo versions. you should review them
Upgrade ended - Sun Apr 5 10:08:29 CEST 2026

sdetweil

@SdR >Sun Apr 5 10:08:29 CEST 2026

there was a bug in the upgrade I fixed at 21:00 US Central time

can you edit ~/MagicMirror/installers/mm.sh

and change the

npm start

to

npm run start:x11

then you can
pm2 restart MagicMirror

SdR

@sdetweil

I have 2 in there after “DISPLAY”… do I need to change both?

#!/bin/bash
cd /home/simon/MagicMirror

if [ $(ps -ef | grep -v grep | grep -i -e xway -e labwc | wc -l) -ne 0 ]; then

if WAYLAND_DISPLAYis set, use it, else set to -0

export WAYLAND_DISPLAY=${WAYLAND_DISPLAY:=wayland-0}
npm run start:wayland
else
DISPLAY=:0 npm start
fi

#DISPLAY=:0 npm start

sdetweil

@SdR said:

DISPLAY=:0 npm start <----- change this one
fi

#DISPLAY=:0 npm start <— this one is commented out (#)

SdR

@sdetweil
made the change and restarted MM but same result, is there a log can can show you after the restart?

sdetweil

@SdR ok,

do this, stop of there is an error with one command

pm2 stop all
cd ~/MagicMirror
rm -rf node_modules
rm package-lock.json
npm run install-mm
npm run start:x11

SdR

@sdetweil ok, did all the commands, no error shown but with the same result again (not showing any weather and weather forecasting).

sdetweil

@SdR Ok, in 2.35 we rewrote the data collection portion of the weather module
it does NOT support the old version 2.5 openweather api anymore.

so, to use the openweather provider, you must get a new 3.0 apikey from openweather which requires a credit card, and you get (today) 1000 free api calls. (so net free)

from a year ago, in the troubleshooting section

https://forum.magicmirror.builders/topic/19323/version-2.30.0-weather-module-stuck-loading-worked-fine-before-upgrade?page=1