PIR-Sensor - put your mirror to sleep if not used

paviro

@IngmarSwart Strange that you have this issue, since I do not. I only have the problem when the monitor is disabled via a relay while the Pi boots.
Could you do some more research on why this is happening and maybe find a way to fix it without root rights?

IngmarSwart

@paviro, I also don’t understand where it comes from, especially since the MagicMirror appears as it should immediately after boot. At first glance, the monitor (Philips 273V5L) and Pi seem to play nice: EDID information is correct, tvservice -s gives the native resolution and refresh rate of the monitor. If I can find some time, I will look into it. However, I am also quite earger to start playing with your Facial-Recognition module… :relaxed:

KirAsh4

This is more of a PSA than anything else, but particularly since the tvservice is part of the rPi’s firmware. While running 'sudo apt-get update && sudo apt-get upgrade' will upgrade your rPi’s packages and firmware, it may not be the latest version. For most, this is okay. But if you’re like me, who likes to live on the bleeding edge of things, particularly when something isn’t working right, running 'sudo rpi-update' separately will update the firmware only, including binaries such as 'tvservice' since they’re part of the firmware, not just a standard package (in fact, you can’t find it as a stand alone package through 'apt-cache'.)

Use at your own risk. :)

witschi87

I’m getting the following error:

start-magic-0 (err): WARNING! Could not find config. Please create one.
start-magic-0 (err): App threw an error when running [Error: Module version mismatch. Expected 47, got 48.]
start-magic-0 (err): [Error: Module version mismatch. Expected 47, got 48.]

I’ve just cloned the git repository and installed the dependencies.
And that is my config:

{
	module: 'MMM-PIR-Sensor',
	config: {
		sensorPIN: 22,
		powerSaving: true
	}
},

paviro

Please use Node v5 not v6 one of the dependencies is not yet ready for v6.

witschi87

Can you tell me how to do that, please?!

paviro

First Google result when searching for downgrade node to v5 :)
Also do not forget to execute npm installand if that does not work reinstall the module from GitHub after you downgraded.

KirAsh4

@paviro, but but but … @MichMich said … he said … he said node 6.1.0 is now supported. Dependencies be damned, they need to catch up.

MichMich

@KirAsh4 Yeah, MM supports Node 6.1.0 @paviro apparently still live in the stone age with his modules … 😈

KirAsh4

@MichMich, I have a laser … let’s tie him up and put his hand under the beam. That’ll teach him!