after reboot i can’t start MagicMirror. The Log show me:

/home/pi/.pm2/logs/MagicMirror-error-0.log last 15 lines: 0|MagicMir | internal/modules/cjs/loader.js:550 0|MagicMir | throw err; 0|MagicMir | ^ 0|MagicMir | 0|MagicMir | Error: Cannot find module 'proto-list' 0|MagicMir | at Function.Module._resolveFilename (internal/modules/cjs/loade r.js:548:15) 0|MagicMir | at Function.Module._load (internal/modules/cjs/loader.js:475:25 ) 0|MagicMir | at Module.require (internal/modules/cjs/loader.js:598:17) 0|MagicMir | at require (internal/modules/cjs/helpers.js:11:18) 0|MagicMir | at Object.<anonymous> (/usr/lib/node_modules/npm/node_modules/c onfig-chain/index.js:1:79) 0|MagicMir | at Module._compile (internal/modules/cjs/loader.js:654:30) 0|MagicMir | at Object.Module._extensions..js (internal/modules/cjs/loader.j s:665:10) 0|MagicMir | at Module.load (internal/modules/cjs/loader.js:566:32) 0|MagicMir | at tryModuleLoad (internal/modules/cjs/loader.js:506:12) 0|MagicMir | at Function.Module._load (internal/modules/cjs/loader.js:498:3)

np had the same problem and figured I could solve it that way ;)

Hi everyone,

I’m doing a module (display data from Habitica ) .

I got the following errors but not at every update. I happened like about 1 time every 5 min (i haven’t seen any regular pattern, it can happen several time in 1 minute and nothing for 10 minutes). And the error can be one of the 3 following :

Error: read ECONNRESET (or Error: read ETIMEDOUT) at TLSWrap.onread UnhandledPromiseRejectionWarning: TypeError: Cannot read property ‘hash’ of null Error: getaddrinfo ENOTFOUND habitica.com

This is what i have coded :

MMM-Habitica.js : updateHabitica => sendSocketNotification(myConfig) node_helper.js : reload() => forEach (members in config.members) => send https request ; on requestResult.end => sendSocketNotification(returnData) MMM-Habitica.js : socketNotificationReceived => gather data and construct dom object

Does anybody has a clue about what could go wrong? (https request with forEach, wrong data from api, other? )

Any help would be greatly welcome

Guillaume

**UPDATE : ** :man_dancing_light_skin_tone:
It seems enclosing the https request in a promise resolve the issue no error so far

return new Promise((resolve, reject) => { var req = https.request(requestOptions, (res) => { res.setEncoding('utf8'); res.on('data', (chunk) => { try{ JSONParsed = JSON.parse(chunk); }catch(error) { } }); res.on('end', () => { self.sendSocketNotification(reloadType, JSONParsed); }); req.on('error', (e) => { console.log(`problem with request: ${e.message}`); }); }); req.end(); })

I just released a new master release. So this should be fixed. :)

@chinnu_2012 You shouldn’t need to enter your credentials when cloning the repository.

Please try: git clone git@github.com:MichMich/MagicMirror.git

Hi
I’m having a problem with a memory leak (or at least my MM keeps eating up memory). I found that this could possible be caused by the clock module when using analog mode.

I’ve tested two scenarios with only the clock module activated; one with digital and one with analoge. => Digital is stable while analoge keeps eating memory.

I’ve attempted a few possible solutions but I’m not a good enough javascript programmer.

Possible cause:
This code keeps loading the face-00n.svg every second, could that be a cause?

if (this.config.analogFace != "" && this.config.analogFace != "simple" && this.config.analogFace != "none") { clockCircle.style.background = "url("+ this.data.path + "faces/" + this.config.analogFace + ".svg)"; clockCircle.style.backgroundSize = "100%";

Other possible cause could be the beginning of the getDom elements for digital clock is created. These elements are never appended to the dom when used in analog style.

Anyone else seen this?
Any other ideas for the problem and solution??

/Fredrik

I just tried to run serveronly mode and get this error.

pi@raspberrypi:~/MagicMirror $ node serveronly /home/pi/MagicMirror/node_modules/escape-html/index.js:14 Var ma�chHtmlRegExp = /[#'&<>]/; ^^ SyntaxError: Unexpected identifier at new Script (vm.js:51:7) at createScript (vm.js:136:10) at Object.runInThisContext (vm.js:197:10) at Module._compile (internal/modules/cjs/loader.js:618:28) at Object.Module._extensions..js (internal/modules/cjs/loader.js:665:10) at Module.load (internal/modules/cjs/loader.js:566:32) at tryModuleLoad (internal/modules/cjs/loader.js:506:12) at Function.Module._load (internal/modules/cjs/loader.js:498:3) at Module.require (internal/modules/cjs/loader.js:598:17) at require (internal/modules/cjs/helpers.js:11:18)

hello

i installboth of MMM-GA and MMM-voice but when i run the MMM-GA igot error undefined on MMM-voice and its veeery lazy to recognize my speach i didnt know why !? do you know ? and then when i say ok google and ask , it is silent at first but when i say ok google again it wants talk but cut the first one ! so how ?

@ryanvox

https://forum.magicmirror.builders/topic/6878/changing-units-from-metric-to-imperial-breaks-currentweather-module/3

Thank you ninjjabreadman !

Exactly what I need !

.module.MMM-MyCalendar { max-width: 300px; }

I have a wifi watchdog installed because my wifi connection sometimes breaks off.
It automatically turn the wifi controller off and on again, when the pi can’t ping my router. Maybe u should check this out:

http://alexba.in/blog/2015/01/14/automatically-reconnecting-wifi-on-a-raspberrypi/

I just replaced the used IP Adresse from this Tutorial with my routers IP adress.

Brainstorming again. Maybe your Pi doesnt have enough power for the wifi controller when u turn on your alexa, magicmirror and such other stuff.
So it cannot hold the connection with the -71db. Maybe a repeater would help, so with e.g. -49db the wifi Controller doesnt need too much power

Platform: Raspberry Pi Zero W, Linux pi 4.9.59+ #1047 Sun Oct 29 11:47:10 GMT 2017 armv6l GNU/Linux

Node Version: v.4.2.1

MagicMirror Version: Latest (2018-01-01)

array.

Steps to Reproduce: explained in description.

Expected Results: I expected not to see evening compliment as code says that it’s evening after 17:00.

Actual Results: explained in description.

Configuration:

{ module: "compliments", position: "bottom_bar", config: { updateInterval: 12000, compliments: { anytime: [ "anytime text" ], rain: [ "rain text" ], morning: [ "morning test" ], evening: ["evening test"] } } },

Additional info: I don’t know if it was the same before the update. Also, “date” in terminal returns afternoon time too.

How to debug this? How to find out what number is behind “hour” variable at that moment?

@henrikra The mirror application itself doesn’t connect to the internet. It uses your existing network connections as configured in the Raspbian operating system. The Raspbian installation already contains auto-reconnect out of the box. (this arrangement means that you can use a wireless connection, an ethernet connection or a bluetooth connection and the mirror will grab whatever is at hand).

The failure to connect to GitHub is most likely the Update module checking to see if the Magic Mirror application has been updated. It’s what pops up the “An update to XXX is available!” notification.

I don’t know how flaky your internet connection is, but it definitely seems like something you will have to account for in your coding. The update module seems to gracefully handle it and try again when the connection has been restored. Perhaps you can look to it for ideas.

In the meantime, I would suggest an sudo apt-get update & sudo apt-get upgrade to make sure that you have any improvements to the networking of your Raspbian installation.

Hey ho!
If I try to play an embedded video in the forum and hit the full-screen button, the video disappears and the site jumps to the first post.

Google Chrome under win10 and Android 7

@jasondreher said in [SOLVED] Dates lower than Thu Jan 01 1970 00:00:00 GMT+0100 (CET) are not supported:

You need to edit the /home/pi/MagicMirror/node_modules/rrule-alt/lib/rrule.js file. See the post below.

Excellent!

@j.e.f.f That could be, I wonder if when Electron starts it somehow removes any SIGINT listeners already created.

With respect to running stop() during a MM crash – the main function in js/app.js is still attaching to process.on("SIGINT", ...) just upstream of the individual node_helper files. If MM crashes I think it should still call the stop() functions unless the node_helper array gets corrupted. An advantage to cycling through each node_helper would be that you don’t have multiple individual SIGINT listeners that are trying to call a process.exit before the other is done.

Thanks @Sean. Of course the problem relates to the this reference, which changes depending on the scope where it’s referenced. Thanks for pointing that out!