MagicMirror Forum
    • Recent
    • Tags
    • Unsolved
    • Solved
    • MagicMirror² Repository
    • Documentation
    • 3rd-Party-Modules
    • Donate
    • Discord
    • Register
    • Login
    A New Chapter for MagicMirror: The Community Takes the Lead
    Read the statement by Michael Teeuw here.

    Looking for Beta-testers!

    Scheduled Pinned Locked Moved MagicMirror
    56 Posts 17 Posters 59.2k Views 18 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • X Offline
      XxX_Cobra_XxX
      last edited by

      @MichMich I have the same problem as ESOB:

      I am now also on the latest develop and it throws an error and just gives me a black screen:

      WARNING! Could not load config file. Starting with default configuration. Error found: Error: Cannot find module 'rrule-alt'
      App threw an error during load
      Error: Cannot find module 'rrule-alt'
          at Module._resolveFilename (module.js:455:15)
          at Function.Module._resolveFilename (/home/pi/MagicMirror/node_modules/electron/dist/resources/electron.asar/common/reset-search-paths.js:35:12)
          at Function.Module._load (module.js:403:25)
          at Module.require (module.js:483:17)
          at require (internal/module.js:20:19)
          at Object. (/home/pi/MagicMirror/modules/default/calendar/vendor/ical.js/node-ical.js:20:13)
          at Module._compile (module.js:556:32)
          at Object.Module._extensions..js (module.js:565:10)
          at Module.load (module.js:473:32)
          at tryModuleLoad (module.js:432:12)
      { Error: Cannot find module 'rrule-alt'
          at Module._resolveFilename (module.js:455:15)
          at Function.Module._resolveFilename (/home/pi/MagicMirror/node_modules/electron/dist/resources/electron.asar/common/reset-search-paths.js:35:12)
          at Function.Module._load (module.js:403:25)
          at Module.require (module.js:483:17)
          at require (internal/module.js:20:19)
          at Object. (/home/pi/MagicMirror/modules/default/calendar/vendor/ical.js/node-ical.js:20:13)
          at Module._compile (module.js:556:32)
          at Object.Module._extensions..js (module.js:565:10)
          at Module.load (module.js:473:32)
          at tryModuleLoad (module.js:432:12) code: 'MODULE_NOT_FOUND' }
      
      

      When I go back to Master branch it loads normally.

      Please help me

      strawberry 3.141S 1 Reply Last reply Reply Quote 0
      • strawberry 3.141S Offline
        strawberry 3.141 Project Sponsor Module Developer @XxX_Cobra_XxX
        last edited by

        @XxX_Cobra_XxX did you install the dependencies? they have changed for the develop branch

        Please create a github issue if you need help, so I can keep track

        X 1 Reply Last reply Reply Quote 0
        • X Offline
          XxX_Cobra_XxX @strawberry 3.141
          last edited by

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

          Thank you very much

          1 Reply Last reply Reply Quote 0
          • R Offline
            roramirez Core Contributors
            last edited by

            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.

            Easy module development with MagicMirror Module Template

            morozgrafixM 1 Reply Last reply Reply Quote 0
            • morozgrafixM Offline
              morozgrafix Moderator @roramirez
              last edited by

              @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.

              E 1 Reply Last reply Reply Quote 0
              • E Offline
                ESOB @morozgrafix
                last edited by

                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.
                
                
                morozgrafixM 1 Reply Last reply Reply Quote 0
                • morozgrafixM Offline
                  morozgrafix Moderator @ESOB
                  last edited by

                  @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.

                  E 1 Reply Last reply Reply Quote 0
                  • E Offline
                    ESOB @morozgrafix
                    last edited by 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.

                    morozgrafixM 2 Replies Last reply Reply Quote 0
                    • morozgrafixM Offline
                      morozgrafix Moderator @ESOB
                      last edited by

                      @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

                      1 Reply Last reply Reply Quote 0
                      • morozgrafixM Offline
                        morozgrafix Moderator @ESOB
                        last edited by 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.

                        E 1 Reply Last reply Reply Quote 0
                        • 1
                        • 2
                        • 3
                        • 4
                        • 5
                        • 6
                        • 5 / 6
                        • First post
                          Last post
                        Enjoying MagicMirror? Please consider a donation!
                        MagicMirror created by Michael Teeuw.
                        Forum managed by Sam, technical setup by Karsten.
                        This forum is using NodeBB as its core | Contributors
                        Contact | Privacy Policy