• Recent
  • Tags
  • Unsolved
  • Solved
  • MagicMirror² Repository
  • Documentation
  • 3rd-Party-Modules
  • Donate
  • Discord
  • Register
  • Login
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 487.8k 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.
  • B Offline
    braik @Mar
    last edited by Mar 6, 2017, 1:27 PM

    @Mar
    Hi there,
    I had the same problem and the I have realized that node serveronly was not launched.
    The problem is that the command :
    cd ~/MagicMirror was not working, so I have changed it for
    cd /home/pi/MagicMirror
    and that’s it.
    Hope this can help

    1 Reply Last reply Reply Quote 1
    • B Offline
      bmarofsky
      last edited by Mar 12, 2017, 3:03 AM

      OK, so i am trying this again on a Pi Zero W

      I got stuck on Step 4
      so I ran:

      sudo apt-get remove nodered
      sudo apt-get remove nodejs nodejs-legacy
      sudo apt-get remove npm   # if you installed npm
      
      wget http://node-arm.herokuapp.com/node_archive_armhf.deb
      sudo dpkg -i node_archive_armhf.deb
      sudo apt-get install -y build-essential python-dev npm
      

      then again on Step 5 i got a ton of these:

      pi@raspberrypi:~/MagicMirror $ sudo npm install
      npm WARN engine feedme@1.0.0: wanted: {"node":">=0.12"} (current: {"node":"0.10.29","npm":"1.4.21"})
      npm WARN engine grunt-eslint@19.0.0: wanted: {"node":">=4"} (current: {"node":"0.10.29","npm":"1.4.21"})
      npm WARN engine request@2.81.0: wanted: {"node":">= 4"} (current: {"node":"0.10.29","npm":"1.4.21"})
      npm WARN engine eslint@3.17.1: wanted: {"node":">=4"} (current: {"node":"0.10.29","npm":"1.4.21"})
      
      

      Are the updated steps or an Image that can be downloaded?

      H 1 Reply Last reply Apr 15, 2017, 1:53 PM Reply Quote 0
      • H Offline
        Hawking @bmarofsky
        last edited by Hawking Apr 15, 2017, 2:19 PM Apr 15, 2017, 1:53 PM

        @bmarofsky
        I’m also trying to install Magic Mirror on a Pi Zero W.

        I think one reason for the problems might be that as far as I can tell

        sudo wget http://node-arm.herokuapp.com/node_latest_armhf.deb
        sudo dpkg -i node_latest_armhf.deb
        

        got me node v4.2.1 which is quite outdated (the regular installer of MM2 updates nodes if the version of node is below 5.1.0).
        I therefore tried to install a more recent version of node following the commands here
        https://github.com/sdesalas/node-pi-zero
        However, the compilation of Magic Mirror worked neither with node 7.7.1 nor with node 6.9.1.

        Before I go into details, did anybody got Magic Mirror working on Raspberry Pi Zero W?
        Which node version (and npm version) did you use and how you he install it? Which browser did you use (I read that Midori has some problems)?

        1 Reply Last reply Reply Quote 0
        • M Offline
          Mitchfarino Module Developer @ArkantosArk
          last edited by Apr 16, 2017, 2:14 PM

          @ArkantosArk

          This is @SebTota 's link https://mega.nz/#!XlIU3QjI!QSdvAE3yXp1oMsdRGNte6lt4SncgvfozSDU7xhxtbbM

          S 1 Reply Last reply Aug 31, 2017, 12:13 AM Reply Quote 0
          • H Offline
            Hawking
            last edited by Apr 21, 2017, 10:04 PM

            I could fix my issue with the blank screen by simply doing

            cd ~/MagicMirror/vendor
            npm install
            

            Then it seem to work (even with the node v 4.2.1). Nevertheless I will try to update to a more recent version of node, just to avoid other problems that are likely to exist in this old node version.

            1 Reply Last reply Reply Quote 0
            • L Offline
              longod
              last edited by Apr 28, 2017, 2:00 AM

              Hi! I have followed this guide step by step and so precisely, however I am still getting an error when I type in DISPLAY=:0 npm start through SSH. This is the output:

              pi@raspberrypi:~/MagicMirror $ DISPLAY=:0 npm start
              
              > magicmirror@2.1.1 start /home/pi/MagicMirror
              > sh run-start.sh
              
              /home/pi/MagicMirror/node_modules/electron/dist/electron: error while loading shared libraries: libXss.so.1: cannot open shared object file: No such file or directory
              
              npm ERR! Linux 4.4.50+
              npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "start"
              npm ERR! node v4.2.1
              npm ERR! npm  v2.14.7
              npm ERR! file sh
              npm ERR! code ELIFECYCLE
              npm ERR! errno ENOENT
              npm ERR! syscall spawn
              npm ERR! magicmirror@2.1.1 start: `sh run-start.sh`
              npm ERR! spawn ENOENT
              npm ERR!
              npm ERR! Failed at the magicmirror@2.1.1 start script 'sh run-start.sh'.
              npm ERR! This is most likely a problem with the magicmirror package,
              npm ERR! not with npm itself.
              npm ERR! Tell the author that this fails on your system:
              npm ERR!     sh run-start.sh
              npm ERR! You can get their info via:
              npm ERR!     npm owner ls magicmirror
              npm ERR! There is likely additional logging output above.
              
              npm ERR! Please include the following file with any support request:
              npm ERR!     /home/pi/MagicMirror/npm-debug.log
              

              Any help on what to do to solve this would be greatly appreciated!

              H 1 Reply Last reply May 1, 2017, 10:15 PM Reply Quote 0
              • H Offline
                Hawking @longod
                last edited by May 1, 2017, 10:15 PM

                @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 May 27, 2017, 3:47 PM

                  @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 May 27, 2017, 6:07 PM

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

                    R 1 Reply Last reply May 28, 2017, 8:13 PM Reply Quote 0
                    • R Offline
                      RV @dantodd
                      last edited by May 28, 2017, 8:13 PM

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

                      D B 2 Replies Last reply May 29, 2017, 5:01 AM Reply Quote 0
                      • 1
                      • 2
                      • 7
                      • 8
                      • 9
                      • 10
                      • 11
                      • 20
                      • 21
                      • 9 / 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