@linuxdxs you can use this simple module MMM-RemoteTemperature and from your termometer you only send an HTTP POST request.
You choose the udate interval and all the MM, with this module, will update their value when you send the HTTP POST.
I hope this help you.

@cowboysdude yes, of course :-)
It’s better to modify the README.md for not to use a zip code but a Locationkey from accuweather in the config file.
Many thanks

@linuxdxs you can use this simple module MMM-RemoteTemperature and from your termometer you only send an HTTP POST request.
You choose the udate interval and all the MM, with this module, will update their value when you send the HTTP POST.
I hope this help you.

@sean
I didn’t know this working mode of MM, thanks for your answer.
It’s right my list has 8 items.
I disable all module except clock and start “dev” mode.
There is only one red error but it’s from this module:

MMM-GoogleShoppingList.js:70 Uncaught TypeError: Cannot read property '1' of null
    at items.forEach.item (MMM-GoogleShoppingList.js:70)
    at Array.forEach (<anonymous>)
    at Class.drawItems (MMM-GoogleShoppingList.js:54)
    at Class.socketNotificationReceived (MMM-GoogleShoppingList.js:46)
    at module.js:246
    at r.<anonymous> (socketclient.js:25)
    at r.emit (index.js:133)
    at r.onevent (socket.js:270)
    at r.MMSocket.self.socket.onevent (socketclient.js:19)
    at r.onpacket (socket.js:228)

After few minutes the same error came again…

Hi, nice module, for my wife :-)
Has someone tested it?
I see the module “Loading” but I don’t see the shopping list.
In console I receive this message:

[GSL] Landed on the target page. Trying to get list
[GSL] Tried. (when even failed) : 8

Some suggest?
Many thanks

@cowboysdude yes, of course :-)
It’s better to modify the README.md for not to use a zip code but a Locationkey from accuweather in the config file.
Many thanks

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

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