MMM-NOAA

[Mykle1]

@evroom

This is from the readme.

{
    disabled: false,
    module: 'MMM-NOAA',
    position: 'top_right',
    config: {
	apiKey: "YOUR API KEY",    // https://www.wunderground.com/weather/api  select the middle plan... 	 
	airKey: "YOUR API KEY",    // IF you want Air Quality Index
	pws: "KNYELMIR13",         // go here to find your pws: https://www.wunderground.com/wundermap		 
}
},

And this is mine

{
            disabled: false,
            module: 'MMM-NOAA',
            position: 'top_left',
            config: {
                apiKey: "MY API KEY", // https://www.wunderground.com/weather/api  select the middle plan... 
                airKey: "MY AIR KEY", // IF you want Air Quality Index
                pws1: "KNYNEWYO103", // go here to find your pws: https://www.wunderground.com/wundermap
                animationSpeed: 0,
        }
        },

[cowboysdude]

@evroom Yes that used to be true…the readme is wrong, sorry. The old weather used to be wunderground and since they quit their free api I had to use a different provider and it works for one location only.

There is no longer a need to use “PWS”…as the new api doesn’t use that. That’s an old wunderground requirement.

At the moment this is all that’s required to make it work…

{
            disabled: false,
            module: 'MMM-NOAA',
            position: 'top_left',
            config: {
            	apiKey: "xxxxxx",
		airKey: "xxxxx"
			}
         },

I am also working to eliminate the airKey in that version…

[evroom]

@cowboysdude
Thanks for answering (@Mykle1 too).
It is working, with just the apiKey in the config, but where does it take the location from?
You say it works for one location only, is that a location I can determine, or is it a location that is hard coded somewhere?
I like the temperatures it is showing, but is the weather I can expect in my location? :-)

[Mykle1]

@evroom

Ok, my bad on my previous answer. My apologies. :-/

At the risk of answering in error again, I will say that the module determines your location (geo-location or some such)

[cowboysdude]

@evroom It automatically gets the latitude and longitude and uses that :)

[evroom]

Okay, I see it uses http://ip-api.com/json to determine latitude and longitude.
It is depending on the proxy server in use.
I am at work now (in Germany) and I see my proxy server is located in Paris, France right now.
Will try it at home to see for which location the weather is presented on my MM.

[evroom]

It appears to use the data from the proxy provider.
In my case the latitude and longitude are 67 kilometres away from my real location.
Also the “city” does not correspond with the “lat” and “lon” when I look them up in Google Maps.
Probably the “city” is from my provider and the “lat” and “lon” from the proxy server of that provider.
Therefore I decided to give MMM-YrThen a try, which looks nice.
Sorry to the persons that put so much efford in MMM-NOAA.

[strawberry 3.141]

there should be the possibility to set the lat and lon yourself, maybe someone is also interested in a weather at a different location. Only if no lat lon was provided you should try to get it via this ip api provider

[bhepler]

I’ve been trying to get this module to work and for the life of me I can’t get it to show up. I’ve gone as minimalist as I can and it’s still not appearing.

Here’s my config:

{
     module: "MMM-NOAA",
     position: "top_right",
     config: {
          apiKey: "debxxxxxx",
          airKey: "Fpyyyyy"
     }
},

Here’s the error that I see in the web browser:

TypeError: "allDay is undefined"
getDomhttp://10.0.0.10:8080/modules/MMM-NOAA//MMM-NOAA.js:344:2
updateDomhttp://10.0.0.10:8080/js/main.js:110:28
updateDomhttp://10.0.0.10:8080/js/main.js:109:10
createDomObjectshttp://10.0.0.10:8080/js/main.js:53:29
createDomObjectshttp://10.0.0.10:8080/js/main.js:24:3
modulesStartedhttp://10.0.0.10:8080/js/main.js:471:4
startModuleshttp://10.0.0.10:8080/js/loader.js:59:3
loadNextModulehttp://10.0.0.10:8080/js/loader.js:40:6
onloadhttp://10.0.0.10:8080/js/loader.js:203:42

And I keep seeing this in the pm2 logs:

0|MagicMir | libGL error: MESA-LOADER: failed to retrieve device information
0|MagicMir | MESA-LOADER: failed to retrieve device information
0|MagicMir | MESA-LOADER: failed to retrieve device information

[Hein-Jan]

@bhepler

As far as I can tell the

libGL error: MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information

Is due to the Open GL driver. I am using the Fake KMS and these are mine errors. I am not using NOAA.