MMM-Pir

gonzonia

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

gonzonia

@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

gonzonia

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

htilburgs

@gonzonia
Ok 👍 succes.

gonzonia

Okay, sorry to revive this. I saw there was an update available so I went to update.

I did a git pull and got this

hint: Pulling without specifying how to reconcile divergent branches is
hint: discouraged. You can squelch this message by running one of the following
hint: commands sometime before your next pull:
hint: 
hint:   git config pull.rebase false  # merge (the default strategy)
hint:   git config pull.rebase true   # rebase
hint:   git config pull.ff only       # fast-forward only
hint: 
hint: You can replace "git config" with "git config --global" to set a default
hint: preference for all repositories. You can also pass --rebase, --no-rebase,
hint: or --ff-only on the command line to override the configured default per
hint: invocation.
From https://github.com/bugsounet/MMM-Pir
   3a5bcdb..1fee537  master     -> origin/master
   fc5b3f6..658a322  dev        -> origin/dev
Updating 3a5bcdb..1fee537
error: Your local changes to the following files would be overwritten by merge:
	MMM-Pir.js
	components/cronJob.js
	components/governorLib.js
	components/motion.js
	components/motionLib.js
	components/pirLib.js
	components/screenDisplayer.js
	components/screenLib.js
	components/screenTouch.js
	node_helper.js
Please commit your changes or stash them before you merge.
Aborting

The thing is, I know I have made NO CHANGES to any of those files.
Should I run a pull.rebase? Would that fix it ?

gonzonia

I just did a reinstall for now, but I would like to know what I should do to fix this in the future

sdetweil

@gonzonia the question is what did you do before

Sounds like you might have downloaded the zip over the files in the working directory, or copied files from somewhere else

In general, the force way to get back to the repo level
is

git reset --hard HEAD

This will restore all the files to the last commit level.
IF you made changes for some reason , they will be wiped out, no warnings.

git status before git pull will tell you if there are any changed files,
and git diff will show you the changes

bugsounet

Readme says:

see there

gonzonia

@bugsounet and that’s what I did wrong! thank you!

sdetweil

@bugsounet you should make it normal, like the rest of the modules…

gonzonia

@sdetweil This is helpful, thank you. I guarantee I made no changes though. I think it’s just that it needs to use npm run update