NOAA v3 using too many requests?

[dazza120]

@motdog not overclocked? My Pi would still work just ment that it was working overtime doing the weather connection every second.

[Mykle1]

@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?

[motdog]

@dazza120 no clue.

[motdog]

@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

[Mykle1]

@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

[motdog]

@Mykle1 what should I look for? I had 475 requests today.

[Mykle1]

@motdog

Are you absolutely sure that this is your setting in the config entry?

updateInterval: 30 * 60 * 1000,

[Mykle1]

@motdog

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!
          }
      },

[motdog]

@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: "",

[motdog]

@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" 
	 }

[motdog]

@dazza120 interesting, Im now up to 600 requests and it locked up.

[Mykle1]

@motdog

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.

[motdog]

@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

[Mykle1]

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

[motdog]

@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