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.

    trouble with MMM-GoogleTrafficTimes

    Scheduled Pinned Locked Moved Troubleshooting
    traffic
    39 Posts 3 Posters 8.2k 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.
    • L Offline
      laschalkh @sdetweil
      last edited by

      @sdetweil

      Hi Sam, I tried that key sequence from the console. I’m not getting the interface.

      Thanks,
      Kevin

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

        @laschalkh all at the same time

        Sam

        How to add modules

        learning how to use browser developers window for css changes

        L 1 Reply Last reply Reply Quote 0
        • L Offline
          laschalkh @sdetweil
          last edited by

          @sdetweil

          Hi Sam,

          yea, I understand this would be pulling up the developer interface from the browser. But it’s not coming up. Is there another way to see those errors?

          Thanks,
          Kevin

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

            @laschalkh you can restart MagicMirror by using

            npm start dev

            if you use.pm2, then stop that instance
            pm2 stop all

            Sam

            How to add modules

            learning how to use browser developers window for css changes

            L 1 Reply Last reply Reply Quote 0
            • L Offline
              laschalkh @sdetweil
              last edited by

              @sdetweil

              Hi Sam, when I try to run npm start dev I get an error. Which directory does it expect to be run from? I tried in a few locations and nothing worked.

              Thanks,
              Kevin

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

                @laschalkh always in the MagicMirror folder

                Sam

                How to add modules

                learning how to use browser developers window for css changes

                1 Reply Last reply Reply Quote 0
                • L Offline
                  laschalkh
                  last edited by

                  ok, tried that and got the error:
                  Failed at the magicmirror@2.13.0 start script.

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

                    @laschalkh there has got to be more than 1 line

                    Sam

                    How to add modules

                    learning how to use browser developers window for css changes

                    1 Reply Last reply Reply Quote 0
                    • L Offline
                      laschalkh
                      last edited by

                      ok, found that it created a log file for that process

                      0 info it worked if it ends with ok
                      1 verbose cli [ ‘/usr/local/bin/node’, ‘/usr/local/bin/npm’, ‘start’, ‘dev’ ]
                      2 info using npm@6.9.0
                      3 info using node@v10.16.0
                      4 verbose run-script [ ‘prestart’, ‘start’, ‘poststart’ ]
                      5 info lifecycle magicmirror@2.13.0~prestart: magicmirror@2.13.0
                      6 info lifecycle magicmirror@2.13.0~start: magicmirror@2.13.0
                      7 verbose lifecycle magicmirror@2.13.0~start: unsafe-perm in lifecycle true
                      8 verbose lifecycle magicmirror@2.13.0~start: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/
                      node-gyp-bin:/home/pi/MagicMirror/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bi
                      n:/usr/local/games:/usr/games
                      9 verbose lifecycle magicmirror@2.13.0~start: CWD: /home/pi/MagicMirror
                      10 silly lifecycle magicmirror@2.13.0~start: Args: [ ‘-c’,
                      10 silly lifecycle ‘DISPLAY=“${DISPLAY:=:0}” ./node_modules/.bin/electron js/electron.js “dev”’ ]
                      11 info lifecycle magicmirror@2.13.0~start: Failed to exec start script
                      12 verbose stack Error: magicmirror@2.13.0 start: DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/ele ctron.js "dev"
                      12 verbose stack spawn ENOENT
                      12 verbose stack at ChildProcess. (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/li
                      b/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.13.0
                      14 verbose cwd /home/pi/MagicMirror
                      15 verbose Linux 4.19.97+
                      16 verbose argv “/usr/local/bin/node” “/usr/local/bin/npm” “start” “dev”
                      17 verbose node v10.16.0
                      18 verbose npm v6.9.0
                      19 error file sh
                      20 error code ELIFECYCLE
                      21 error errno ENOENT
                      22 error syscall spawn
                      23 error magicmirror@2.13.0 start: DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js "dev"
                      23 error spawn ENOENT
                      24 error Failed at the magicmirror@2.13.0 start script.
                      24 error This is probably not a problem with npm. There is likely additional logging output above.
                      25 verbose exit [ 1, true ]

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

                        @laschalkh is this a pi 0?

                        Sam

                        How to add modules

                        learning how to use browser developers window for css changes

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