so you could try that first…

see this topic on how to get the develop branch
https://forum.magicmirror.builders/topic/14327/testing-new-fixes-or-solving-current-problems-with-next-release-code

see next message first

https://github.com/MagicMirrorOrg/MagicMirror/pull/4110

to get this on your system , do

cd ~/MagicMirror
git fetch origin pull/4110/head:_fix_weather
git switch _fix_weather

restart mm.

I opened an issue in the MagicMirror GitHub repo so we can make sure it’s tracked and fixed

See https://github.com/MagicMirrorOrg/MagicMirror/issues/4109

for comparison, here are the current logs while the system is working correctly. As you can see, the weather provider initializes and then stays quiet for several minutes:

Apr 18 14:56:53 MagicMirror npm[230]: [2026-04-18 14:56:53.051] [LOG]   [weather] Attempting to initialize provider openmeteo...
Apr 18 14:56:53 MagicMirror npm[230]: [2026-04-18 14:56:53.317] [LOG]   [weather] Weather provider openmeteo initialized...
Apr 18 15:06:53 MagicMirror npm[230]: [2026-04-18 15:06:53.184] [LOG]   [weather] Attempting to initialize provider openmeteo...

And here again is the ‘Loop’ state from earlier today (for direct comparison):

[18.04.2026 10:15:22.453] [INFO]  [http_fetcher] [weatherprovider.openmeteo] Fetching url: https://api.open-meteo.com/v1/forecast?latitude=50.4667&longitude=7.6333...
[18.04.2026 10:15:22.510] [INFO]  [http_fetcher] [weatherprovider.openmeteo] Fetching url: https://api.open-meteo.com/v1/forecast?latitude=50.4667&longitude=7.6333...
[18.04.2026 10:15:22.622] [INFO]  [http_fetcher] [weatherprovider.openmeteo] Fetching url: https://api.open-meteo.com/v1/forecast?latitude=50.4667&longitude=7.6333...

The difference is clear: When it fails, it ignores the timing logic entirely. It seems that once a specific error occurs (maybe a temporary timeout from Open-Meteo), the http_fetcher enters a state where it retries instantly without any back-off delay."

here is my current configuration for the weather modules. I am using the default weather module with Open-Meteo.

{
                        module: "weather",
                        position: "top_right",
                        config: {
                                weatherProvider: "openmeteo",
                                type: "current",
                                tempUnits: "metric",
                                lat: 50.4667,
                                lon: 7.6333,
                                useKmh: true, 
                                updateInterval: 20 * 60 * 1000,
                        }
                },
                {
                        module: "weather",
                        position: "top_right",
                        header: "Wetter Vorhersage",
                        config: {
                                weatherProvider: "openmeteo",
                                type: "forecast",
                                lat: 50.4667,
                                lon: 7.6333,
                                useKmh: true, 
                                updateInterval: 20 * 60 * 1000,
                        }
                },

An interesting update: Right now, the weather data is actually being displayed correctly again. However, based on my observations over the last few days, it usually works in the morning and early afternoon, and then fails (stuck on ‘Loading’) for the rest of the day.

This supports the theory that the request loop I see in the logs (journalctl) eventually triggers a rate limit or a temporary IP ban from Open-Meteo. The config seems to work fundamentally, but the fetching behavior is out of control."