@Phantomkommander said:

Currently, if a client reconnects during the backend’s “protection phase,” it stays on “Loading…” until the next scheduled fetch. It would be the icing on the cake if the module could immediately push the cached data to a newly connected client, instead of making it wait for the next real API call.

Good suggestion. I’ve opened a PR (https://github.com/MagicMirrorOrg/MagicMirror/pull/4121) to implement that :)

@iamktothek You don’t need node-fetch. The fetch API is built-in meanwhile :-)

@Dentrass-0 Cool 👍 You could now remove the npm install command from the README.

@Dentrass-0 You could ask ChatGPT how to replace axios with fetch in your module.
That would even have the advantage of simplifying the installation and update process, since npm install would no longer be necessary.

@Dentrass-0 Nice! 👏

But why are you using axios? And why an super outdated version from 2023?
axios should be easily replaceable with the built-in fetch API.

@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

@BKeyport Okay, no rush 🙂

Sam is right, that was caused by the big rewrite (which resolved other issues, particularly a fundamental architectural one).

A fix is already in the develop branch: https://github.com/MagicMirrorOrg/MagicMirror/pull/4092

Are you familiar enough with Git to test the develop branch?

So that you can start receiving weather data again right away and don’t have to wait until we’ve figured the issue out, I’d suggest you try a different provider.

https://docs.magicmirror.builders/modules/weather.html

@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.

@oskisch Are you still on the develop branch? Are there still errors in the console?

@oskisch said:

Failed to connect to Wayland display: No such file or directory (2)

Try node --run start:x11

@oskisch said:

• SYSTEM: manufacturer: Raspberry Pi Foundation; model: Raspberry Pi 3 Model B Rev 1.2; virtual: false; MM: v2.36.0-develop

Why are you on the develop branch?

A workaround for users still having issues with the calendar. There was a problem with the node-ical package for some events. This has just been fixed with a new node-ical release (v0.26.0).

To use the new version, run this command in the MagicMirror directory:
npm install node-ical@latest.

Note that this will change your package.json and package-lock.json files, which would cause conflicts during the next MagicMirror update. Therefore, also run the following to restore them:
git restore package*.json

You will then have v0.26.0 installed - the package.json file say otherwise, but that doesn’t matter.

Please give some feedback if that helps :-)

@hrt13 said:

[2026-04-02 19:59:16.671] [ERROR] [calendar] Could not expand event “Tax Day”: ical.expandRecurringEvent is not a function

Looks like you didn’t update the dependencies after you pulled the new MM version.

Please run node --run install-mm and check again.

@BKeyport It should be fixed with v1.5.0. Please update and check :-)

@Niggich What do you user for the pages? MMM-Carousel or MMM-pages? Do you use a fork?

I tested the original projects of MMM-Carousel and MMM-pages without any issues.

@Niggich I made a mistake when I recently added translations to the module. I’ve fixed it now. Please update and check :-)

@christian-klein I like it! Don’t forget to add it to the module list: https://github.com/MagicMirrorOrg/MagicMirror/wiki/3rd-party-modules 🙂

@OliWer Nice. Don’t forget to add it to the module list: https://github.com/MagicMirrorOrg/MagicMirror/wiki/3rd-party-modules