@postremalone - Could you provide some more information? Tell us what command you entered and specifically what messages you received. Remember to use the markup tags.
Read the statement by Michael Teeuw here.
Posts made by bhepler
-
RE: PM2 is not installing. Is Anyone Having The Same Problem?
-
RE: Two Instances in PM2
@shazglass - Ah. Okay, easy enough.
You’re missing the
mm.sh
script. I’m not sure how you had this registered in pm2 earlier, but we can fix it. We’ll use nano to create a newmm.sh
file:cd ~ nano mm.sh
This will give you a blank screen with the nano options at the bottom. Enter the following lines:
cd ~/MagicMirror DISPLAY=:0 npm start
When you’re done, hit
ctl+o
to save the file and thenctl+x
to exit nano. Then just like you did earlier, make your script executable by enteringchmod +x mm.sh
Before we go any further, we need to test your script. From the command line, enter
./mm.sh
Your mirror should start after 30 seconds or so. Try this and report back with any errors and behaviors. Also, please use the markup commands when posting code and logs (follow this link for a quick tutorial). -
RE: MMM-Hotword
Excellent! I can finally get my mirror to respond to a particular swear word. It’s a literary reference. Honest.
-
RE: Two Instances in PM2
@shazglass - Hmm. I don’t know. It should be working normally at this point. Let’s try switching to the previous process. We’ll delete the one that the installer created, then add the one to your script.
First, we remove the existing process:
cd ~ pm2 delete MagicMirror pm2 save
Then we use your
mm.sh
script that you had earlier.pm2 flush pm2 start mm.sh pm2 save
At this point, your mirror should come up in about 30 seconds. If it does not, enter
pm2 log mm
and copy the results here. Be sure to use the forum markup tools to help format your log messages. -
RE: Weird graphical error
After a day, the flashing effect seems to occur about an hour after mirror boot. So far, it has occurred twice. Rebooting the mirror seems to be the only way to fix it.
Stopping the MagicMirror process will drop me back to the desktop, but it will still have the graphical corruption.
-
Weird graphical error
In short, the upgrade to v2.4.1 was a chore. Turning on either OpenGL driver from the
/boot/config.txt
file prevented the Pi from booting. Eventually, the SD card became corrupted and I had to re-flash the Raspbian image. After that, the install went pretty smoothly. It just took time.However, now I’m getting this weird flashing effect on my mirror. It seems to be at the OS level, as restarting the MagicMirror process through pm2 didn’t solve the issue. Rebooting the mirror did make the effect go away, but I’m not sure for how long. I’ll provide more updates as I collect more information.
Here’s the effect:
https://youtu.be/q4so_JpdDkgAny help would be appreciated.
-
RE: E-paper large screen instead of a mirror
@gooral - That’s an interesting idea. What advantages are you hoping to find with e-paper instead of a computer monitor?
-
RE: Two Instances in PM2
@shazglass All right, we’ll get you through it.
pm2 runs on Pi startup and will start your mirror process for you. There should be only one listing. If you ran the installation script and said “yes” to using pm2, there should be only one process called MagicMirror in pm2.
To remove the
mm
process from pm2, enter the following:cd ~ pm2 stop all pm2 delete mm pm2 save rm mm.sh pm2 flush pm2 start MagicMirror
At this point, your Magic Mirror interface should appear after a minute or so. You can press
ctrl-q
to exit the Magic Mirror interface, but pm2 should bring it back up in short order. -
RE: MMM-NOAA
I’ve been trying to get this module to work and for the life of me I can’t get it to show up. I’ve gone as minimalist as I can and it’s still not appearing.
Here’s my config:
{ module: "MMM-NOAA", position: "top_right", config: { apiKey: "debxxxxxx", airKey: "Fpyyyyy" } },
Here’s the error that I see in the web browser:
TypeError: "allDay is undefined" getDomhttp://10.0.0.10:8080/modules/MMM-NOAA//MMM-NOAA.js:344:2 updateDomhttp://10.0.0.10:8080/js/main.js:110:28 updateDomhttp://10.0.0.10:8080/js/main.js:109:10 createDomObjectshttp://10.0.0.10:8080/js/main.js:53:29 createDomObjectshttp://10.0.0.10:8080/js/main.js:24:3 modulesStartedhttp://10.0.0.10:8080/js/main.js:471:4 startModuleshttp://10.0.0.10:8080/js/loader.js:59:3 loadNextModulehttp://10.0.0.10:8080/js/loader.js:40:6 onloadhttp://10.0.0.10:8080/js/loader.js:203:42
And I keep seeing this in the pm2 logs:
0|MagicMir | libGL error: MESA-LOADER: failed to retrieve device information 0|MagicMir | MESA-LOADER: failed to retrieve device information 0|MagicMir | MESA-LOADER: failed to retrieve device information