MMM-NOAA

[core]

Hi,

first, thanks again for helping!
here is the log after executing npm start dev in cd MagicMirror

Starting MagicMirror: v2.1.3
Loading config …
Loading module helpers …
No helper found for module: alert.
Initializing new module helper …
Module helper loaded: updatenotification
No helper found for module: clock.
No helper found for module: calendar_monthly.
Initializing new module helper …
Module helper loaded: MMM-temp-ds18b20
Initializing new module helper …
Module helper loaded: MMM-NOAA
Initializing new module helper …
Module helper loaded: MMM-Sonos
Initializing new module helper …
Module helper loaded: MMM-Fuel
Initializing new module helper …
Module helper loaded: MMM-SystemStats
Initializing new module helper …
Module helper loaded: newsfeed
All module helpers loaded.
Starting server on port 8080 …
Server started …
Connecting socket for: updatenotification
Connecting socket for: MMM-temp-ds18b20
Connecting socket for: MMM-NOAA
Starting module: MMM-NOAA
Connecting socket for: MMM-Sonos
Sonos helper started …
Connecting socket for: MMM-Fuel
Starting module helper: MMM-Fuel
Connecting socket for: MMM-SystemStats
Connecting socket for: newsfeed
Starting module: newsfeed
Sockets connected & modules started …
Launching application.
SONOS_UPDATE
Create new news fetcher for url: http://rss.kicker.de/news/aktuell - Interval: 300000
Create new news fetcher for url: http://www.n-tv.de/rss - Interval: 300000
SONOS_UPDATE

And here is my config file for MMM-NOAA:

	{
		disabled: false,
		module: 'MMM-NOAA',
			position: 'top_right',
			config: 
			{
			apiKey: "xxx",    
			useAir: true,             
			airKey: "xxx",    
			pws: "ISCHIFFE4",         
			showClock: false,           
			dformat: false,            
			format: "24",             
			ampm: true,               
			showGreet: false,          
			name: "",                  // Your name
			showWind: true,
			showDate: false,
			showForecast: true,         //show bottom 3 day forecast
			flash: true                 //Today in forecast flashes halo
		}
	},

With this config of the Module, the following modules are shown on screen and running:

MMM-NOAA
Calendar_monthly
MMM-temp-ds
clock

When I delete MMM-NOAA from the config, the following modules are shown on screen and running:

Calendar_monthly
clock
MMM-temp-ds
newsfeed
MMM-Fuel
MMM-Sonos
MMM-SystemStats

Thanks again for help!!

[core]

ok in addition I ran pm2 logs mm with regard to the issue.
Here is the log:

pi@magicpi:~ $ pm2 logs mm
[TAILING] Tailing last 15 lines for [mm] process (change the value with --lines option)
/home/pi/.pm2/logs/mm-error-0.log last 15 lines:
0|mm | at ClientRequest.emit (events.js:191:7)
0|mm | at Socket.socketErrorListener (_http_client.js:358:9)
0|mm | at emitOne (events.js:96:13)
0|mm | TypeError: Cannot read property ‘statusCode’ of undefined
0|mm | at Request.request [as _callback] (/home/pi/MagicMirror/modules/MMM-Fuel/apis/tankerkoenig.js:115:29)
0|mm | at self.callback (/home/pi/MagicMirror/modules/MMM-Fuel/node_modules/request/request.js:186:22)
0|mm | at emitOne (events.js:96:13)
0|mm | at Request.emit (events.js:191:7)
0|mm | at Request.onRequestError (/home/pi/MagicMirror/modules/MMM-Fuel/node_modules/request/request.js:878:8)
0|mm | at emitOne (events.js:96:13)
0|mm | at ClientRequest.emit (events.js:191:7)
0|mm | at TLSSocket.socketErrorListener (_http_client.js:358:9)
0|mm | at emitOne (events.js:96:13)
0|mm | at TLSSocket.emit (events.js:191:7)
0|mm | Failure: null

/home/pi/.pm2/logs/mm-out-0.log last 15 lines:
0|mm | Sonos helper started …
0|mm | Connecting socket for: MMM-Fuel
0|mm | Starting module helper: MMM-Fuel
0|mm | Connecting socket for: MMM-SystemStats
0|mm | Connecting socket for: newsfeed
0|mm | Starting module: newsfeed
0|mm | Sockets connected & modules started …
0|mm | Launching application.
0|mm | SONOS_UPDATE
0|mm | Create new news fetcher for url: http://rss.kicker.de/news/aktuell - Interval: 300000
0|mm | Create new news fetcher for url: http://www.n-tv.de/rss - Interval: 300000
0|mm |
0|mm | > magicmirror@2.1.3 start /home/pi/MagicMirror
0|mm | > sh run-start.sh
0|mm |

[idoodler]

This post is deleted!

[idoodler]

@core Can you remove MMM-Fule from your `config.json. There is an unhandled error with this module.

[core]

Hi

thanks, I will try it.

Just for my understanding: I should delete the MMM-Fuel module from my config.js (or is config.json another file)?
Sorry I m noob.

Thank you very much!

[idoodler]

@core Sorry, its the config.js file.

[cowboysdude]

@waynerigley Thank you!

What you can do is not show the top scrolling forecast and that should lift up the module above the bottom line…

I made this to work on a 32" mirror so it’s kinda big I know :)

There’s also NOAA1 that is much shorter but doesn’t look like NOAA2…

[cowboysdude]

@core What version of NOAA are you running? If you’re using NOAA2 85% of that config isn’t even used …

Check the readme file on github

[core]

Thanks all for your help!

@idoodler I deleted MMM-Fuel from my config.js. Nothing changed, the other modules mentioned before won‘t work…this seems to be a problem with MMM-NOAA „blocking“ other modules.

@cowboysdude I run the latest version, even tried a re-installation. I adjusted the config to the current version, i.e only using apiKey and airKey as shwon in the readme.

Any more ideas…?

[core]

Ok i tried another weather module instead of mmm–noaa.
Everything is on screen and works perfectly.
So (in my case) mmm–noaa causes the problems.

Anyway I would like to stick to mmm–noaa for its better visualization and tools.
I appreciate any help and solutions.

Thanks!

[idoodler]

@core You can open the MagicMirror Interface in Chrome on your desktop, open the Development Tools („F12“ on Windows) head over to „Console“ and check for anything red.

[Mykle1]

@core

I don’t like to speak for someone else but in this case . . .

@cowboysdude is a personal friend of mine. He is currently in the middle of a massive re-write of NOAA, and that’s after he puts in long days at his day job. I’m sure he’ll investigate this issue when he can. In the meantime, which version of NOAA are you running. I see CBD asked you but you didn’t answer him. :-/

[WayneRigley]

@mykle1 im hanging on the side till the new release… thanks for the heads up

[core]

Hi,

@idoodler thanks for your help, I will try it!

@Mykle1 I know that CBD is currently working on an update for this module and I understand that this is very time consuming. I think I will wait for the new version :)
With regard to CBD question: I wrote him (see my prevoius post) that I am using the latest version of this module (V 2.1.7).

@core said in MMM-NOAA:

Thanks all for your help!

@idoodler I deleted MMM-Fuel from my config.js. Nothing changed, the other modules mentioned before won‘t work…this seems to be a problem with MMM-NOAA „blocking“ other modules.

@cowboysdude I run the latest version, even tried a re-installation. I adjusted the config to the current version, i.e only using apiKey and airKey as shwon in the readme.

Any more ideas…?

Best regards!

[Mykle1]

@core said in MMM-NOAA:

I wrote him (see my prevoius post) that I am using the latest version of this module (V 2.1.7).

Yes, you did. My bad.

[ganther]

Same behavior with my mirror.
After latest MMM-NOAA update my MMM-CalendarExt doesn‘t work anymore. No errors in logs.
I was forced to deactivate NOAA. :(

[evroom]

Hi,

I installed MMM-NOAA V2.0 just now, but the lines necessary in the config.js struck me as being too little.

No ‘position’, etc, just the api’s.
I read that it takes:

language: “en”,
timeFormat: 24,
units: “metric”,

from the config.js, but then still I am missing info like ‘location’, ‘locationID’, etc.
How does it know which city to take ?
What weather information is currently displayed ? England due to “en” ? :-)

In github I read:

“In this new Version you can select up to 3 different weather locations like in this example.”

but I fail to see this.

Could you please provide me with a correct config.js entry for this otherwise good looking module ??

And airvisual.com refuses to give me api (does not send me the confirmation mail), but that not a fault of the module.

Best regards,

Erik-Jan

[Mykle1]

@evroom

This is from the readme.

{
    disabled: false,
    module: 'MMM-NOAA',
    position: 'top_right',
    config: {
	apiKey: "YOUR API KEY",    // https://www.wunderground.com/weather/api  select the middle plan... 	 
	airKey: "YOUR API KEY",    // IF you want Air Quality Index
	pws: "KNYELMIR13",         // go here to find your pws: https://www.wunderground.com/wundermap		 
}
},

And this is mine

{
            disabled: false,
            module: 'MMM-NOAA',
            position: 'top_left',
            config: {
                apiKey: "MY API KEY", // https://www.wunderground.com/weather/api  select the middle plan... 
                airKey: "MY AIR KEY", // IF you want Air Quality Index
                pws1: "KNYNEWYO103", // go here to find your pws: https://www.wunderground.com/wundermap
                animationSpeed: 0,
        }
        },

[cowboysdude]

@evroom Yes that used to be true…the readme is wrong, sorry. The old weather used to be wunderground and since they quit their free api I had to use a different provider and it works for one location only.

There is no longer a need to use “PWS”…as the new api doesn’t use that. That’s an old wunderground requirement.

At the moment this is all that’s required to make it work…

{
            disabled: false,
            module: 'MMM-NOAA',
            position: 'top_left',
            config: {
            	apiKey: "xxxxxx",
		airKey: "xxxxx"
			}
         },

I am also working to eliminate the airKey in that version…

[evroom]

@cowboysdude
Thanks for answering (@Mykle1 too).
It is working, with just the apiKey in the config, but where does it take the location from?
You say it works for one location only, is that a location I can determine, or is it a location that is hard coded somewhere?
I like the temperatures it is showing, but is the weather I can expect in my location? :-)