@FlorianRD You need to be on Magic Mirror versions 2.1.0 or higher (i.e. develop branch).
Edit: What MagicMirror version are you on? 2.1.0? When you navigate from the MMM-Buttons folder to ../../node_modules you should end up in a folder with an electron folder. If there is only a electron-prebuilt folder, it should be possible to fix the issues by upgrading MagicMirror to 2.1.0.
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! firstname.lastname@example.org start: `electron js/electron.js "dev"`
npm ERR! Exit status 1
npm ERR! Failed at the email@example.com 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!
@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:
Now, type as follows:
pi@MagicMirror:~ $ cd MagicMirror/config/
You should now be in MagicMirror/config/ looking like this:
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:
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
And your Magic should have started.
Please continue discussion about install issues here. There is already info on how it can be solved. For other problems with the PIR-Sensor Module please open a new thread in the troubleshooting section.
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.
I’m basically a newbie too. I haven’t seen any video tutorials for installing new modules. But this one I’m recommending has some very simple installation instructions. Feel free to send a PM if you want me to walk you through the process.
@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.
Is there a way to suppress DWD warnings which are higher than x meters?
In my Landkreis there are plenty of warnings above 400 or 600 m which do not directly relate to my hometown as it´s on a 300m level.
Would really appreciate if that could be added as a future option.
As already mentioned, great module which is really useful.
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.