NOAA v3 using too many requests?

motdog

I’m not sharing a key as far as I know. My usage just skyrocketed which was surprising. I switched from dark sky to another provider & all is well. Tomorrow I’ll get a new key from darksky and see what happens. Just seemed weird to me

Mykle1

@motdog

Yeah, that’s a good idea. Let us know the result with the new key.

motdog

So the weather with weather underground hasn’t updated since yesterday. I looked at my stats and they were super high for yesterday. Seems the same as what happened before. Weird that random days trigger high requests.

Any thoughts? I’m going to switch back to darksky api to see what happens.

sdetweil

@motdog weather underground has been shutting down keys for over a year now. No new free keys are available. Time to switch to another weather solution.

motdog

@sdetweil Thanks for the heads up. Still curious about the spike in requests. Had that with darksky too which is why I switched to weather underground.

dazza120

@motdog I had the same! Have you got a raspberry Pi? And is it locking up? I had this on mine it just kept dailing every second it was mad! Took off my Overclock that I had on the Pi and it’s working V well at the mo.

Mykle1

@motdog

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.

motdog

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

motdog

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

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.