@greda said in Manage MagicMirror by smartphone: Thanks you Mykle 1 !!! De rien, mon ami

To troubleshoot, I changed http://localhost:8080 to http://www.google.com. I rebooted and it came up with google on the screen. I am not sure if it is the browser not connecting to the MM2 server or the server not working.

Thank you so much! You have guided me to right direction and now I am doing requests the right way in node_helper :)

In the installation Script i saw an installation of PM2, the Splash Screen and some more, that would then still be kept in the system…

@cowboysdude can you help me in MMM-NOAA and MMM-awesome-alexa

@Mykle1 I agree with you on that. There’s no reason to upgrade to stretch unless you really need to. In my case, I had to upgrade to stretch because the latest alexa sdk doesn’t support jessie. When I say upgrade, I moved every thing to a new card. My pi zero runs pihole + open vpn and is still on jessie. No reason to switch that one unless the foundation stops releasing updates for jessie.

Well. After manually installing version 1.7.6 of electron and globally installing the coffee and lint nodes that the initial install complained about. I ran the manual install and everything seems to be working. I now have to add back my modules and see where we are. Thanks.

Trying to install that module, get the following results : MMM-RTSPStream@1.2.1 postinstall /home/pi/MagicMirror/modules/MMM-RTSPStream ./install_sd_patch.sh && sudo npm i -g http-server Applying Graceful Shutdown patch to MagicMirror. error: Anwendung des Patches fehlgeschlagen: js/electron.js:96 error: js/electron.js: Patch konnte nicht angewendet werden npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules/chokidar/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.1.3: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“arm”}) npm ERR! Linux 4.9.35-v7+ npm ERR! argv “/usr/bin/node” “/usr/bin/npm” “install” npm ERR! node v6.12.0 npm ERR! npm v3.10.10 npm ERR! code ELIFECYCLE npm ERR! MMM-RTSPStream@1.2.1 postinstall: ./install_sd_patch.sh && sudo npm i -g http-server npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the MMM-RTSPStream@1.2.1 postinstall script ‘./install_sd_patch.sh && sudo npm i -g http-server’. 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 MMM-RTSPStream package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! ./install_sd_patch.sh && sudo npm i -g http-server npm ERR! You can get information on how to open an issue for this project with: npm ERR! npm bugs MMM-RTSPStream npm ERR! Or if that isn’t available, you can get their info via: npm ERR! npm owner ls MMM-RTSPStream 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/modules/MMM-RTSPStream/npm-debug.log What I am supposed to do know ?

Hello, I have problems with the MMM-PIR-Sensor Module. I cloned it in my module-folder and installed it. The Output from the Sensor is plugged at pin22 of the raspberryPi. The sensitivity is almost rotated to left. Also the Delay time. The Relay is plugged at pin23 of the RaspberryPi. module: “MMM-PIR-Sensor”, config: { sensorPIN: 22, powerSavingDelay: 5, relayPIN: 23, relayOnState: 1, } powerSavingDelay is 5 seconds, so I don’t need to wait to long while testing at startup the raspberry, the Relay is switched off, after a short while it is switched on. But it is independent of the PIR-Sensor. Also if I take away the PIR-Sensor and plugg the PIN22 directly to 5V, GND, the Relay doesn’t switch.

I know this big Tower :-)

Thank you. I appreciate the checking. I ended up re-running the install script and it worked. I have no idea but am very happy. Now that I know not to mess with the modules, it is much easier.

@greda said in Disable ipWhitelist: Thank you so much Mukle1. Cheers!

Sorry i find : git pull !!!

@termeric said in Starting MM on Reboot: Thanks, i needed to execute the command All is well. You’re welcome, mate. :-)

I’m using the module and I have been able to get it working, try this in the config.js { module: “MMM-Dublin-Bus”, position: “bottom_left”, config: { stopNumber: 111, updateInterval: 10, mode: “dom” } }

@d00my Does it work now? I think I have an similar problem with the PiCam. I start the Magic Mirror and after selecting the camera nothing is happend. It doesn’t try do recognizie any user. I reinstalled all, and it worked ONCE… now I have the same problem like bevor. I tried intervall: 1, 2 and 5.

I just came across this post while also looking for a way to do this. After not finding any answer by searching, I decided to look at the css files included with this module and see if I could figure it out. I’m a new at this, but easily found the lines to make changes at for displaying the pointer visibility: in MMM-Carousel.css, make the following changes (in Bold): … .control label { z-index: 0; display: none; text-align: center; line-height: 50px; position: relative; width: 50px; height: 50px; left: 33%; /* Center in .control div: this.width / .control.width; / top: 33%; / Center in .control div: this.height / .control.height;; */ font-size: 50px; color: #FFF; cursor: pointer !important; opacity: 0.5; } /Increase brightness when directly over/ .control label:hover { opacity: 1.0; } …