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.

    How I got my Magic Mirror working on a Raspberry Pi 0 (zero)

    Scheduled Pinned Locked Moved Tutorials
    raspberry pipi0zeropizeropi1
    204 Posts 47 Posters 558.3k Views 47 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.
    • H Offline
      Hawking @longod
      last edited by

      @longod

      I didn’t try your way of starting the MagicMirror. However, is there a reason that you don’t use the commands in the guide to start the MagicMirror (using the start.sh and startMidori scripts)? There is no DISPLAY=:0 npm start mentioned in this thread.

      1 Reply Last reply Reply Quote 0
      • R Offline
        RV @randombullet
        last edited by

        @randombullet i followed those steps but i got a error it says that he cannot connect with localhost: 8080 webpage?

        1 Reply Last reply Reply Quote 0
        • D Offline
          dantodd
          last edited by

          have you tried just using “npm start” in ssh? That works for me.

          R 1 Reply Last reply Reply Quote 0
          • R Offline
            RV @dantodd
            last edited by

            @dantodd you mean every time i start my rasp on i need to type npm start?

            D B 2 Replies Last reply Reply Quote 0
            • H Offline
              Hawking
              last edited by Hawking

              @RV said in How I got my Magic Mirror working on a Raspberry Pi 0 (zero):

              @dantodd you mean every time i start my rasp on i need to type npm start?

              no, that is definitely not necessary.

              I don’t know the reason for the error message (is there actually a space between localhost: and 8080?). What happens if you run

              cd ~/MagicMirror
              node serveronly &
              

              manually?

              1 Reply Last reply Reply Quote 0
              • D Offline
                dantodd @RV
                last edited by

                @RV said in How I got my Magic Mirror working on a Raspberry Pi 0 (zero):

                @dantodd you mean every time i start my rasp on i need to type npm start?

                Automating the process is fairly simple but let’s get you up and running first. You should also check your permissions in the config.js file. Make sure that your whitelist is properly configured.

                1 Reply Last reply Reply Quote 0
                • B Offline
                  braik @RV
                  last edited by braik

                  @RV Hi, I don’t know if it can help, but I have noticed that the “~” shortcut to go tho the /home/pi folder does not work on the scripts.
                  So when you do the same commands manually everything seems to be OK, but when you run the scripts then you get a bug.
                  The solution, in my case, was to replace all the folder shortcuts (as ~ for home folder) with the complete explicit path inside the scripts.
                  Good luck
                  Braik

                  R 1 Reply Last reply Reply Quote 0
                  • R Offline
                    RV @braik
                    last edited by

                    @braik as i said before i am not that experienced with Python, Linux or what so ever. I think you are right on this one. When i typed cd /home/pi/ i didn’t get a response or anything.

                    I hope you can show me how to replace the folder, like you have told me before.

                    H 1 Reply Last reply Reply Quote 0
                    • H Offline
                      Hawking @RV
                      last edited by

                      @RV said in How I got my Magic Mirror working on a Raspberry Pi 0 (zero):

                      When i typed cd /home/pi/ i didn’t get a response or anything.

                      This sounds strange. Did you type it in the unit terminal? cd is the comand to change directory. Maybe you have already been in the /home/pi/ directory (than the change would have no effect). Could you type pwd (print working directory)
                      and give the result before and after the cd /home/pi/ command and give the results?

                      1 Reply Last reply Reply Quote 0
                      • 1 Offline
                        12wsx
                        last edited by

                        Hello. I installed image of SebTota everything work, but i had to update and after put: "git pull"my MM don,t get up.
                        error

                        0 info it worked if it ends with ok
                        1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'start' ]
                        2 info using npm@2.14.7
                        3 info using node@v4.2.1
                        4 verbose run-script [ 'prestart', 'start', 'poststart' ]
                        5 info prestart magicmirror@2.1.2
                        6 info start magicmirror@2.1.2
                        7 verbose unsafe-perm in lifecycle true
                        8 info magicmirror@2.1.2 Failed to exec start script
                        9 verbose stack Error: magicmirror@2.1.2 start: `sh run-start.sh`
                        9 verbose stack spawn ENOENT
                        9 verbose stack     at ChildProcess. (/usr/local/lib/node_modules/npm/lib/utils/spawn.js:17:16)
                        9 verbose stack     at emitTwo (events.js:87:13)
                        9 verbose stack     at ChildProcess.emit (events.js:172:7)
                        9 verbose stack     at maybeClose (internal/child_process.js:818:16)
                        9 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
                        10 verbose pkgid magicmirror@2.1.2
                        11 verbose cwd /home/pi/MagicMirror
                        12 error Linux 4.4.34+
                        13 error argv "/usr/local/bin/node" "/usr/local/bin/npm" "start"
                        14 error node v4.2.1
                        15 error npm  v2.14.7
                        16 error file sh
                        17 error code ELIFECYCLE
                        18 error errno ENOENT
                        19 error syscall spawn
                        20 error magicmirror@2.1.2 start: `sh run-start.sh`
                        20 error spawn ENOENT
                        21 error Failed at the magicmirror@2.1.2 start script 'sh run-start.sh'.
                        21 error This is most likely a problem with the magicmirror package,
                        21 error not with npm itself.
                        21 error Tell the author that this fails on your system:
                        21 error     sh run-start.sh
                        21 error You can get their info via:
                        21 error     npm owner ls magicmirror
                        21 error There is likely additional logging output above.
                        22 verbose exit [ 1, true ]
                        ```how can i resolved this problem?
                        1 Reply Last reply Reply Quote 0
                        • 1
                        • 2
                        • 8
                        • 9
                        • 10
                        • 11
                        • 12
                        • 20
                        • 21
                        • 10 / 21
                        • 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