Looking for Beta-testers!

XxX_Cobra_XxX

@strawberry-3.141 I have installed the dependencies now with ‘npm install’ and it works! ;-)

Thank you very much

roramirez

Hey Guys,

To prevent problems like the error on validation on develop branch I say to you we are working a test suite for MagicMirror.

Now is initial state with some tests. Today @MichMich merged a change with some testing for e2e area. At now isn’t integrated the e2e tests in Travis. You can run e2e tests with

export DISPLAY=:0 && npm run test:e2e
You need run npm install before

The build a test is simple. If someone is animated and want to build one or need some light let me know.

So, also it helps if you run the e2e tests into your system and tells us if something is wrong or good.

morozgrafix

@roramirez I just submitted PR to add chai-as-promised to devDependencies. I was missing it from globally installed packages and ran into an error when tried to run tests.

ESOB

Something on the develop branch turned my magic mirror back to black screen again (It ran fine on develop branch yesterday but when I did my pull&&install today it went down again). Here is the information from the pm2 logs, tell me if you need anything else:

mm-0 (out): Module helper loaded: MMM-NFL
mm-0 (out): Initializing new module helper ...
mm-0 (out): Module helper loaded: newsfeed
mm-0 (out): All module helpers loaded.
mm-0 (out): Starting server op port 8080 ...
mm-0 (out): Server started ...
mm-0 (out): Connecting socket for: MMM-Remote-Control
mm-0 (out): Starting node helper for: MMM-Remote-Control
mm-0 (out): Connecting socket for: calendar
mm-0 (out): Starting node helper for: calendar
mm-0 (out): Connecting socket for: MMM-Traffic
mm-0 (out): MMM-Traffic helper started ...
mm-0 (out): Connecting socket for: MMM-WunderGround
mm-0 (out): MMM-WunderGround helper started ...
mm-0 (out): Connecting socket for: MMM-NFL
mm-0 (out): Starting module: MMM-NFL
mm-0 (out): Connecting socket for: newsfeed
mm-0 (out): Starting module: newsfeed
mm-0 (out): Sockets connected & modules started ...
mm-0 (out): Launching application.

mm-0 (err):     at exports._exceptionWithHostPort (util.js:1049:20)
mm-0 (err):     at Server._listen2 (net.js:1253:14)
mm-0 (err):     at listen (net.js:1289:10)
mm-0 (err):     at net.js:1399:9
mm-0 (err):     at _combinedTickCallback (internal/process/next_tick.js:77:11)
mm-0 (err):     at process._tickCallback (internal/process/next_tick.js:98:9)
mm-0 (err):     at Module.runMain (module.js:592:11)
mm-0 (err):     at run (bootstrap_node.js:402:7)
mm-0 (err):     at startup (bootstrap_node.js:157:9)
mm-0 (err):   code: 'EADDRINUSE',
mm-0 (err):   errno: 'EADDRINUSE',
mm-0 (err):   syscall: 'listen',
mm-0 (err):   address: '::',
mm-0 (err):   port: 8080 }
mm-0 (err): ERROR! Could not find main module js file.

morozgrafix

@ESOB looks like your port 8080 is in use. Do you happen to have another instance of MM running already? Or maybe something else is taking your port 8080.

ESOB

@morozgrafix maybe, I issued a pm2 stop and then did a restart and I am no longer getting that error. I am still getting a black only screen with the only error being:

"ERROR! Could not find main module js file."

What logs should I get you to figure out the reason for lack of display?

Edit:
Scratch that, I double checked the logs and I get the same error. I will do a full pi reboot again to triple check but it seems consistent.
Edit 2:
After triple check, only one MM instance open and same error noted about port 8080.

morozgrafix

@ESOB did you run npm install after pulling development branch? Next step would be to try to start it in node serveronly mode and point your browser at http://:8080 or run npm start Dev and see if you get any errors in console log of the browser or electron app

morozgrafix

@ESOB sorry I was replying before you edited post with update. Try temporarily changing your config.js to another port if 8080 is taken for some reason.

ESOB

@morozgrafix So I tried changing the port number to 8081 and I got this:

mm-0 (err): WARNING! Could not load config file. Starting with default configuration. Error found: RangeError: "port" argument must be >= 0 and < 65536
mm-0 (err): App threw an error during load
mm-0 (err): RangeError: "port" argument must be >= 0 and < 65536
mm-0 (err):     at assertPort (internal/net.js:17:11)
mm-0 (err):     at Server.listen (net.js:1371:7)
mm-0 (err):     at new Server (/home/pi/MagicMirror/js/server.js:20:9)
mm-0 (err):     at /home/pi/MagicMirror/js/app.js:193:18
mm-0 (err):     at loadNextModule (/home/pi/MagicMirror/js/app.js:142:5)
mm-0 (err):     at /home/pi/MagicMirror/js/app.js:137:6
mm-0 (err):     at Class.loaded (/home/pi/MagicMirror/modules/node_modules/node_helper/index.js:19:3)
mm-0 (err):     at loadModule (/home/pi/MagicMirror/js/app.js:118:6)
mm-0 (err):     at loadNextModule (/home/pi/MagicMirror/js/app.js:135:5)
mm-0 (err):     at /home/pi/MagicMirror/js/app.js:137:6
mm-0 (err): ERROR! Could not find main module js file.

I did run npm install, also tried serveronly and running npm start dev but did not gather any additional information. I will say the weird thing is when I leave it on port 8080, the remote control module still loads.

morozgrafix

@ESOB This error WARNING! Could not load config file. seems very odd. Can you please post your config.js file? Also another option is to backup your config.js and do file copy of config.js.sample to config.js to have good known configuration to begin with.

When starting with npm start dev or node serveronly do you see any errors in the Console Log of the dev tools of the electron or your browser?

P.S. I wanted to fork this troubleshooting conversation into a separate thread, but can’t seem to find a way.