@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

@sdetweil
Same thing. I feel like this line is the issue ----“Selecting previously unselected package nodejs.” How can I clear wherever it’s finding that?

(I also tried the uninstall from your repo and install, same thing)

pi@MagicMirror2:~ $ bash -c  "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/node20_install.sh)"
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libc-ares2 libjs-highlight.js libnode72 nodejs-doc
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
  nodejs*
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 919 kB disk space will be freed.
(Reading database ... 107017 files and directories currently installed.)
Removing nodejs (12.22.12~dfsg-1~deb11u4) ...
Processing triggers for man-db (2.9.4-2) ...
Hit:1 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
Hit:2 http://archive.raspberrypi.org/debian bullseye InRelease
Reading package lists... Done
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
ca-certificates is already the newest version (20210119).
curl is already the newest version (7.74.0-1.3+deb11u7).
gnupg is already the newest version (2.2.27-2+deb11u2).
The following packages were automatically installed and are no longer required:
  libc-ares2 libjs-highlight.js libnode72 nodejs-doc
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
deb [arch=arm64 signed-by=/etc/apt/keyrings/nodesource.gpg] https://deb.nodesource.com/node_20.x nodistro main
Get:1 https://deb.nodesource.com/node_20.x nodistro InRelease [12.1 kB]
Hit:2 http://archive.raspberrypi.org/debian bullseye InRelease                   
Hit:3 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
Get:4 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages [3,264 B]
Fetched 15.4 kB in 1s (16.3 kB/s)
Reading package lists... Done
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Suggested packages:
  npm
The following NEW packages will be installed:
  nodejs
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/148 kB of archives.
After this operation, 919 kB of additional disk space will be used.
Selecting previously unselected package nodejs.
(Reading database ... 106955 files and directories currently installed.)
Preparing to unpack .../nodejs_12.22.12~dfsg-1~deb11u4_armhf.deb ...
Unpacking nodejs (12.22.12~dfsg-1~deb11u4) ...
Setting up nodejs (12.22.12~dfsg-1~deb11u4) ...
update-alternatives: using /usr/bin/nodejs to provide /usr/bin/js (js) in auto mode
Processing triggers for man-db (2.9.4-2) ...

@sdetweil

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

@sdetweil

After an uninstall it says npm isn’t installed. I tried the install again and it’s still installing 12.22.12

I did the backup. I’m just going to rebuild. It’s annoying but it should work. :crossed_fingers_light_skin_tone:

@sdetweil Thanks. When I ran into issues last update I ended up building it up from scratch again. There were some benefits to that and I have a pretty clean install now. I can do it again but would prefer to not have to.