Read the statement by Michael Teeuw here.
NOAA v3 using too many requests?
-
I’m just curious (and I may have missed this) but have you changed the
updateInterval: 30 * 60 * 1000,This is designed to constrain the module to 48 calls per day. Also, as a long shot, are you running more than one weather module using the same API key? I do. -
@Mykle1 I have not changed the update interval Is that in the css? I only have the one module running. What seems weird is that it runs fine then all of the sudden spikes.
-
@dazza120 I am running a Pi 3B the Pi doesn’t lock up. Occasionally if I try to do something a bit funky with a gif in the eye candy module it has but as soon as I use a different gif I am ok.
-
@motdog not overclocked? My Pi would still work just ment that it was working overtime doing the weather connection every second.
-
@motdog said in NOAA v3 using too many requests?:
I have not changed the update interval Is that in the css?
It is in the MMM-NOAA3.js file. Please verify the value. It can also be placed in the config entry which would override the module.js value.
Have you gotten a new API key?
Have your deleted you NOAA install and re-installed?
Have you tried NOAA by itself? No other modules running, or at most just the defaults of MM? -
@dazza120 no clue.
-
@Mykle1 I haven’t modified the js file. I did get a new key. One thing I changed at darksky was to limit the number of requests. The default had me at 1000. I lowered it to 750 so I shouldn’t hit the maximum. I’ll give it a few days to monitor. The number of requests stays low most of the time but occasionally spikes up
-
@motdog said in NOAA v3 using too many requests?:
The number of requests stays low most of the time but occasionally spikes up
Well, something is causing the module to fetch the data. I do not believe it’s the module itself based on your answers
-
@Mykle1 what should I look for? I had 475 requests today.
-
Are you absolutely sure that this is your setting in the config entry?
updateInterval: 30 * 60 * 1000,
