@cowboysdude And I surely will. I think all of this stuff is amazing and I’m learning as quickly as I can. I’ll be glad to help when I can. I wanna get me some of those ^ Peace

Okay, next try… npm ERR! Linux 4.4.26-v7+ npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "start" "dev" npm ERR! node v7.4.0 npm ERR! npm v4.0.5 npm ERR! code ELIFECYCLE npm ERR! magicmirror@2.0.0 start: `electron js/electron.js "dev"` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the magicmirror@2.0.0 start script 'electron js/electron.js "dev"'. npm ERR! Make sure you have the latest version of node.js and npm installed. npm ERR! If you do, this is most likely a problem with the magicmirror package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! electron js/electron.js "dev" npm ERR! You can get information on how to open an issue for this project with: npm ERR! npm bugs magicmirror npm ERR! Or if that isn't available, you can get their info via: npm ERR! npm owner ls magicmirror npm ERR! There is likely additional logging output above. npm ERR! Please include the following file with any support request: npm ERR! /home/pi/MagicMirror/npm-debug.log

So ended up updating npm to resolve the grunt/mini match issues and now all is working in perfect harmony again. No issue at all with remote control in the first place but instead having to update MM and in turn update npm!

@shashank your prayers has been heard https://forum.magicmirror.builders/topic/1575/mmm-buttons-connect-multiple-buttons-to-send-configurable-notifications

Hi, read this… https://forum.magicmirror.builders/topic/1326/ipwhitelist-howto/11

@phrazelle In this thread we basically have the same question, so lets continue the discussion there.

@PhilsterM9 Hi again, maybe I’m missing something… If you followed the install guide when you installed… When you SSH in to your Pi (or open a terminal on the desktop of the pi) you should end up in a prompt looking like this: pi@MagicMirror:~ $ Now, type as follows: pi@MagicMirror:~ $ cd MagicMirror/config/ You should now be in MagicMirror/config/ looking like this: pi@MagicMirror:~/MagicMirror/config $ To copy a file enter: pi@MagicMirror:~/MagicMirror/config $ cp config.js.sample config.js Check if the files where copied with ls both file should be there now: pi@MagicMirror:~/MagicMirror/config $ ls Listed like this: config.js config.js.sample Now, if you want you can edit your config file: pi@MagicMirror:~/MagicMirror/config $ nano config.js Change whatever you need to change… But you actually don’t have to change anything just for testing it. Now restart the MagicMirror with pm2 like this: pi@MagicMirror:~/MagicMirror/config $ pm2 restart mm You should se something like this: Restarts are now immutable, to update environment or conf use --update-env [PM2] Applying action restartProcessId on app [mm](ids: 0) [PM2] [mm](0) ✓ ┌──────────┬────┬──────┬───────┬────────┬─────────┬────────┬─────┬──────────┬──────────┐ │ App name │ id │ mode │ pid │ status │ restart │ uptime │ cpu │ mem │ watching │ ├──────────┼────┼──────┼───────┼────────┼─────────┼────────┼─────┼──────────┼──────────┤ │ mm │ 0 │ fork │ 26361 │ online │ 32 │ 0s │ 22% │ 2.3 MB │ disabled │ └──────────┴────┴──────┴───────┴────────┴─────────┴────────┴─────┴──────────┴──────────┘ Use `pm2 show ` to get more details about an app pi@MagicMirror:~/MagicMirror/config $ And your Magic should have started. :)

Is there a way to change the size of a module? I’m looking at trying to shrink the size of the calendar module–make it more narrow. I would like it to be the size of the weather update. Thanks.

@jakubc You are right, the comma is redundant, but it doesn’t do any harm in this environment. In this case it did not work because lolobyte was running a MagicMirror version which did not have this feature. :)

Never mind. It just doesn’t work with Microsoft Edge. Not a problem.

My problem is that i dont see it at all :( https://forum.magicmirror.builders/post/12059

@mh77 a string in javascript is handled as true, so 'false' => true

@bhepler That’s what I had concluded as well. There’s already the wordnik module , I’ve looked into its code, couldn’t find out how to edit it for my usage though, since my coding knowledge is very limited. Maybe the bible verse module? I’ll give it a go.

Should be fixed in the develop branch now: https://github.com/MichMich/MagicMirror/issues/611#issuecomment-272714388

From what I have found, Alexa can now be handsfree. Here is an example: http://lifehacker.com/how-to-build-your-own-amazon-echo-with-a-raspberry-pi-1787726931 Hope this helps.

Hi Guys. I wonder if you could help. I have installed MMM-Facial-Recognition module, did all the steps and have all files in right place. Face training went fine as well. When I start my magic mirror all my modules are loading fine except Facial Recognition. I get in terminal: connecting socket for: MMM-Facial-Recognition Starting module helper: MMM-Facial-Recognition Sockets connected & modules started I don’t get anything else after that. When I do lsusb I get camera shown as: Bus 001 Device 008: ID 046d:0825 Logitech, Inc. Webcam C270 As far as I understand, I need to have usbCam true, which I do, and inside MMM-Facial-Recognition module there are 2 files (configure.py and webcam.py) which mention Device ID. My question is, what device ID i have to put in those 2 files? my cam is on Bus 001 Device 008: ID 046d:0825 Logitech, Inc. Webcam C270. Cheers,

@hk24 in the node_helper you could extend the routes of the express server so when you click the link there will be a request send to your node_helper script which can then activate the lightbulb. see an example here https://github.com/paviro/MMM-syslog/blob/master/node_helper.js#L17 the link would look like this http://MIRROR_IP:MIRROR_PORT/syslog?type=INFO&message=YOUR_MESSAGE

Any idea where that LED.py script came from? Is it possible that this is a script that you’ve created at some point learning how to control an LED with GPIO outputs? Maybe posting exact steps and commands that you are running, along with output that you get would give us some more information to troubleshoot and help you.

@binderth said in Wunderlist won't display entries: CLIENT ID: 20 characters CLIENT SECRET: 60 characters Please be aware, that in the Wunderlist API there’s a CLIENT SECRET, which is exactly as long as the ACCESS TOKEN. The ACCESS TOKEN is not shown directly after generating the Keys, there’s a button “CREATE ACCESS TOKEN”, after that, the token is generated on the fly (note: it changes, everytime you press the button!). Then you can put in the token, which then resulted in my lists showing up in the MM as expected! ;) So please be aware, there are in fact three keys, only two are needed in config.js.