MMM-NOAA - Another Weather Module

[justjim1220]

@mykle1 :nauseated_face: :nauseated_face: :nauseated_face:

[cowboysdude]

[Mykle1]

@cowboysdude

There are no bounds to my jealousy right now.

[SoleLo]

@mykle1 I can tell there is a lot of love in that “maniac”, he is just trying to tease us.

[Mykle1]

@solelo

Yes, I am privy to some of his diabolical, maniacal work, but I am sworn to secrecy. Mostly, I am just in awe. :-)

[SoleLo]

@Mykle1 We respect it. I’m waiting to switch over since I can’t get the MyWeather modules to load… :disappointed_face:

[Mykle1]

@solelo said in MMM-NOAA - Another Weather Module:

I’m waiting to switch over

Well, I think the first 2 versions of NOAA are still available

[SoleLo]

@mykle1 I have one commented out, I’m going to turn it on or just wait…

[nobita]

@justjim1220
Work now,it’s my mistake i use old API Key
Thanks again

[redink]

I know you are working on V3, and I am looking forward to it. But, I’ve been having issue with V2. Specifically, it wouldn’t work with MMM-CalendarExt. Meaning I couldn’t have both on screen at the same time.

I looked at the errors, and the issue appears to be with the following lines of code

 	if (this.config.units != "metric") {
	 tt.innerHTML = n Day ~ " + allDay[0].fcttext + "<br />" 
	 	: "Night ~ " + allDay1 + "<br />";
	 	} else {
	 tt.innerHTML = n " + allDay[0].fcttext_metric + "<br />" 
	 	: "" + allDayM1 + "<br />";  
	 	}

The error was something about an uncaught exception from a promise. My JavaScript is very rusty to actually try and fix this on my own, but simply commenting out those lines actually made the error go away, and I was able to get NOAA and CalendarExt on screen at the same time.

Just posting this because I spent the last two days trying to get this resolved, and figured someone else might benefit.