MMM-NOAA

core

Hi everyone,

I have problems with regard to the latest version of this module.

I updated to the new version, including the updated weather service provider and since then, two of my other modules (MMM-Fuel and MMM-Sonos) are not working any more. The position (bottom_left) is just blank now, wheras the MMM-NOAA (position: top_right) module works. Even a re-install of MMM-NOAA and reboot of my Rpi3 did not fix this issue.
When I delete the module from my config, all other modules are working again, so I can clearly assign the problem to the MMM-NOAA module.
Until now, I don´ t use this module and all modules are working smoothly. However, I like this module so hopefully, the problems will be fixed soon. Any news about it?

Thanks!

idoodler

@core Please provide any log. Execute pm2 log MagicMirror (if you are using pm2), reproduce the issue and post the log here.

When posting the log it is recommended to add it in a code block for better readability.

:clinking_beer_mugs:

cowboysdude

@core run your mirror like this ‘npm start dev’ and tell me what errors you are getting.

Apparently there is a conflict on your mirror so lets see what it is and fix it :)

@idoodler Thanks for the help!!! :) I’m so busy this time of year I’m not on here much.

I’d like a copy of the Italian language file if someone wants to do a pull request on github and upload it that would be great! Thank you

WayneRigley

@cowboysdude Glad to say i have the NOAA Installed and working perfect will say better than any other weather module ive installed as the temps are perfect. my ONLY issue is the module does not seem to be auto-sizing to its position. as you can see its overlaying on top of the bottom bar… anyone have any thoughts or what i should start to attack first . ! Picture would not load so here is a link https://photos.app.goo.gl/VNkNaXwfMWWxyemN7

core

hi,

thanks for the help. I ran npm start dev and here is the log:

0 info it worked if it ends with ok
1 verbose cli [ ‘/usr/bin/node’, ‘/usr/bin/npm’, ‘start’, ‘dev’ ]
2 info using npm@3.10.10
3 info using node@v6.12.3
4 verbose config Skipping project config: /home/pi/.npmrc. (matches userconfig)
5 verbose stack Error: ENOENT: no such file or directory, open ‘/home/pi/package.json’
5 verbose stack at Error (native)
6 verbose cwd /home/pi
7 error Linux 4.9.53-v7+
8 error argv “/usr/bin/node” “/usr/bin/npm” “start” “dev”
9 error node v6.12.3
10 error npm v3.10.10
11 error path /home/pi/package.json
12 error code ENOENT
13 error errno -2
14 error syscall open
15 error enoent ENOENT: no such file or directory, open ‘/home/pi/package.json’
16 error enoent ENOENT: no such file or directory, open ‘/home/pi/package.json’
16 error enoent This is most likely not a problem with npm itself
16 error enoent and is related to npm not being able to find a file.
17 verbose exit [ -2, true ]

anz ideas?

idoodler

@core Did you just execute npm start dev in your Raspberry Pi’s home directory?

Follow the steps to successfully execute the command:

Stop any instance of MagicMirror (pm2 stop MagicMirror if you use pm2)
cd MagicMirror -> You need to go into the MagicMirror directory
Start MagicMirror with Dev Tools
- If you are connected via SSH: DISPLAY=:0 nohup npm start dev &
- If you are directly on your Raspberry Pi: npm start dev

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!