I think I had the GPIO correct originally. Went back to that and it’s working.

@htilburgs yes. I was using mode 9 in the old version. When I looked it up I thought that’s what corresponded. Im on Pi OS 11 and Wayland is for 12 according to the read me

@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
				}
			}
		},

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

@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,
	  }

@sdetweil said in MMM-Pir:

nvm install v20.9.0

That did it!

As always, THANK YOU!

@sdetweil said in MMM-Pir:

sudo nvm i 20

sudo nvm i 20
sudo: nvm: command not found

@sdetweil

$ nvm -v
0.39.7

@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

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

@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 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 Thanks!

I was trying to update MMM-Pir and having some trouble so I decided, I’d rename the directory and start with a fresh install. I cloned the directory and followed the instructions with “npm run setup”. Apparently my node version is too high.

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.8.3”,“node”:“v21.7.1”}

Can I not use MMM-Pir now?

I’ve been using MMM-CalendarExt3 for a while now and all is good. Suddenly I’ve got a single event that’s an hour off. The events for the rest of the day are fine, and the time is correct on all other methods (Google Calendar, BusyCal, iOS Calendar).

@XDmToter
There’s a way to get an iCal URL without making it public. I see this in my “Settings and Sharing” section of Google Calendar.

@sdetweil

I’m just going to rebuild. I’ll let you know if I hit any snags. Thanks again.

@sdetweil

pi@MagicMirror2:~ $ ls /etc/apt/sources.list.d
nodesource.list  raspi.list
pi@MagicMirror2:~ $ sudo cat /etc/apt/sources.list.d/nodesource.list
deb [arch=arm64 Pin-Priority=600 signed-by=/etc/apt/keyrings/nodesource.gpg] https://deb.nodesource.com/node_20.x nodistro main
pi@MagicMirror2:~ $ sudo cat /etc/apt/sources.list.d/raspi.list
deb http://archive.raspberrypi.org/debian/ bullseye main
# Uncomment line below then 'apt-get update' to enable 'apt-get source'
#deb-src http://archive.raspberrypi.org/debian/ bullseye main

@sdetweil

Thanks for trying. I appreciate all the support you provide the MM community.

pi@MagicMirror2:~ $ sudo apt-get update
sudo apt-get install nodejs -y
Hit:1 https://deb.nodesource.com/node_20.x nodistro InRelease
Hit:2 http://archive.raspberrypi.org/debian bullseye InRelease
Hit:3 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
Reading package lists... Done
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
nodejs is already the newest version (12.22.12~dfsg-1~deb11u4).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
pi@MagicMirror2:~ $ 

@sdetweil

pi@MagicMirror2:~ $ sudo cat  /etc/apt/sources.list.d/nodesource.list
deb [arch=arm64 Pin-Priority=600 signed-by=/etc/apt/keyrings/nodesource.gpg] https://deb.nodesource.com/node_20.x nodistro main