@sdetweil
Hi Sam,

I’ve been testing the new develop branch of the weather module over the last few days, and I wanted to give you some positive feedback.

My tablet recently developed a life of its own (eigenartiges Eigenleben), causing unpredictable connection drops and browser reloads. This would have normally triggered the 24-hour API limit for OpenMeteo, but your new protection logic completely saved my setup! It’s great to see that the module now prevents “rogue” clients from getting the whole IP banned.

While testing, I had one idea for an improvement:
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.

Anyway, thanks for the amazing work. Everything is running smoothly now!

Best regards,

Florian

@sdetweil

Hi Sam,

I wanted to give you a quick update and, most importantly, say a huge thank you for your incredibly fast and professional help! It’s amazing to see how quickly you identified the defect and even opened an official issue on GitHub.

I’ve been monitoring the develop branch, and the fix is definitely working. The “rapid-fire” request loop is gone. Even with my temporary IP block, the logs show that the system is now handling the situation gracefully without spamming the API anymore:

Apr 21 07:45:29 MagicMirror npm[495]: [2026-04-21 07:45:29.616] [WARN]  [http_fetcher] [weatherprovider.openmeteo] ...
Apr 21 07:45:40 MagicMirror npm[495]: [2026-04-21 07:45:40.581] [LOG]   [weather] Received INIT_WEATHER for instance module_5_weather

The system is stable now, and I’m just waiting for Open-Meteo to lift the rate limit. I’ll provide another final update in a few days to confirm everything is still running smoothly, but for now: Thanks again, Sam! I really appreciate the support you give to this community.

@sdetweil “Thank you, Sam! I’m glad the logs were helpful in identifying the defect. I’ll keep an eye on the GitHub issue and wait for the official fix. Thanks for your great support!”

@sdetweil
"Hi Sam,

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

@sdetweil Hi Sam,

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

Hi everyone,

I’m struggling with the default weather module since the latest update. I’ve already spent some time analyzing the logs and behavior with the help of an AI (Gemini) to pinpoint the cause. Here is what we found:

1. The Issue:
   Most of the time, I just see “Loading…”. The logs show a massive request loop, firing hundreds of requests per minute.
   Key Observation: The weather is often displayed correctly in the morning until early afternoon. After that, it breaks. This strongly suggests that the request loop exhausts the rate limit or triggers an IP ban from Open-Meteo every day.

2. My Environment:

Provider: Open-Meteo (no API key).

Platform: Proxmox LXC Container (Fresh install via helper script).

Network: Pi-hole is running, but Open-Meteo is whitelisted. DNS resolution is fine.

3. Troubleshooting steps taken:

Fresh Install: Completely recreated the LXC container – no change.

Config: Increased updateInterval significantly, but it’s ignored during the loop.

Alternatives: Investigated MMM-OneCallWeather and OWM, but the “Free Plan” doesn’t provide the forecast data I need without a credit card.

It looks like the http_fetcher or the weather node_helper is stuck in a logic loop and ignores the update intervals for Open-Meteo. Any advice on how to fix this?

@sdetweil said in Faulty temperature display?:

@Phantomkommander i think Germany would be +7…

After your advice, I checked the data again and you were right! I have no idea why I put - it there. :D

Thank you for your patience.

@sdetweil I just entered the coordinates, which I found from a website. See image

Hello everyone,
Yesterday I created a container for Magicmirror in Proxmox with Ubuntu 24.04. It’s working relatively well now. The only problem I have with the standard “Weather” module is that it doesn’t show me the “correct” temperature. The problem could be related to the fact that I live in Germany. Where I specified “metric” as “unit”. Can you maybe help me?

Attached is a picture of the temperature. However, we have around 30°C at the moment.

Best regards