Read the statement by Michael Teeuw here.
NOAA v3 using too many requests?
-
@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,
-
Post your NOAA config entry in a code block please. It should look like this.
{ disabled: false, module: 'MMM-NOAA3', position: 'top_right', config: { provider: "darksky", apiKey: "YOUR API KEY", airKey: "YOUR AIR KEY", // IF you want Air Quality Index css: "NOAA4", userlat: "40.123456", userlon: "-74.123456", updateInterval: 30 * 60 * 1000, // VERY IMPORTANT! } },
-
@Mykle1 from the NOAA3.js
Module.register("MMM-NOAA3", { defaults: { animationSpeed: 0, initialLoadDelay: 8000, rotateInterval: 60 * 1000, updateInterval: 30 * 60 * 1000, apiKey: "", airKey: "", pws: "", css: "", frow: true, nupdate: false, userlat: "", userlon: "",
-
@Mykle1 from my main config
{ module: 'MMM-NOAA3', position: 'bottom_left', config: { provider: "darksky", apiKey: "xxxx", airKey: "xxxx", css: "NOAA4", userlat: "38.751389", userlon: "-90.565948" }
-
@dazza120 interesting, Im now up to 600 requests and it locked up.
-
Yikes! I’m out of ideas other than to see if this behavior exists when NOAA3 is the only module running. I’m not suggesting that you re-install MM but that is what I would do. Good luck.