Read the statement by Michael Teeuw here.
MagicMirror on Pi Zero W
-
I now did a installation on a fresh image and used node version 6.6.1 which automatically includes npm 3.10.8. So instead of
sudo wget http://node-arm.herokuapp.com/node_latest_armhf.deb sudo dpkg -i node_latest_armhf.deb sudo apt-get install npm
I did
wget -O - https://raw.githubusercontent.com/sdesalas/node-pi-zero/master/install-node-v6.9.1.sh | bash
Then I got later on no warnings about to old or insecure version any more but just
npm WARN prefer global coffee-script@1.10.0 should be installed with -g npm WARN prefer global jsonlint@1.6.2 should be installed with -g npm WARN prefer global colorguard@1.2.0 should be installed with -g > electron-chromedriver@1.6.0 install /home/hawking/MagicMirror/node_modules/electron-chromedriver > node ./download-chromedriver.js > electron@1.6.5 postinstall /home/hawking/MagicMirror/node_modules/electron > node install.js npm WARN lifecycle magicmirror@2.1.1~install: cannot run in wd %s %s (wd=%s) magicmirror@2.1.1 cd vendor && npm install /home/hawking/MagicMirror npm WARN lifecycle magicmirror@2.1.1~postinstall: cannot run in wd %s %s (wd=%s) magicmirror@2.1.1 sh installers/postinstall/postinstall.sh /home/hawking/MagicMirror
(in this installation I did not use the pi user, but I had the same problem when I used the default pi user).
If one knows the solution for the blank screen it is obvious that this is a strong hint that one should run
cd ~/MagicMirror/vendor/ && npm install cd ~/MagicMirror/ && sh installers/postinstall/postinstall.sh
(the later at the moment just prints a success message and is therefore not really needed)
I don’t know why these commands did not work automatically, maybe an issue with some directories that are not set (I assume in the error instead of %s the directory should be displayed). -
I installed the image from https://forum.magicmirror.builders/topic/1183/how-i-got-my-magic-mirror-working-on-a-raspberry-pi-0-zero/84 , updated the System to use the onboard wifi and this works for me.
-
@Hawking Thanks for all your help and comments, I’ve managed to get it up and running now!
Now I just need to get the whitelist sorted :grimacing:
-
@Mitchfarino said in MagicMirror on Pi Zero W:
@Hawking Thanks for all your help and comments, I’ve managed to get it up and running now!
No problem.
@Mitchfarino said in MagicMirror on Pi Zero W:
Now I just need to get the whitelist sorted :grimacing:
This worked fine for me, I just added the IP of my regular PC (e.g 192.168.2.185) to the list in the config file so that it looked like
ipWhitelist: ["192.168.2.185", "127.0.0.1", "::ffff:127.0.0.1", "::1"],
If I then typed the ip:port (the port is also defined in the MM config, default is 8080) of my raspi (e.g.
http://192.168.2.170:8080/
) in the browser bar of my regular PC I could see the page also on my regular PC (took 1-2 seconds to load).
If this does not work for you, just open a new thread and provide details. -
BLANK SCREEN, NO CLOCK/CALENDAR/MOMENTS solved and simplified from other topics and posts:
After you follow the instructions in the first post to #23 then jump to here:
24 cd ~/MagicMirror/vendor
25 npm install
26 sudo rebootI’m not a linux expert, but I built this a few weeks back before the latest version of MM and it worked flawlessly. There should be a hook in the original package.json that kicks it into the vendor directory and runs “npm install” there but it doesn’t happen now (5/3/2017).
Also, for those of you who do not have a monitor, after you SSH into your Rpi Zero W:
sudo raspi-config
5 interfacing options
P3 VNC
YES you want to enable the VNC server
reboot when it asks.Use VNC Viewer or whatever, connect to your rpi using either ip address or if you set it up in your DHCP table with a :0 (zero) to see your screen or :1 to have a desktop.
CaptnJB
-
This post is deleted! -
@Iseknutz said in MagicMirror on Pi Zero W:
I installed the image from https://forum.magicmirror.builders/topic/1183/how-i-got-my-magic-mirror-working-on-a-raspberry-pi-0-zero/84 , updated the System to use the onboard wifi and this works for me.
@Iseknutz
At least I can get this method up and running on my RPI0w, but what’s the trick to updating the system to use the onboard wifi? I’ve created the wpa_supplicant.conf and I’ve even jacked with the etc/network/interfaces - but no luck getting it to connect to the network.
Thx -
@kylelmartin can you post or pm your WPA_supplicant.conf file? Please remove your passwords and maybe change your wifi name if that makes you feel better.
How are you updating your wpa-supplicant through a terminal or by copying it onto your card? Windows or Mac?
CaptnJB -
@CaptnJB
here is the wpa_supplicant.conf file - or at least the latest rendition of it.country=US ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev update_config=1 network={ ssid="KLM-Guest" key_mgmt=NONE priority=1 id_str="guest" } network={ ssid="mywebsite.com" psk="oldasspw" priority=2 id_str="klm" }
My regular old wifi network name has a “.” in the name and I thought that might cause some problems. So, I set up a second guest wifi network so this device wouldn’t need a password.
-
@kylelmartin, I apologize for the delay just landed in Madrid. For starters I would take out the id lines. Keep it simple. Try this.
country=US ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev update_config=1 network={ ssid="KLM-Guest" psk="" priority=1 } network={ ssid="KLM" psk="oldasspw" priority=2 }
Also, mywebsite.com should be be your router ssid. If you have it set to that “mywebsite.com” in the file you gave it is most likely “KLM”.
Why would you want the guest network to have priority?
CaptnJB