Hi guys, I just wanted to say thank you to @bhepler and @sdetweil for trying to help me with this problem. In the end I just used a very old backup at first and updated it, which worked fine at first and yesterday I tried setting my RPi up from scratch again and it worked perfectly! I’m sorry for anybody who encounters the same error and tries finding answers here, sadly there doesn’t seem to be a perfect solution for this. MrKnight230

@sdetweil I finally got it working again!:thumbs_up: I did a full fresh installation on a new SD card with complete latest Raspian and new MM and all the modules I used before…and still the same behavior: MMM-IFrame showed nothing and I got the same warnings as mentioned below. Then I tried MMM-SmartWebDisplay by @AgP42 which finally displays my video stream again. (BTW: This also works with other URLs as described in the documentation) Many thanks for this module.:clapping_hands: For all having issues with MMM-iFrame, MMM-IFrame-Ping etc., try MMM-SmartWebDisplay. Don’t forget to do a NPM install in the module folder once the module is cloned. Thanks, Peter

@Stoffbeuteluwe autoplay is a new restriction in the browsers… you have to click on something… dumb for a mirror with no mouse!! fix edit the smart-mirror/main.js find the line let mainWindow and change it so it looks like this let mainWindow; function createWindow() { app.commandLine.appendSwitch('autoplay-policy', 'no-user-gesture-required'); //< -------- added then save and restart MM

it does not work the way you want… not a config option… code would have to be changed

@JcMarin cool… can u mark this solved?

actually this is because you have fired a timer on the slide update showSlides2: function () { if (!this.slideIndex) { this.slideIndex = 0; } var i; var slides = document.getElementsByClassName("mySlides"); for (i = 0; i < slides.length; i++) { console.log(slides[i]); slides[i].style.display = "none"; } this.slideIndex++; slides[this.slideIndex - 1].style.display = "block"; if (this.slideIndex > (slides.length - 1)) { this.slideIndex = 0 } setInterval(this.showSlides2, 2000); //< ------- here restarts the function, BUT inside the function 'this'; becomes the context of the timer routine and not the module.. this.updateDom(1000); // or whatever transition time u want. }, to fix it you need an arrow function to keep context right see https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Functions/Arrow_functions but net showSlides2: function () { if (!this.slideIndex) { this.slideIndex = 0; } var i; var slides = document.getElementsByClassName("mySlides"); for (i = 0; i < slides.length; i++) { console.log(slides[i]); slides[i].style.display = "none"; } this.slideIndex++; slides[this.slideIndex - 1].style.display = "block"; if (this.slideIndex > (slides.length - 1)) { this.slideIndex = 0 } setInterval( () => { this.showSlides2()} , 2000); // < --- was a typo here.. need () => { stuff } this.updateDom(1000); // or whatever transition time u want. },

I am having a problem trying to use any of the APIs that are listed for the MMM-RemoteControl module. I have installed the module and added a config with showModuleApiMenu: true. I can access http://host:port/remote.html and things work from there. In my case monitor on/off. I am trying to use the API to turn the monitor on/off and none of the APIs seem to work. Even using the example from https://github.com/Jopyth/MMM-Remote-Control/blob/master/API/README.md it shows: curl -X GET http://magicmirrorip:8080/api/monitor/off When I run this I get an error that says “Cannot GET /api/monitor/off” It does not matter what command I try to run they all fail with a similar message. Any ideas what I am missing?

@Ultimatum22 hey there went to do the most current update and ran into the same issue with the vendor/package-lock.json package so I ran the removal script as stated below and it worked and now my pi is updated… I remember you brought up that I should have that package in a gitignore file how do I move it over?

@seramik thanks but as said I already have a method of turning to TV off I just wanted the hdmi to stay live, as said it’s the mmm-voice that was the issue/cause

@emrhssla also, on the module side, logging is Log.log() instead of console.log() then u open the developers window, and select the console tab… currently there is no mechanism to show both parts of a module in the same place node_helper = console.log() - shows in terminal window module.js = Log.log() - shows in developers window, console tab

@sdetweil thank U!!

Doesn’t help much, but mine is still OK.

after installing the update, and doing npm install in the MagicMirror folder, you need to do npm install in each module folder if it contains a package.json file… for some, like hotword, u need to look at its install instructions, as there is a multi-step process to use to resolve this error…

@Sean I checked again, you are right, polling is the only option. Thanks for your cool module!

Hello, I have a problem with my two MMs. Both runs independently. For both MMs, the monitor always turns off at the same time (MM one every day at about 8 a.m., MM two every day at about 21:30 p.m.) and stays off until the PI is restarted. The monitor one turns off after about 3 hours after reboot, the other after about 16 hours after reboot. For both PIs I installed the XScreensaver and deactivated the screensaver. Monitor one has an installed PIR sensor but the other one does not. When I connect via VNC, I can see the MM display. But not at the monitor. I have unfortunately no idea, why the monitor turns off. I would really appreciate if anyone have a good advice for me. Thanks in advance. Lars

@toastybot there are modules that support Amazon Alexa and Google Assistant voice interactions MMM-Alexa And MMM-AssistantMk2 There may be others. I have used both of these, with MMM-Hotword in front

Hello! I know there are many articles addressing this already, but I haven’t found one to work yet so hoping someone can shed new light. MM 2.7.0 on an RaspberryPi Zero W and chromium MM was working after initial setup, I was tweaking modules just to get my initial layout all set (occasionally getting the “please use a config.js” message, fixing my js then it worked again… So now the issue: Twice now after pm2 restart mmrestart from just changing config.js I get the browser page that the Site can't be reached... localhost refused to connect 1st time it happened I started going back through the whole setup again doing npm install, etc and nothing worked. I was just about to burn the whole thing down when… Finally after one more sudo reboot after no changes… it just worked. This time, it’s not coming back yet. tail -n 50 ~/.pm2/logs/mmstart-out.log: wm_set_cursor_visibility: visible using XCreateFontCursor Starting MagicMirror: v2.7.1 Loading config ... Loading module helpers ... No helper found for module: alert. Initializing new module helper ... Module helper loaded: updatenotification No helper found for module: clock. Initializing new module helper ... Module helper loaded: MMM-CalendarExt Loading module helpers ... No helper found for module: alert. Initializing new module helper ... Module helper loaded: updatenotification No helper found for module: clock. Initializing new module helper ... Module helper loaded: MMM-CalendarExt Whoops! There was an uncaught exception... 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 wm_set_cursor_visibility: visible using XCreateFontCursor Starting MagicMirror: v2.7.1 Loading config ... Loading module helpers ... No helper found for module: alert. Initializing new module helper ... Module helper loaded: updatenotification No helper found for module: clock. Initializing new module helper ... Module helper loaded: MMM-CalendarExt Loading module helpers ... No helper found for module: alert. Initializing new module helper ... Module helper loaded: updatenotification No helper found for module: clock. Initializing new module helper ... Module helper loaded: MMM-CalendarExt Whoops! There was an uncaught exception... 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 nmap -A -T4 localhost: Starting Nmap 7.40 ( https://nmap.org ) at 2019-04-24 06:55 EDT Nmap scan report for localhost (127.0.0.1) Host is up (0.0021s latency). Other addresses for localhost (not scanned): ::1 Not shown: 998 closed ports PORT STATE SERVICE VERSION 22/tcp open ssh (protocol 2.0) | fingerprint-strings: | NULL: |_ SSH-2.0-OpenSSH_7.4p1 Raspbian-10+deb9u4 | ssh-hostkey: | 2048 66:12:9f:31:9f:17:1c:07:1e:f4:73:e5:66:95:ea:1a (RSA) |_ 256 17:08:1d:39:a9:ff:3f:1d:5a:66:c7:2a:e6:36:78:5f (ECDSA) 111/tcp open rpcbind 2-4 (RPC #100000) | rpcinfo: | program version port/proto service | 100000 2,3,4 111/tcp rpcbind |_ 100000 2,3,4 111/udp rpcbind 1 service unrecognized despite returning data. If you know the service/version, please submit the following fingerprint at https://nmap.org/cgi-bin/submit.cgi?new-service : SF-Port22-TCP:V=7.40%I=7%D=4/24%Time=5CC040A8%P=arm-unknown-linux-gnueabih SF:f%r(NULL,29,"SSH-2\.0-OpenSSH_7\.4p1\x20Raspbian-10\+deb9u4\n"); Service detection performed. Please report any incorrect results at https://nmap.org/submit/ . Nmap done: 1 IP address (1 host up) scanned in 23.12 seconds /etc/hosts/: 127.0.0.1 localhost ::1 localhost ip6-localhost ip6-loopback ff02::1 ip6-allnodes ff02::2 ip6-allrouters 127.0.1.1 juddpi sudo iptables -L --verbose: Chain INPUT (policy ACCEPT 0 packets, 0 bytes) pkts bytes target prot opt in out source destination Chain FORWARD (policy ACCEPT 0 packets, 0 bytes) pkts bytes target prot opt in out source destination Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes) pkts bytes target prot opt in out source destination Any help is greatly appreciated. Thanks, all!

@Julia Same here …been working on it for a year…other people have gotten it to work though i can’t for some reason :( … look some pages back from the last one here https://forum.magicmirror.builders/topic/8569/mmm-mirrormirroronthewall-installation-issue/131?page=14

@dxfan227 that shouldn’t matter. The message the OP posted comes from server.js after checking the ipWhitelist config variable