MMM-Pir

[gonzonia]

@sdetweil I did that and I still get the same problem. How do I make sure it uses the correct version?

pi@MagicMirror:~/MagicMirror/modules/MMM-Pir $ sudo npm install n -g

added 1 package in 5s
pi@MagicMirror:~/MagicMirror/modules/MMM-Pir $ sudo n 20
     copying : node/20.18.0
   installed : v20.18.0 (with npm 10.8.2)

npm error code EBADENGINE
npm error engine Unsupported engine
npm error engine Not compatible with your version of node/npm: MMM-Pir@2.0.0
npm error notsup Not compatible with your version of node/npm: MMM-Pir@2.0.0
npm error notsup Required: {"node":">=20.9.0 <21 || >=22"}
npm error notsup Actual:   {"npm":"10.9.0","node":"v21.7.1"}

[sdetweil]

@gonzonia said in MMM-Pir:

{“npm”:“10.9.0”,“node”:“v21.7.1”}

you may have to close and open new shell
or do

hash -r

to update the path

[gonzonia]

@sdetweil Okay.
I’ve run

sudo npm install n -g
sudo n 20
hash -r

then closed the terminal and reconnected.
Went back into the MMM-Pir directory and tried running the setup again.
Same problem

[sdetweil]

@gonzonia node -v
returns what?

[gonzonia]

@sdetweil

pi@MagicMirror:~ $ node -v 
v21.7.1

[sdetweil]

@gonzonia weird… how did you upgrade to node 21?
apt or nvm?

[gonzonia]

@sdetweil Honestly, I don’t remember. I think I installed nvm at one point to fix something else but I do run apt regularly to update everything

[sdetweil]

@gonzonia do nvm -v

n and nvm do the same thing
nvm is a bash script
n is a javascript app

[gonzonia]

@sdetweil

$ nvm -v
0.39.7

[sdetweil]

@gonzonia ok, so you have nvm too

sudo nvm i 20

[gonzonia]

@sdetweil said in MMM-Pir:

sudo nvm i 20

sudo nvm i 20
sudo: nvm: command not found

[sdetweil]

@gonzonia ok, been a while

nvm install v20.9.0

[gonzonia]

@sdetweil said in MMM-Pir:

nvm install v20.9.0

That did it!

As always, THANK YOU!

[Peter]

@gonzonia is your Magic Mirror working now with MMM-PIR?
My MM stopped turning on after updating MMM-PIR.
Peter

[gonzonia]

@Peter So it’ll go off but the PIR doesn’t work to turn it back on? Mine is working. Try re-installing. Here’s the config I’m using.

  module: 'MMM-Pir',
		  position: 'top_left',
		  classes: 'SceneFamily SceneSam',
		  config: {
			debug: false,
			delay: 2 * 60 * 1000,
			mode: 9	,
			displayCounter: false,
			displayBar: false,
			displayStyle: "Line",
			displayLastPresence: false,
			lastPresenceTimeFormat: "LL H:mm",
			mode6_gpio: 20,
			mode6_clearGpioValue: true,
			xrandrForceRotation: "left",
			wrandrForceRotation: "normal",
			wrandrForceMode: "1920x1080",
			touchMode: 3,
			pir_gpio: 4,
			pir_mode: 0,
	  }

[Peter]

@gonzonia before installing did you follow all the tips mentioned by sdetweil?
Peter

[bugsounet]

Can you check new ReadMe

I haven’t had time to create a topic for the new release of MMM-Pir v2 yet, sorry

[gonzonia]

@Peter Yes. Because I was getting an error when I tried installing.

[gonzonia]

@bugsounet
I installed v 2 successfully. Everything seemed to be working with my old config (posted above). I tried updating based on the new readme, but now it won’t come back on.

I did have the wrong GPIO originally, but now it should be correct.

{
		  module: 'MMM-Pir',
		  position: 'top_left',
		  classes: 'SceneFamily SceneSam',
		  config: {
			debug: false,
			Display: {
					timeout: 2 * 60 * 1000,
					animate: true,
					style: 0,
					colorFrom: "#FF0000",
					colorTo: "#00FF00",
					mode: 2,
					counter: true,
					lastPresence: false,
					lastPresenceTimeFormat: "LL H:mm",
					availability: false,
					autoDimmer: false,
					xrandrForceRotation: "left"
				},
				Pir: {
					mode: 0,
					gpio: 20
				},
				Cron: {
					ON: [],
					OFF: []
				},
				Touch: {
					mode: 0
				},
				Governor: {
					sleeping: 4,
					working: 2
				},
				Sounds: {
					on: 0,
					off: 0
				}
			}
		},

[htilburgs]

@gonzonia Are you using X11 or Wayland?
Because now you’re using mode 2 and that’s for X11