@bmarofsky said in How I got my Magic Mirror working on a Raspberry Pi 0 (zero):

@Andrius-ok Thank You! Worked Perfectly. Setup Wifi (your SSID and PW were still in there) and your config loaded. I am in the process of converting to my config.

so i have all my modules in place and the system crashes: unable to handle kernel null pointer dereference at virtual address
I’ll roll back to your setup and see if it is stable. i am using calendar, weather, clock and newsfeed- very similar to yours.

@Andrius-ok Thank You! Worked Perfectly. Setup Wifi (your SSID and PW were still in there) and your config loaded. I am in the process of converting to my config.

@VladoPortos same here, but on a Windows PC if i go to the MM url, the pihole stat show perfectly.
could it be a raspbian browser issue?

tried on stretch lite and got this

pi@raspberrypi:~/MagicMirror $ sudo npm install
npm WARN engine http-auth@3.2.3: wanted: {"node":">=4.6.1"} (current: {"node":"4.2.1","npm":"2.14.7"})
npm WARN deprecated coffee-script@1.10.0: CoffeeScript on NPM has moved to "coffeescript" (no hyphen)
npm WARN engine apache-crypt@1.2.1: wanted: {"node":">=4.6.1"} (current: {"node":"4.2.1","npm":"2.14.7"})
npm WARN engine apache-md5@1.1.2: wanted: {"node":">=4.6.1"} (current: {"node":"4.2.1","npm":"2.14.7"})
npm WARN engine hawk@6.0.2: wanted: {"node":">=4.5.0"} (current: {"node":"4.2.1","npm":"2.14.7"})

@j.e.f.f Thank You! Spent 3 days trying to figure this out after my SD card corrupted and I had to rebuild my MM.
(making sure I remember where I store my backup .img)

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?

I have the Analog clock setup but it only works from my laptop browsers (firefox, IE). On the Pi zero (Jessie full) I am running either Midori or KWeb and the clock shows but is stuck at 9:00.

If I switch it to Digital, it works and i see the correct time and the seconds updating. Any thoughts?

EDIT: I tried scaling the clock from 600 to 100 and it started working. Scaled it up to 600, still worked. Rebooted and it stopped.

@MichMich It would be good to require screenshots. Other wise its a good start.

Thanks, looks good!