@benderstwin - It sounds like the notification is using a local (to the Pi) file for the notification sound. When you browse to the web app from another machine, the new machine doesn’t have the notification file in the same file path as the Pi. You could try hunting down where this notification noise is being stored and then rewriting the reference to it to go to a web-accessible location. That’s a fair bit of work for an audible notification.

@dsmtweaker If your local content locates under MagicMirror and it’s sub directory, you can contact via http. ~/MagicMirror/YOUR_RESOURCE => http://localhost:8080/YOUR_RESOURCE ~/MagicMirror/modules/MMM-SOMETHING/SOMEWHERE/SOME => http://localhost:8080/modules/MMM-SOMETHING/SOMEWHERE/SOME But other location… hmmm I’m not sure whether symbolic_link would work. If not so, you need another approach. - more complex… just to move your content under MagicMirror would be simpler.

Thanks for your answer. No, There is no .ics url in my CALDAV service and No, I will not use a GAFAM to convert this calendar to a ics… i will probably need to run a service on the pi to locally convert the calendar

I Had Similar i have just moved the pi to boot from sd to SSD that i had and for the life of me a fresh mirror 2.50 version wouldn’t run auto boot for love nor money i used this link in the end and its working well without having to kill everything and start again https://github.com/MichMich/MagicMirror/wiki/Auto-Starting-MagicMirror Hope this helps someone else Install PM2 using NPM: sudo npm install -g pm2 Starting PM2 on Boot To make sure PM2 can do it’s job when (re)booting your operating system, it needs to be started on boot. Luckily, PM2 has a handy helper for this. pm2 startup PM2 will now show you a command you need to execute. Make a MagicMirror start script. To use PM2 in combination with MagicMirror, we need to make a simple shell script. Preferable, we put this script outside the MagicMirror folder to make sure it won’t give us any issues if we want to upgrade the mirror. cd ~ nano mm.sh Add the following lines: cd ~/MagicMirror DISPLAY=:0 npm start Save and close, using the commands CTRL-O and CTRL-X. Now make sure the shell script is executable bij performing the following command: chmod +x mm.sh You are now ready to the MagicMirror using this script using PM2. Starting your MagicMirror with PM2 Simply start your mirror with the following command: pm2 start mm.sh You mirror should now boot up and appear on your screen after a few seconds. Enable restarting of the MagicMirror script. To make sure the MagicMirror restarts after rebooting, you need to save the current state of all scripts running via PM2. To do this, execute the following command: pm2 save And that’s all there is! You MagicMirror should now reboot after start, and restart after any failure. Controlling you MagicMirror via PM2. With your MagicMirror running via PM2, you have some handy tools at hand: Restarting your MagicMirror: pm2 restart mm Stopping your MagicMirror: pm2 stop mm Show the MagicMirror logs: pm2 logs mm Show the MagicMirror process information: pm2 show mm

Thanks for your help! I think if I could solve the not autologging in into the GUI my problem is fixed. I’ve started raspi-config and selected auto-login desktop, but after reboot the login form is shown. and when manually typing in the password i get “cannot currently show the desktop”. No password change has occured (the password is accepted in ssh) @bhepler said in gui not autologging in and pm2 is not starting automatically: @mdissel - When you installed pm2, did you run the command that it spit out for you? Try running this command: pm2 startup. It will give you a command that you will have to copy & paste and run with the sudo command. Something like this: sudo su -c "env PATH=$PATH:/home/unitech/.nvm/versions/node/v4.3/bin pm2 startup. Yes, I did. Anyhow, copy & paste that command and see if that solves your problem. As for “cannot currently show the desktop”, I’m assuming that you’re working directly on the pi itself and not SSH from another computer. A couple things to check: You’re running Raspian Stretch, with desktop (not lite). Yes… it worked at some time, You ran the system updates as soon as you got the pi connected to the internet (sudo apt-get update && sudo apt-get upgrade -y) Yes. I did You’re still using the pi user and not some other user account. It did work with the pi user. Thanks again!

@alenba2 Well MM definitely works with stretch but nevertheless… if it works, I guess it’s ok

I’m having a similar issue. For any events more than 24 hours out, it is only displaying the number of days away + end time. [image: 1544800657473-cal.png] I had to rebuild my MM after the Pi I was using crashed, so I believe I was running the previous version of MM before the rebuild. I seem to recall the calendar module displaying number of days in future + start time before. FWIW, I’m using google calendar.

looks like you did not complete the install… cd MagicMirror npm install when that completes, look for node_modules/electron. is that folder present? if so, then try npm start again

As title suggests, I am unable to connect to AWS IoT Core when using MMM-MirrorMirrorOnTheWall. The console would be stuck on “Attempt to connect to AWS”, tried giving it commands also but to no avail. Certs folder has also been put into …/modules/MMM-MirrorMirrorOnTheWall/

@sean Looks like I’ll be learning how to program in Java script :) Thanks for the tips. BTW: I found the issue with the python not running, seems the call from node changes the name of the script so main () had a different name to the import. Didn’t cure the snowboy issue (at least it got called, didn’t respond to wake word though 🤔, I’ll ask on the snowboy forum why that might be), but everything else worked.

I have a problem with my .ics file for the standard calendar module. The exeptions “exdate” of an event are stored in the wrong format, it look like this: BEGIN:VEVENT DTSTAMP:20181120T052855Z CLASS:PUBLIC CREATED:20181120T052855Z DESCRIPTION: DTEND;TZID=Europe/Zurich:20170828T082000 DTSTART;TZID=Europe/Zurich:20170828T075000 EXDATE:20170925T055000Z,20171002T055000Z,20171009T055000Z,20171016T055000 Z,20171023T055000Z LAST-MODIFIED:20181120T052855Z RRULE:FREQ=WEEKLY;UNTIL=20171112T065000Z;BYDAY=MO SEQUENCE:0 SUMMARY:xxx TRANSP:OPAQUE UID:2b8ae706-c70f-4592-a380-6d301b5bb624 X-MICROSOFT-CDO-BUSYSTATUS:BUSY END:VEVENT but they should look like this: BEGIN:VEVENT DTSTAMP:20181120T052855Z CLASS:PUBLIC CREATED:20181120T052855Z DESCRIPTION: DTEND;TZID=Europe/Zurich:20170828T082000 DTSTART;TZID=Europe/Zurich:20170828T075000 EXDATE:20170925T055000Z EXDATE:20171002T055000Z EXDATE:20171009T055000Z EXDATE:20171016T055000Z EXDATE:20171023T055000Z LAST-MODIFIED:20181120T052855Z RRULE:FREQ=WEEKLY;UNTIL=20171112T065000Z;BYDAY=MO SEQUENCE:0 SUMMARY:xxx TRANSP:OPAQUE UID:2b8ae706-c70f-4592-a380-6d301b5bb624 X-MICROSOFT-CDO-BUSYSTATUS:BUSY END:VEVENT Since these are wrong, none of the calendar elements are shown. Any suggestions how to change that?

@radu_stancu great debugging! and thanks for the detailed feedback… someone else might fall into this same trouble

@redink Good news!

Anybody have any clues? I’m at a loss here

what module do you have installed for voice recognition? and map viewing?

@mykle1 there is no better thought motivator than posting on a live forum…!!

@j-e-f-f thanks very much , i’m from china . This is why I replied late. Your opinion is very useful to me. About hardware performance issues. I think it can be done by other GPU devices. The key is the second question you mentioned. How to position the face in the mirror.I will follow your suggestion to test. If I succeed, I will show it here. Thanks again!

Hi, I am trying to install MMM-awesome-alexa to my magic mirror, but I am having some issues. I have all of the alexa developer keys, but it ends up to a black screen on my raspberry pi. I have been searching all over the internet to find out why this is happening, but I noticed something on my terminal responding, Starting MagicMirror: v2.5.0 Loading config ... Loading module helpers ... WARNING! Could not load config file. Starting with default configuration. Error found: Error: Cannot find module '/home/pi/MagicMirror/modules/MMM-awesome-alexa/node_modules/snowboy/lib/node/binding/Release/electron-v2.0-linux-arm/snowboy.node' Loading module helpers ... App threw an error during load Error: Cannot find module '/home/pi/MagicMirror/modules/MMM-awesome-alexa/node_modules/snowboy/lib/node/binding/Release/electron-v2.0-linux-arm/snowboy.node' at Module._resolveFilename (module.js:543:15) at Function.Module._resolveFilename (/home/pi/MagicMirror/node_modules/electron/dist/resources/electron.asar/common/reset-search-paths.js:35:12) at Function.Module._load (module.js:473:25) at Module.require (module.js:586:17) at require (internal/module.js:11:18) at Object.<anonymous> (/home/pi/MagicMirror/modules/MMM-awesome-alexa/node_modules/snowboy/lib/node/index.js:8:29) at Object.<anonymous> (/home/pi/MagicMirror/modules/MMM-awesome-alexa/node_modules/snowboy/lib/node/index.js:132:3) at Module._compile (module.js:642:30) at Object.Module._extensions..js (module.js:653:10) at Module.load (module.js:561:32) Whoops! There was an uncaught exception... { Error: Cannot find module '/home/pi/MagicMirror/modules/MMM-awesome-alexa/node_modules/snowboy/lib/node/binding/Release/electron-v2.0-linux-arm/snowboy.node' at Module._resolveFilename (module.js:543:15) at Function.Module._resolveFilename (/home/pi/MagicMirror/node_modules/electron/dist/resources/electron.asar/common/reset-search-paths.js:35:12) at Function.Module._load (module.js:473:25) at Module.require (module.js:586:17) at require (internal/module.js:11:18) at Object.<anonymous> (/home/pi/MagicMirror/modules/MMM-awesome-alexa/node_modules/snowboy/lib/node/index.js:8:29) at Object.<anonymous> (/home/pi/MagicMirror/modules/MMM-awesome-alexa/node_modules/snowboy/lib/node/index.js:132:3) at Module._compile (module.js:642:30) at Object.Module._extensions..js (module.js:653:10) at Module.load (module.js:561:32) code: 'MODULE_NOT_FOUND' } 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/issues Launching application. I looked through it and found that snowboy was not found, and I couldn’t even find it myself with the directory it provided. I looked around and found something saying I needed to use npm run electron-rebuild, but it also gives a error, Rebuild Failed An unhandled error occurred inside electron-rebuild Could not detect abi for version 2.0.0 and runtime electron. Updating "node-abi" might help solve this issue if it is a new release of electron Error: Could not detect abi for version 2.0.0 and runtime electron. Updating "node-abi" might help solve this issue if it is a new release of electron at Object.getAbi (/home/pi/MagicMirror/modules/MMM-awesome-alexa/node_modules/electron-rebuild/node_modules/node-abi/index.js:43:9) at _callee6$ (/home/pi/MagicMirror/modules/MMM-awesome-alexa/node_modules/electron-rebuild/lib/rebuild.js:152:37) at tryCatch (/home/pi/MagicMirror/modules/MMM-awesome-alexa/node_modules/electron-rebuild/node_modules/regenerator-runtime/runtime.js:63:40) at Generator.invoke [as _invoke] (/home/pi/MagicMirror/modules/MMM-awesome-alexa/node_modules/electron-rebuild/node_modules/regenerator-runtime/runtime.js:337:22) at Generator.prototype.(anonymous function) [as next] (/home/pi/MagicMirror/modules/MMM-awesome-alexa/node_modules/electron-rebuild/node_modules/regenerator-runtime/runtime.js:96:21) at Generator.tryCatcher (/home/pi/MagicMirror/modules/MMM-awesome-alexa/node_modules/bluebird/js/release/util.js:16:23) at PromiseSpawn._promiseFulfilled (/home/pi/MagicMirror/modules/MMM-awesome-alexa/node_modules/bluebird/js/release/generators.js:97:49) at /home/pi/MagicMirror/modules/MMM-awesome-alexa/node_modules/bluebird/js/release/generators.js:201:15 at _rebuild (/home/pi/MagicMirror/modules/MMM-awesome-alexa/node_modules/electron-rebuild/lib/rebuild.js:613:18) at rebuild (/home/pi/MagicMirror/modules/MMM-awesome-alexa/node_modules/electron-rebuild/lib/rebuild.js:624:28) at _callee$ (/home/pi/MagicMirror/modules/MMM-awesome-alexa/node_modules/electron-rebuild/lib/cli.js:160:45) at tryCatch (/home/pi/MagicMirror/modules/MMM-awesome-alexa/node_modules/electron-rebuild/node_modules/regenerator-runtime/runtime.js:63:40) at Generator.invoke [as _invoke] (/home/pi/MagicMirror/modules/MMM-awesome-alexa/node_modules/electron-rebuild/node_modules/regenerator-runtime/runtime.js:337:22) at Generator.prototype.(anonymous function) [as next] (/home/pi/MagicMirror/modules/MMM-awesome-alexa/node_modules/electron-rebuild/node_modules/regenerator-runtime/runtime.js:96:21) at Generator.tryCatcher (/home/pi/MagicMirror/modules/MMM-awesome-alexa/node_modules/bluebird/js/release/util.js:16:23) at PromiseSpawn._promiseFulfilled (/home/pi/MagicMirror/modules/MMM-awesome-alexa/node_modules/bluebird/js/release/generators.js:97:49) npm ERR! code ELIFECYCLE npm ERR! errno 255 npm ERR! mmm-awesome-alexa@1.0.0 electron-rebuild: electron-rebuild --pre-gyp-fix npm ERR! Exit status 255 npm ERR! npm ERR! Failed at the mmm-awesome-alexa@1.0.0 electron-rebuild script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run can be found in: npm ERR! /home/pi/.npm/_logs/2018-12-05T14_47_11_588Z-debug.log Is there any fix for this that anyone knows? I want to get this built before the end of the week so I can get it ready for next year. Thanks!

@cowboysdude No, they will magically appear on your mirror. ;-)