Hi everyone,

Just to remind you that this still works…

https://github.com/RedNax67/MMM-TrafficCal

https://forum.magicmirror.builders/topic/831/mmm-trafficcal-dynamically-display-commutes-based-on-calendar-entries?_=1590694194999

It’s not a module but a python script which runs on the client…

Hi,

Why not use this: https://github.com/cowboysdude/Pir-Sensor? Works great for me.

@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 :blush:

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…

@ostfilinchen And you’re certain the warning isn’t present in the wunderground payload?

Mine shows three because the payload has three warnings:

	"alerts": [
		{
		"type": "WND",
		"wtype_meteoalarm": "1",
		"wtype_meteoalarm_name": "Wind",
		"level_meteoalarm": "2",
		"level_meteoalarm_name": "Yellow",
		"level_meteoalarm_description": "The weather is potentially dangerous. The weather phenomena that have been forecast are not unusual, but be attentive if you intend to practice activities exposed to meteorological risks. Keep informed about the expected meteorological conditions and do not take any avoidable risk.",
		"description": "Severe gusts of 80-90 km/h.BE AWARE of debris being blown around. Localised outdoor activity disruption is possible due to debris.>",
		"date": "1970-01-01 00:00:00 GMT",
		"date_epoch": "NA",
		"expires": "2017-02-23 23:59:00 GMT",
		"expires_epoch": "NA",
		"message": "Severe gusts of 80-90 km/h.BE AWARE of debris being blown around. Localised outdoor activity disruption is possible due to debris.>)",
		"phenomena": "NA",
		"significance": "NA",
		"attribution": "Information provided by , <a href='http://meteoalarm.eu/'>EUMETNET - MeteoAlarm</a> Note: Time delays between this website and <a href='http://meteoalarm.eu/'>Meteoalarm.eu</a> are possible. For the most up-to-date information about alert levels as published by the participating National Meteorological Services, please visit <a href='http://meteoalarm.eu/'>Meteoalarm</a>. For terms of use of this information, and copyright information, see <a href='http://meteoalarm.eu/'>Meteoalarm</a> Terms of Use."
		}
		,
		{
		"type": "WIN",
		"wtype_meteoalarm": "2",
		"wtype_meteoalarm_name": "Snow/Ice",
		"level_meteoalarm": "2",
		"level_meteoalarm_name": "Yellow",
		"level_meteoalarm_description": "The weather is potentially dangerous. The weather phenomena that have been forecast are not unusual, but be attentive if you intend to practice activities exposed to meteorological risks. Keep informed about the expected meteorological conditions and do not take any avoidable risk.",
		"description": "Potential disruption due to snow and ice from 6AM CET SAT until 8:59AM CET SAT",
		"date": "2017-02-25 06:28:03 GMT",
		"date_epoch": "NA",
		"expires": "2017-02-25 07:59:00 GMT",
		"expires_epoch": "NA",
		"message": "Potential disruption due to snow and ice from 6AM CET SAT until 8:59AM CET SAT)",
		"phenomena": "NA",
		"significance": "NA",
		"attribution": "Information provided by , <a href='http://meteoalarm.eu/'>EUMETNET - MeteoAlarm</a> Note: Time delays between this website and <a href='http://meteoalarm.eu/'>Meteoalarm.eu</a> are possible. For the most up-to-date information about alert levels as published by the participating National Meteorological Services, please visit <a href='http://meteoalarm.eu/'>Meteoalarm</a>. For terms of use of this information, and copyright information, see <a href='http://meteoalarm.eu/'>Meteoalarm</a> Terms of Use."
		}
		,
		{
		"type": "WRN",
		"wtype_meteoalarm": "3",
		"wtype_meteoalarm_name": "Thunderstorms",
		"level_meteoalarm": "2",
		"level_meteoalarm_name": "Yellow",
		"level_meteoalarm_description": "The weather is potentially dangerous. The weather phenomena that have been forecast are not unusual, but be attentive if you intend to practice activities exposed to meteorological risks. Keep informed about the expected meteorological conditions and do not take any avoidable risk.",
		"description": "Potential disruption due to thunderstorms from 4PM CET MON until 9:59PM CET MON",
		"date": "2017-02-27 11:46:02 GMT",
		"date_epoch": "NA",
		"expires": "2017-02-27 20:59:00 GMT",
		"expires_epoch": "NA",
		"message": "Potential disruption due to thunderstorms from 4PM CET MON until 9:59PM CET MON)",
		"phenomena": "NA",
		"significance": "NA",
		"attribution": "Information provided by , <a href='http://meteoalarm.eu/'>EUMETNET - MeteoAlarm</a> Note: Time delays between this website and <a href='http://meteoalarm.eu/'>Meteoalarm.eu</a> are possible. For the most up-to-date information about alert levels as published by the participating National Meteorological Services, please visit <a href='http://meteoalarm.eu/'>Meteoalarm</a>. For terms of use of this information, and copyright information, see <a href='http://meteoalarm.eu/'>Meteoalarm</a> Terms of Use."
		}
	]

@c502 Thanks!

The initial xml doesn’t hold all the info:

This atom/xml feed is an index to active advisories, watches and warnings 
issued by the National Weather Service.  This index file is not the complete 
Common Alerting Protocol (CAP) alert message.  To obtain the complete CAP 
alert, please follow the links for each entry in this index.  Also note the 
CAP message uses a style sheet to convey the information in a human readable 
format.  Please view the source of the CAP message to see the complete data 
set.  Not all information in the CAP message is contained in this index of 
active alerts.

You’ll have to follow the links in the initial xml message to get the full info. You could probably use the newsfeed module as an initial startingpoint…

@ostfilinchen Cannot reproduce your error. We have cloudy conditions here now and everything works fine.
One thing i did notice when using the remote control module is that it places the icon tables in the config.js for some reason. Could you check your config? Maybe you can pm me your config section.maybe it’s some combination of settings…

@johnnyboy Did you try this (a bit further down in the thread)? https://www.raspberrypi.org/forums/viewtopic.php?f=29&t=24679

@ostfilinchen Some obsolete coloricon code got in the way it seems. Are you not using the coloricons?

@ostfilinchen Anything in the logs? Works fine here…

IT could be your chosen weatherstation is feeding ‘estimated’ forecasts. The module skips those as they vary wildly (0 to 15 degrees C)… Should clear up on it’s own in that case.

Update: There was no logging on skipping estimated forecasts. Added it just now.

@RedNax New version has these strings as config items…