Menu ▾ ▴

#710 5.1.0 – location timeout retry loop exhausts OpenWeatherMap daily quota

General
open
nobody
None
medium
2 days ago
2026-11-09
No

Hi,

Meteorologist 5.1.0 on macOS 27.2 (Apple Silicon), location set to <here>, source OpenWeatherMap (One Call 3.0, free key), update frequency 60 min.

When the Mac stays awake with the display off (Amphetamine, lid closed), location acquisition times out and the app retries every ~5–6 seconds with no backoff. Each retry also triggers a One Call request, so ~630 requests/hour. The free 1,000 calls/day is exhausted in ~1.5 hours and the key is blocked for the rest of the day. The loop stops as soon as the display wakes.

Log excerpt (repeats all night):

[2026-11-06T12:17:13Z] <Warning>: Location acquisition timed out.
[2026-11-06T12:17:13Z] <Warning>: Location unavailable; continuing startup using saved location if available.
[2026-11-06T12:17:14Z] <Error>: OpenWeatherMap: The operation couldn't be completed. (Meteorologist.OpenWeatherError error 0.)
[2026-11-06T12:17:19Z] <Warning>: Location acquisition timed out.
...

On 2026-11-06 alone: ~21,900 log lines, 630 timeouts per hour between 01:42 and 14:18 local time.

I've used the app with the same key for years without hitting the limit. It started around the 5.1.0 update.

Suggestions:

  • On location timeout, use the saved location and wait for the normal update interval instead of retrying immediately (or use exponential backoff).
  • Don't issue a new weather request per location retry.
  • Optionally pause updates while the displays are asleep.

Thanks for the app!

Discussion

  • EdwardD20

    EdwardD20 - 6 days ago

    Any chance you could privately share your PLIST file with me at EdwardD20@mac.com?

    Have you tried 5.1.1? It fixed several timing issues.

    Ed

     
  • EdwardD20

    EdwardD20 - 3 days ago

    @Alexandru - still having problems or has it settled down?

    Ed

     
  • Alexandru Nuta

    Alexandru Nuta - 2 days ago

    Hi Ed, thanks for the reply and for following up. I was still on 5.1.0. I'm updating to 5.1.1 now and will test it.

     

Log in to post a comment.