Read the statement by Michael Teeuw here.
NOAA v3 using too many requests?
-
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.
-
@Mykle1 yeah its crazy. I don’t lock up often and I don’t know if it is a correlation. I may just try a different weather module to see if thats the solution
-
@motdog said in NOAA v3 using too many requests?:
I may just try a different weather module to see if thats the solution
Try one what uses the darksky api key that you have. If the same thing happens then the key is the problem. Keep me posted.
-
@Mykle1 will do. I have tried a different key. Weird thing is that the first few days has a small amount of requests then it spikes