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.

    Losing display output after 5 minutes

    Scheduled Pinned Locked Moved Unsolved Troubleshooting
    14 Posts 3 Posters 3.3k Views 3 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.
    • S Offline
      sdetweil @danjvd
      last edited by

      @danjvd weird.

      so next I would disable one module at a time.
      (not the defaults)

      add

      disabled:true,
      

      after the module: line

      Sam

      How to add modules

      learning how to use browser developers window for css changes

      D 1 Reply Last reply Reply Quote 0
      • D Offline
        danjvd @sdetweil
        last edited by

        @sdetweil

        Before I was able to start disabling modules, MM would not start this morning. There are the logs that I got from pm2:

        0 info it worked if it ends with ok
        1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'start' ]
        2 info using npm@6.14.12
        3 info using node@v10.24.1
        4 verbose run-script [ 'prestart', 'start', 'poststart' ]
        5 info lifecycle magicmirror@2.17.1~prestart: magicmirror@2.17.1
        6 info lifecycle magicmirror@2.17.1~start: magicmirror@2.17.1
        7 verbose lifecycle magicmirror@2.17.1~start: unsafe-perm in lifecycle true
        8 verbose lifecycle magicmirror@2.17.1~start: PATH: /usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/pi/MagicMirror/node_modules/.bin:/usr/bin:/bin
        9 verbose lifecycle magicmirror@2.17.1~start: CWD: /home/pi/MagicMirror
        10 silly lifecycle magicmirror@2.17.1~start: Args: [ '-c',
        10 silly lifecycle   'DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js' ]
        11 info lifecycle magicmirror@2.17.1~start: Failed to exec start script
        12 verbose stack Error: magicmirror@2.17.1 start: `DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js`
        12 verbose stack spawn ENOENT
        12 verbose stack     at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:48:18)
        12 verbose stack     at ChildProcess.emit (events.js:198:13)
        12 verbose stack     at maybeClose (internal/child_process.js:982:16)
        12 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
        13 verbose pkgid magicmirror@2.17.1
        14 verbose cwd /home/pi/MagicMirror
        15 verbose Linux 5.10.63-v7l+
        16 verbose argv "/usr/bin/node" "/usr/bin/npm" "start"
        17 verbose node v10.24.1
        18 verbose npm  v6.14.12
        19 error code ELIFECYCLE
        20 error syscall spawn
        21 error file sh
        22 error errno ENOENT
        23 error magicmirror@2.17.1 start: `DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js`
        23 error spawn ENOENT
        24 error Failed at the magicmirror@2.17.1 start script.
        24 error This is probably not a problem with npm. There is likely additional logging output above.
        25 verbose exit [ 1, true ]
        
        D 1 Reply Last reply Reply Quote 0
        • D Offline
          danjvd @danjvd
          last edited by danjvd

          @sdetweil

          Give you a little update after finding the error above. I have reinstalled dependency and built electron.

          cd ~/MagicMirror
          npm install
          cd ~/MagicMirror/node_modules/electron/
          node install.js
          

          The reinstall came with the following warnings

          npm WARN tsutils@3.21.0 requires a peer of typescript@>=2.8.0 || >= 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >= 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta but none is installed. You must install peer dependencies yourself.
          npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/fsevents):
          npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
          

          I restarted MM with npm start, now getting the following:

          [24.11.2021 17:34.23.187] [ERROR] WARNING! Could not load config file. Starting with default configuration. Error found: Error: Cannot find module 'valid-url'
          Require stack:
          - /home/pi/MagicMirror/modules/MMM-CalendarExt2/node_helper.js
          - /home/pi/MagicMirror/js/app.js
          - /home/pi/MagicMirror/js/electron.js
          - /home/pi/MagicMirror/node_modules/electron/dist/resources/default_app.asar/main.js
          

          I disable that mode and was able to get MM restarted. I’m guessing there is an issue with MMM-CalendarExt2.

          S 1 Reply Last reply Reply Quote 0
          • S Offline
            sdetweil @danjvd
            last edited by sdetweil

            @danjvd valid-url see
            https://forum.magicmirror.builders/topic/15778/fix-for-black-screen-in-2-16-and-later

            Sam

            How to add modules

            learning how to use browser developers window for css changes

            1 Reply Last reply Reply Quote 0
            • 1
            • 2
            • 2 / 2
            • 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