Gals/Guys,

I don’t know if anyone else has been experiencing the same weird things that seem to be happening to a couple of my modules.
In 2 modules, that used to work with no issue, they stopped updating. I checked them and one used setTimeout() while the other used setInterval() to refresh the data. These modules have been working for some time and all of a sudden they stopped. I reset my pi to see if that’d help, no luck. I apt-get update and rpi-update to see if that’d help. Didn’t help my issue. I’m running the latest non-develop build of MM.
I tried some troubleshooting by using setInterval() with a 5 minute delay.
I just had one of the faulty modules in my config.js so nothing else would mess with it.
I had a counter that updated every time the function was supposed to run. It ran the first time, and never again. So I switched to setTimeout() with the same delay and counter. It runs 5-270 times randomly(random to me at least).
I have a bunch of console.log()'s in my code to see if any part fails. Those never get triggered.

So in summary, 2 of my 10 or so modules have started acting erratically with their timing events. SetInterval() stopped working for me all together, and setTimeout() stops updating at random times. The other modules I use all update fine with setTimeout().

If anyone has seen this before and knows how to fix it, I’d be greatly appreciative. Thanks!

P.S. I see the same freezes using MagicMirror’s built in browser as well as Chrome and Firefox from a separate computer.

Thomas,

I haven’t developed it since I first made it so I’m not sure if it still works with all the updates the pi & MM have gotten. Sorry.

If you want to still try and get it to work, yes you do need 2 sensors to detect movement between them. You also need to run the MagicMirror with sudo to allow permissions to the GPIO pins in MagicMirror.

@AAPS If /24 is working for you then stick with it. The /120 just allows less IPs the ability to access your mirror.

If you aren’t forwarding your pi’s ports outside your local network it really shouldn’t matter.

@JbeesonMagic16 Yeah, @in_a_days recommendation fixes the problems in the jshint. Hopefully that works for you.

@JbeesonMagic16 No, it’s a general javascript problem finder. If you paste your config.js file in it’s entirety into http://jshint.com/. You should see it say “One undefined variable”. If you see

Expected '}' to match '{' from line XXX and instead saw ']'

You are missing a bracket. Look at line XXX and then follow the code down to see where the missing bracket is.

Try putting your config.js in a website like http://jshint.com/. It should help you find any brackets you might be missing.

@fox I don’t have a camera so I’m not too sure how to program for it. The API does allow you to get data from the camera as well as take snapshots. The API also gives you the video URL which I imagine you can use to get video on the mirror.

@Snille Yeah, this module requires root access. I haven’t developed it since I first made it so I’m not sure if it still works with all the updates the pi & MM have gotten. Sorry.

I’m not sure about MMM-Alexa, but MMM-AlexaPi needs AlexaPi installed and configured correctly to work.

You should just need to put

var row = document.createElement("tr");
var header = document.createElement("th");
var header2 = document.createElement("th");
header.innerHTML = "Load";
row.appendChild(header);
header2.innerHTML = "KWh";
row.appendChild(header2);
table.appendChild(row);

before

var channels = this.xml.getElementsByTagName("channel");

You can add a title by modifying your config.js file to add a header.
The documentation for that is here.