MMM-NOAA - Another Weather Module

justjim1220

@cowboysdude

Dude! Cowboys season… :face_with_stuck-out_tongue_closed_eyes:

cowboysdude

@justjim1220

alt text

justjim1220

@cowboysdude

Galm

@cowboysdude : thanks a lot ;) Football first

justjim1220

@vauxdvihl

I made it bigger by changing the font and image values in the css file I use. WHich, I use the CSS4 option.

PILuke

Hello,
has someone tested the NOAA3 module with accuweather provider?
I think something is wrong to identify the city with lan and long.
With this config I don’t see any weather information from the module, only air quality:

		{
			disabled: false,
			module: 'MMM-NOAA3',
		 	position: 'top_right',
		     	config: {
				provider: "accuweather",
				apiKey: "xxxxxxxxxxxx",
				airKey: "yyyyyyyyy",
				css: "NOAA3",                  // THIS MUST CONTAIN A CSS STYLE NAME
				userlat: "45.483219", //MUST HAVE BOTH
				userlon: "9.203567"  //MUST HAVE BOTH
				}
		},

In the aw.js file I find this request:

url =  "http://dataservice.accuweather.com/currentconditions/v1/"+zip+"?apikey="+this.config.apiKey+"&details=true";

I think this request doesn’t pass the correct “location key” (the zip value).
Infact if I manually force a “location key” the “current conditions” start to work:

url =  "http://dataservice.accuweather.com/currentconditions/v1/214046?apikey="+this.config.apiKey+"&language="+config.language+"-it&details=true";

This instead doesn’t work for the forecast, if I force the “location key” the module doesn’t show the “four day forecast”

url: "http://dataservice.accuweather.com/forecasts/v1/daily/5day/214046?apikey="+this.config.apiKey+"&language="+config.language+
"-us&details=true&metric=false",

I found also another problem with the language because in the request is passed the right language but not the right region, it remains “us”, so the module doesn’t show any value :

&language="+config.language+"-us&details=true&metric=false"

Can someone resolve the problem?
I’m not so able with js :-)
Thanks

cowboysdude

@piluke I will look into it. However the one problem AW provider does have is at times when you’re just starting the module you have to reload it to get the 4 day forecast…why, I’m not really sure it’s just how it’s been working.

I’ve made some changes but a few more need to be made here’s an example of the update:

cowboysdude

@piluke the updated aw.js is uploaded to git hub.

Do a git pull and the config has changed to include your zip…
REMEMBER YOU MAY HAVE TO RELOAD IT TO GET THE BOTTOM FORECAST…tis an accuweather issue…

{
			disabled: false,
			module: 'MMM-NOAA3',
		 	position: 'top_right',
		     	config: {
				provider: "accuweather",
				apiKey: "xxxxxxxxxxxx",
				airKey: "yyyyyyyyy",
				css: "NOAA3", 
				userlat: "45.483219",  
				userlon: "9.203567"  
			        zip: "11111" //YOUR ZIPCODE	
                           }
		},

cowboysdude

Still working on openweather api as time permits…it’s a complete train wreck LOL

Something has changed…but I am working to fix it.

PILuke

@cowboysdude many many thanks for your help and your time.
Now the module is working.
I can see current conditions and forecast (without reload the page) but … they are not correct. :-)
I make some test, with my zip code the aw system identify a city in Mexico not in Italy!

I think it’s necessary to identify a single locationKey with aw API.
I found three way:
by lat and lon:
https://developer.accuweather.com/accuweather-locations-api/apis/get/locations/v1/cities/geoposition/search

or by zip code:
https://developer.accuweather.com/accuweather-locations-api/apis/get/locations/v1/postalcodes/search

or by name:
https://developer.accuweather.com/accuweather-locations-api/apis/get/locations/v1/cities/search

but i don’t know how to use it in javascript…

Infact if I put (in config.js) the right locationKey for my city instead zipcode the module work perfectly.