@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. ;-)

@keroppi I PM’ed you with the link as we can not uploads files here

@tbs86 Assuming you mean MMM-BMW-DS, you can add this to your custom.css file and adjust to your liking .MMM-BMW-DS .image { /* icon size */ width: 1.75%; height: 1.75%; margin-top: 0px; margin-bottom: -10px; }

For future generations looking to solve this problem: I believe one of my modules (MMM-CTA for the record) poops out a ton of log entries. Those fill up my SD card after a few weeks. I ended up installing a pm2 module called pm2-logrotate. https://www.npmjs.com/package/pm2-logrotate I’m setting it to rotate my var/log file before it gets too big. Hopefully this will solve future problems. pi@raspberrypi:~ $ pm2 install pm2-logrotate pi@raspberrypi:~ $ pm2 set pm2-logrotate:max_size 2G

Thanks that was it! I’m not sure how I managed to install such an old version. Incase anyone else has this issue, I followed the instructions here to install the current version.

@blackmirror u need to go to the MMM-DHT-Sensor folder and do npm install there too (and any other modules that have a package,json file supplied) the upgrade SHOULD do this for you, but appears not…

@sandy2503 In many case, You can adjust specific module with this CSS selector. .[MODULENAME] e.g) .clock { width: 400px; } Or you can adjust all modules in specific region with this pattern; region.[REGIONNAME] .module region.right .module { width: 400px; } But some module could override its CSS with higher priority, in that case; Examine all the CSS then solve it one by one. PS For CalenderExt, you can use ellipsis: 20 for truncating title. Anyway, I’m building new calendar module with new parser and looks.

@nico0709 - Have you tried creating a test event in that 3rd calendar that is not repeating? Just to verify that the 3rd calendar is showing up? Is there anything in the logs when the mirror starts?

@tbs86 You’re welcome, mate. :-)

So, it does the same thing now with my other magic mirror install. The other unit is on a 7" touchscreen, I have it alternating between the Weather module and the Weather Forcast module.

@kelemvor I don’t think you want the Lite version. Raspbian Desktop, yes.

thank you guys… you are totaly right.

Hello. *** Disclaimer"“” I have used the search as I do know this has been asked about many times before, but return results do not fit my problem… but concede I may be using several wrong terms in my search… Anyways, Monitor is on smart switch to turn on/off… Pi left on 24/7. When I turn on monitor after 2 days, I see that MM has frozen, so have to manually switch Pi off/on, and everything boots up and works as should. Can someone please point me to what I should be looking at to stop the freezing? Not as if it is running anything intensive - stock modules and 2 small Gifs. Thanks

yeah, I didn’t even realize it was there, either.

@sdetweil Yes, looking for contact info

@dwleo Glad it works now. Cheers!

Re: MMM-SwissStationboard Hi Tried to insert “Kirchberg-Alchenflüh” as a station, but even if I insert the station id which is “8508084” no data is shown. It always says “Loading trains”. If I put the next station which is “Aefligen” or the id which is “8508085” everything works and the data is shown. Thanks for any help! { module: ‘MMM-SwissStationboard’, position: ‘bottom_left’, header: ‘Zugsverbindungen ab Kirchberg-Alchenflueh’, config: { stop: ‘8508084’, // Start train station maximumEntries: 4, // Max departures displayed minWalkingTime: 10, // Minimum time to get to the station hideNotReachable: 0, //Will hide all the not reachable connections }

@marcusjsh Well still doable. Does the return give you a json or xml return?