@analogcheep thanks, let me know if yours works and upvote if it is helpful!

@cdh1001 thanks, I will amend my guide over the weekend then.

@cdh1001 please specify tweaks as they might help others.

@big11 I did a test install today, so I’m really not sure what you are doing.

You will notice that the missing dependencies are installed in subsequent steps (e.g. there’s a problem with style lint and acorn. This is then fixed (see where it says + stylelint@9.9.0 and + acorn lower down in your warnings).

This installation is completely different from the MM-Wiki. It does not use sh run-start.sh at all. Therefore there may well be problems.

Can I ask, are you doing your installation over SSH/Telnet? or on the Pi itself? because you keep mentioning ‘locally’ and I just want to make sure I know what you mean by that.

Edit: Also, don’t use npm install in sudo; it should be run as the normal user

@big11 this goes to my forked repo. Are you booting through to the desktop or to the console?

@big11 From what I am reading of your reply, are you booting into command line mode? You should be booting into Desktop AutoLogin from sudo raspi-config | Choose option: Boot Options | Choose option: Desktop / CLI | then Desktop Autologin.

Can you confirm which install script you ran? Did you run the one from ac2799/MagicMirror or ac2799/MagicMirrorPi0Installer?

@12wsx Did you change the default user to be called root? I’m confused as to why your prompt says root@raspberrypi, but the home directory (/home/pi/MagicMirror) is that instead of /home/root/MagicMirror

As I remember, the shell script refers directly to a home drive using the user pi; if you wish to change this on your installation, issue:
EDIT: I just noticed I think you’re running off my installer rather than the forked magic mirror repository that I have been testing more recently. The edits are the same, except instead of being in ~/MagicMirror/installers it’ll be in ~/MagicMirror/PiZero, and the files won’t have Pi0 on the end of their names

sudo nano ~/MagicMirror/installers/startMagicMirror.sh

change the bottom line so instead of pi it is the correct user’s home drive e.g.

sh /home/root/MagicMirror/installers/chromium_startPi0.sh

Also check pm2_MagicMirrorPi0.json and chromium_startPi0.sh in case they also are pointing to the pi user folder.

then do

sudo chmod a+x ~/MagicMirror/installers/startMagicMirrorPi0.sh;
sudo chmod a+x ~/MagicMirror/installers/pm2_MagicMirrorPi0.json;
sudo chmod a+x ~/MagicMirror/installers/chromium_startPi0.sh;

to make all the files executable (just in case they aren’t already)

Now run:

sudo su -c "env PATH=$PATH:/usr/bin pm2 startup systemd -u pi --hp /home/pi"
pm2 start ~/MagicMirror/installers/pm2_MagicMirrorPi0.json
pm2 save

changing the /home/pi to ensure you are in the correct user.
Then restart and let me know what happens.

That’s the only thing that I can think it could be at the moment

@12wsx straight after installation did you restart the pi zero? It should run, it’s quite a slow start up process though… if you run pm2 show MagicMirror what does it say? It takes a good minute to fire up sometimes…

@dazza120 thanks, did you test my script? I was looking at a single installer that would auto detect 2B/3B Or Zero and install the appropriate script, thereby meaning a single repo for all platforms.

It’s able to detect 3B+ and Zero and does full install for 3B+ and server only for Zero, I don’t have a 3B though to make sure it works on that.

@idoodler I didn’t really understand what was the difference between server only and not. This installs magic mirror, runs it as server only and runs three chromium browser on start-up to display it all… functionally I couldn’t tell the difference, but there might be something I’m missing