console.Log() shows nothing?

izanbard

@mortenbirkelund just a note if you put a console.log() in the node_helper, then it apears on the command line output (or PM2 out.log if you are using PM2)

mortenbirkelund

Thank you once again for your help. Now that I understand where to see the logs, i can see that my button is not working. Anybody who knows why nothing happens when I click the button

Module.register("MMM-Slider",{

	// Default module config.
	defaults: {
		//text: "Hello World!"

	},

	// Override dom generator.
	getDom: function() {
		var wrapper = document.createElement("div");
		
		wrapper.appendChild(this.createButton());
		return wrapper;
	},
	
	createButton: function() {
		var button = document.createElement("span");
		button.innerHTML ="Click me";
		button.id = this.identifier + "_button";
		
		button.addEventListener("click", function () {
			console.log("The button was clicked");
		});

		return button;
	}
	
});

mortenbirkelund

@Snille I have looked at your button module for inspiration. Do you know why nothing happens when I click the button?

mortenbirkelund

Found the error. I needed to add

.region.fullscreen {
z-index: -1;
}

as css and now it is working.

Snille

Hmm… I don’t have any custom css om my develop-version of MM, but the problem is of course that you will not see the pointer when moving over to the “mirror” if you are using a mouse.
You can add a custom.css with only:

body {
  cursor: pointer;
 }

then you will see where you “are” when moving the mouse. :)
But you should not need anything else.

hasbean

@mortenbirkelund I know this is really 4 years old, but it was my first match on Google. I couldn’t figure out why logs weren’t printing to terminal.

Anyhow, to make Electron print to terminal, add this to the environment variables:

ELECTRON_ENABLE_LOGGING=1

Hope it helps others!

easty

@hasbean For a complete beginner, how do you do add that statement to environment variables?

sdetweil

@easty in the script that starts mm do

export ELECTRON_ENABLE_LOGGING=1

or do that before u manually type npm start

or use the MMM-Logging module (not mine)

easty

@sdetweil

Getting error EADDRINUSE and MM is blank, though I was trying to debug a module that stopped working yesterday 1st October.

At this point, I will delete and reinstall MM and wait for the module developer to update or move to an alternative. I traced the error back to http data request made by node helper js but haven’t been able to find a way to see the console.log or log.info for it. The http link produces json data correctly.

Edit

Okay this error was to do with the module, I was curious so I deleted the folder for the module and its working again. I can see info logging in terminal.

How can I see info logging for node helper js?

sdetweil

@easty u are using pm2 to launch mm.

so open a terminal window and do

pm2 status
pm2 stop x

where x is the name (MagicMirror if you used my install script})
or the number in the row of output

u don’t have to reinstall

pm2 info x

will tell you how the process is started mm.sh
which is what u would modify

using pm2, u can also see the logs by using the command,
pm2 logs --lines=???
where ??? is a number, 15 by default