@j-e-f-f This looks familiar… well done!

@jamielola Hi!

You’ll also have to change the notifications (GET_WUNDERGROUND (request) and WUNDERGROUND (the reply sent by node_helper). Those notifications go systemwide so when 2 modules send the same one, the first one wins… The trick is to make them unique to the instance.

@BenRoe

Having the same problem with my module… A theoretical solution could be to make node_helper multi instance aware by appending some identifier to the notification unique to the instance: ie GET_WEATHER_001… The helper triggers on GET_WEATHER and builds an array with the different notifications and payloads. It then periodically runs through the array getting the appropriate requests and sending out notifications like WEATHER_001 with the specific payload.

Haven’t built it yet though…

Hi,

Please have a look at this post: https://forum.magicmirror.builders/topic/998/mmm-wunderground-2-locations-gives-duplicate-data-from-the-first-location

@sithlordhood

Hi!

Did your log show errors similar to:

0|mm       | WARNING! Could not validate config file. Please correct syntax errors. Starting with default configuration.

In your post above there are weird (double) quotes that proved problematic when trying your config. This one works fine on my setup:

			module: "MMM-WunderGround",
			position: "top_right",
			header: "",
			config: {
				apikey: "xxxxxxxxxxxxxxxx",
				pws: "pws:IPORTSMO30",
				currentweather: 0,
				coloricon: true,
				hourly: "1",
				fcdaycount: "10",
				hourlyinterval: "2",
				hourlycount: "1",
				animationSpeed: 5000,
				alerttime: 10000,
				alerttruncatestring: "english:",
				roundTmpDecs: 0,
				UseCardinals: 1,
				windunits: "mph",
				sysstat: "0"
			}
		},

Good luck!

OOps… sorry…fixed

Hi,

This is because of offloading scheduling to the node_helper.js. Have a look here: https://github.com/RedNax67/MMM-WunderGround/issues/20

Hi,

Been having a bit of a dilemma… Made something (i think is) rather cool using a technique i haven’t seen in any module here… Spritesheet animation using css. Works great and only consists of a hand full of codelines…

However my module uses a nonpublic api to get a preformatted spritesheet (just stumbled upon it… ), so i can’t really share it i think. I could however share the code without (information) about the api used…

What do we think?

@ostfilinchen There appears to be an issue at weather underground. Just noticed that all but one warnings have expired already. Usually they wouldn’t be present in the api payload when expired. I’ll have to start checking for expiration in the code…

Update: new version now checks alert expiration

@ostfilinchen Could you have at the wunderground payload? It’s present in your logs/console…