Problems with weather modules on new install

erik72

I have tried several times installing and it all goes fine.
No errors during updates or install.
MM starts fine and most works, but weather and forecast is not there.
I have followed the complete install guide.
I’m running default config.js, no changes

Any ideas would be nice, thanks

Anhalter42

@erik72 you need an openweather.org API key, see documentation of for example currentweather-Module:

appid
The OpenWeatherMap API key, which can be obtained by creating an OpenWeatherMap account.
This value is REQUIRED

erik72

Thanks that worked, but every other time i change something i change something in config.js. I get the following error during startup

Whoops! There was an uncaught exception…
{ Error: listen EADDRINUSE ::: 8080
at Object.exports._errnoException (util.js:1022:11)
at exports._exceptionWithHostPort (util.js:1045:20)
at Server._listen2 (net.js:1262:14)
at listen (net.js:1298:10)
at Server.listen (net.js:1376:9)
at new Server (/home/pi/MagicMirror/js/server.js:27:9)
at /home/pi/MagicMirror/js/app.js:219:18
at loadNextModule (/home/pi/MagicMirror/js/app.js:168:5)
at /home/pi/MagicMirror/js/app.js:163:6
at Class.loaded (/home/pi/MagicMirror/modules/node_modules/node_helper/index.js:19:3)
code: ‘EADDRINUSE’,
errno: ‘EADDRINUSE’,
syscall: ‘listen’,
address: ‘::’,
port: 8080 }

first time it was the default config.js where i changed this line:
ipWhitelist: [], // Set [] to allow all IP addresses.

then i can copy config.js.sample to config,js and it works again

i edit in nano

Mykle1

@erik72

Paste your config.js file here. Remove your API keys first and precede the paste with three back ticks.

erik72

@Mykle1
Got it working somehow thanks for taking the time

Mykle1

@erik72 said in Problems with weather modules on new install:

Got it working somehow thanks for taking the time

Even better. Enjoy your mirror.

bhepler

@erik72 said in Problems with weather modules on new install:

EADDRINUSE

This usually means that you already have the mirror process running and attempted to start it again.

erik72

@bhepler
Perhaps I am starting/stopping in a wrong way.
Because often when I have made a config change it will fail, but work after a reboot.
I use npm start and Ctrl-Z in terminal to quit.

bhepler

@erik72 If you’re working directly on the pi, you can use ctrl+q to stop the interface and return to the terminal. If you’re using SSH to remote into the pi, then ctrl+c should stop it right nicely.

You can always check to see if the mirror is running by typing ps ax | grep node. If you get anything in response more than 6957 pts/19 S+ 0:00 grep --color=auto node (where 6975 will be some random number) then the MM process is running and you’ll need to shut it down in order for it to process your changes.

erik72

@bhepler
Thanks, will give it a try.
This is a really friendly forum