Read the statement by Michael Teeuw here.
Installing on a Pi Zero
-
you made my day…
it works…
the first differences i encountered was the Installation of electron …
this i didn’t found at all the others…and i thought before, that this will be the quest…
regarding to the warnings installing npm
you could fix that with “npm Audit fix” or “npm Audit fix --force”
as suggested…i did this also, so maybe this could be an error too…
and if it works but this warnings, who cares…. :-)
have a great day…
thank you -
Awesome write up. Super helpful!
-
Thank you very much for this work! The tutorial works perfectly. I just installed it in a rpi zero W. Highly recommended for anyone who wants to install it on this SBC.
-
Many thanks Andrew - worked well for me (other than first step: connecting to wifi with WPA2 needed some minor tweaks.)
-
@cdh1001 please specify tweaks as they might help others.
-
@andyc7687 - I needed to delete the line:
key_mgmt=WPA-PSK
Based on discussions elsewhere I originally tried renaming Key_mgmt to WPA2 and/or changing group=CCMP, but neither of those were necessary for me; simply deleting the line was sufficient. -
@cdh1001 thanks, I will amend my guide over the weekend then.
-
Thanks for the script and the hints so far :-)
Unfortunately I am really frustrated after x installations. :-( Currently everything is installed the autostart works but chrome says “err_connection_refused”!
Does anyone have an idea?
Zero W V1.1 / Raspian Desktop / no sudo
-
@smolo Some suggestions: First, make sure that some form of IP address is present in the
address
key. Usually 127.0.0.1, but the IP address of your pi will probably work too. Without that value, the web server has a tendency to freak out.Second, make sure you are specifying the port in your web call. That one has bitten me a couple times.
Third, I would double-check your IP whitelist in the
config.js
. Possibly open it up to all connections and attempt to view the magic mirror from another computer. See if the problem is local to the PI Zero or if it is on a deeper level. -
@bhepler
First, as a supplement the installation is absolute standard except for another VNC server.
Chromium starts automaticly with http://localhost:8080I have already tested the following constellations before my post.
the local ip (192.168.2.84:8080)
127.0.0.1:8080
localhost:8080“err_connection_refused”
with https browser fault > “err_address_unreachable”
Other things :…
- ublock is inactive!
- Configuration vom MagicMirror Config:
var config = {
port: 8080,
address: “0.0.0.0”,
ipWhitelist: [], - Test from another pc > “err_connection_refused”