Read the statement by Michael Teeuw here.
How I got my Magic Mirror working on a Raspberry Pi 0 (zero)
-
@SebTota I went to my old image from before the update and thats still working fine, but when I updated it, it again had the error come up. The only difference is last time I did the update it said Error: Cannot find module ‘colors’
-
@SebTota
I still don’t understand what update you are referring to.
Both error messages sound like there are modules missing (either “express” or “colors”).What happens if you do
cd ~/MagicMirror && sudo npm install cd ~/MagicMirror/vendor && npm install -
@Hawking My MagicMirror has been sitting for a long time. When I recently finished the frame to get the computer display and rpi zero out of my closet I booted the rpi zero and on the top of the display it said A New Version of Magic Mirror is available or something along those lines. So I went into the MagicMirror folder and used the command “git pull && npm install” as specified in the README file of MagicMirror.
-
@SebTota said in How I got my Magic Mirror working on a Raspberry Pi 0 (zero):
git pull && npm install
Have there been errors when you did so?
I got
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/me/MagicMirrorThats why I then did
cd ~/MagicMirror/vendor && npm installin addition (see my post above). Maybe this also solves your problem.
-
@Hawking Sorry to keep bothering you but I ended up making it work with the two commands you told me to do. Now my problem is when the Pi Zero W is booting it connects to the WiFi but when magic mirror boots the pi disconnects.
-
@SebTota
Just to make sure that I understand the problem correctly:
You see the MagicMirror on the screen (Clock running etc). but you can no longer connect to the Pi Zero (using eg. ssh)?Just as a test:
What happens if you disable the MagicMirror from autostart (for example by moving the MagicMirror start script from /etc/init.d/ to your home directory) and start it manually while you are already logged in? I don’t know your exact setup or your Linux knowledge, if you need further help how to do this, just let me know. -
@Hawking I actually eventually got it working. Thanks so much for all your help!
-
Hello everyone.
I’ve followed the instructions and did everything in the comments (all 12 pages) to make sure I am doing them right. I was able to see MM2 thru the browser but on my screen, it is showing white screen.
Loading config ... Loading module helpers ... No helper found for module: alert. Initializing new module helper ... Module helper loaded: updatenotification No helper found for module: clock. Initializing new module helper ... Module helper loaded: calendar No helper found for module: compliments. No helper found for module: currentweather. No helper found for module: weatherforecast. Initializing new module helper ... Module helper loaded: newsfeed All module helpers loaded. Starting server on port 8080 ... Server started ... Connecting socket for: updatenotification Connecting socket for: calendar Starting node helper for: calendar Connecting socket for: newsfeed Starting module: newsfeed Sockets connected & modules started ... Ready to go! Please point your browser to: http://localhost:8080 Whoops! There was an uncaught exception... { [Error: listen EADDRINUSE :::8080] code: 'EADDRINUSE', errno: 'EADDRINUSE', syscall: 'listen', address: '::', port: 8080 } MagicMirror will not quit, but it might be a good idea to check why this happened. Maybe no internet connection? If you think this really is an issue, please open an issue on GitHub: https://github.com/MichMich/MagicMirror/issuesmind helping me out with this?
-
@hoggboss22 your mm seems being excuted multiple. Common pitfal is that more than one browser are opened.(maybe your previous test running?)
Or your machine is already using port 8080.Kill all browsers(and node or npm) and restart. Or change port in your config like 8088.
-
I thought the same thing, i changed from 8080 to 9090 and it gave me the same error. I ran the net stat command to find the port being in used and guess what… there was nothing that is using 8080 or 9090
Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 0.0.0.0:ssh 0.0.0.0:* LISTEN tcp6 0 0 [::]:tproxy [::]:* LISTEN tcp6 0 0 [::]:ssh [::]:* LISTEN udp 0 0 0.0.0.0:mdns 0.0.0.0:* udp 0 0 0.0.0.0:49645 0.0.0.0:* udp 0 0 0.0.0.0:bootpc 0.0.0.0:* udp6 0 0 [::]:mdns [::]:* udp6 0 0 [::]:44605 [::]:* raw6 0 0 [::]:ipv6-icmp [::]:* 7 Active UNIX domain sockets (only servers) Proto RefCnt Flags Type State I-Node Path unix 2 [ ACC ] STREAM LISTENING 7951 /var/run/dbus/system_bus_socket unix 2 [ ACC ] STREAM LISTENING 7954 /var/run/avahi-daemon/socket unix 2 [ ACC ] STREAM LISTENING 7957 /run/thd.socket unix 2 [ ACC ] STREAM LISTENING 10463 @/tmp/.X11-unix/X0 unix 2 [ ACC ] STREAM LISTENING 5161 /run/systemd/fsck.progress unix 2 [ ACC ] STREAM LISTENING 10321 /run/user/1000/systemd/private unix 2 [ ACC ] STREAM LISTENING 10326 /run/user/1000/gnupg/S.gpg-agent unix 2 [ ACC ] STREAM LISTENING 10329 /run/user/1000/bus unix 2 [ ACC ] STREAM LISTENING 4967 /run/systemd/private unix 2 [ ACC ] STREAM LISTENING 10331 /run/user/1000/gnupg/S.gpg-agent.browser unix 2 [ ACC ] STREAM LISTENING 10363 /run/user/1000/gnupg/S.gpg-agent.ssh unix 2 [ ACC ] STREAM LISTENING 10365 /run/user/1000/gnupg/S.gpg-agent.extra unix 2 [ ACC ] STREAM LISTENING 8845 /var/run/dhcpcd.sock unix 2 [ ACC ] STREAM LISTENING 5005 /run/systemd/journal/stdout unix 2 [ ACC ] STREAM LISTENING 8847 /var/run/dhcpcd.unpriv.sock unix 2 [ ACC ] SEQPACKET LISTENING 5325 /run/udev/control unix 2 [ ACC ] STREAM LISTENING 10464 /tmp/.X11-unix/X0
