My question is which file holds the code for the section headings. I figure if I take them out and just have the date and icons, the module will fit perfectly on the small screen, then I can desing the other modules to fit in the space left.

Thanks in Advance

You don’t have to use geolocation at all. I use my latitude and longitude and it fires right up. The module does error in the terminal, but only once. Then it performs as expected with no further errors.

server is located in Paris, France

Well. Stumbled on this just now and same thing for me. But I don’t understand as https://www.abstractapi.com/ip-geolocation-api returns Sweden for me… How is that even possible

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.

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

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)

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…

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

I installed MMM-NOAA V2.0 just now, but the lines necessary in the config.js struck me as being too little.

No ‘position’, etc, just the api’s.
I read that it takes:

language: “en”,
timeFormat: 24,
units: “metric”,

from the config.js, but then still I am missing info like ‘location’, ‘locationID’, etc.
How does it know which city to take ?
What weather information is currently displayed ? England due to “en” ? :-)

In github I read:

“In this new Version you can select up to 3 different weather locations like in this example.”

but I fail to see this.

Could you please provide me with a correct config.js entry for this otherwise good looking module ??

And airvisual.com refuses to give me api (does not send me the confirmation mail), but that not a fault of the module.

Best regards,

Erik-Jan

I wrote him (see my prevoius post) that I am using the latest version of this module (V 2.1.7).

Yes, you did. My bad.

@idoodler thanks for your help, I will try it!

@Mykle1 I know that CBD is currently working on an update for this module and I understand that this is very time consuming. I think I will wait for the new version :)
With regard to CBD question: I wrote him (see my prevoius post) that I am using the latest version of this module (V 2.1.7).

@core said in MMM-NOAA:

Thanks all for your help!

@idoodler I deleted MMM-Fuel from my config.js. Nothing changed, the other modules mentioned before won‘t work…this seems to be a problem with MMM-NOAA „blocking“ other modules.

@cowboysdude I run the latest version, even tried a re-installation. I adjusted the config to the current version, i.e only using apiKey and airKey as shwon in the readme.

Any more ideas…?

Best regards!

I don’t like to speak for someone else but in this case . . .

@cowboysdude is a personal friend of mine. He is currently in the middle of a massive re-write of NOAA, and that’s after he puts in long days at his day job. I’m sure he’ll investigate this issue when he can. In the meantime, which version of NOAA are you running. I see CBD asked you but you didn’t answer him. :-/

Anyway I would like to stick to mmm–noaa for its better visualization and tools.
I appreciate any help and solutions.

Thanks!

@idoodler I deleted MMM-Fuel from my config.js. Nothing changed, the other modules mentioned before won‘t work…this seems to be a problem with MMM-NOAA „blocking“ other modules.

@cowboysdude I run the latest version, even tried a re-installation. I adjusted the config to the current version, i.e only using apiKey and airKey as shwon in the readme.

Any more ideas…?

Check the readme file on github