Posts made by philmavedzenge

I had the same issue for some time, it turned out to be the time in between detections was too long. the sensor would detect movement and keep that state until the set time and then checks again. Play around with adjusting one of the orange screws on the sensor until the detection time is very low.

@sdetweil said in MMM-NewPIR v3:

@philmavedzenge it doesn’t upgrade mode/npm

install checks, upgrade does not (usually didn’t need to)

I see now. Thanks a lot for the help

@fozi i had used that script to update, i don’t know why it didn’t update the other components. Thanks a lot for your help

@djboob66 said in MMM-NewPIR v3:

sudo npm install -g npm@6.14.15

thank you guys very much, this worked for me

@djboob66 said in MMM-NewPIR v3:

@philmavedzenge said in MMM-NewPIR v3:

npm WARN notsup Unsupported engine for yargs@17.2.1: wanted: {“node”:“>=12”} (current: {“node”:“10.24.0”,“npm”:“6.13.6”})

You need to update npm and node

Thanks for the response. How do I do that? Which folder should I update it in?

Hi guys,

After updating my MagicMirror to the latest version, this modules does not work. I tried reinstalling but its giving an error that i do not understand. Could someone help please? I have attached the logs, not sure if they will help.

at Module._compile (internal/modules/cjs/loader.js:778:30)

npm WARN notsup Unsupported engine for electron-rebuild@3.2.3: wanted: {“node”:“>=12.13.0”} (current: {“node”:“10.24.0”,“npm”:“6.13.6”})
npm WARN notsup Not compatible with your version of node/npm: electron-rebuild@3.2.3
npm WARN notsup Unsupported engine for @malept/cross-spawn-promise@2.0.0: wanted: {“node”:“>= 12.13.0”} (current: {“node”:“10.24.0”,“npm”:“6.13.6”})
npm WARN notsup Not compatible with your version of node/npm: @malept/cross-spawn-promise@2.0.0
npm WARN notsup Unsupported engine for fs-extra@10.0.0: wanted: {“node”:“>=12”} (current: {“node”:“10.24.0”,“npm”:“6.13.6”})
npm WARN notsup Not compatible with your version of node/npm: fs-extra@10.0.0
npm WARN notsup Unsupported engine for yargs@17.2.1: wanted: {“node”:“>=12”} (current: {“node”:“10.24.0”,“npm”:“6.13.6”})
npm WARN notsup Not compatible with your version of node/npm: yargs@17.2.1

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @bugsounet/pir@1.0.6 postinstall: electron-rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @bugsounet/pir@1.0.6 postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

I have been using this module for the past 3 or so months. Initially I had the same issue. What you need to do is to download the powershell scripts from the module’s GitHub page. Run those and see if you get any data back. I can help you if you experience any issues with this.

You will have to try different end points until you find the correct one for your region. I then changed the locale as described in the above posts and it’s been working since.

I have since changed the module a bit to add more functionality.

I’m having the same issue above as @gonzonia . After some time the module stops changing the images and they become stuck until I refresh the browser. This only started about 2 or so weeks ago.

@philmavedzenge said in MMM-GooglePhotos:

@Sean i really like this module and have been using it for sometime now. I have noticed with the new update that there is a padding of about 10px around the screen. Is there a way of removing that? I use my screen in landscape mode only. Thanks in advance

@Sean nevermind, i fixed it in custom.css

@Sean i really like this module and have been using it for sometime now. I have noticed with the new update that there is a padding of about 10px around the screen. Is there a way of removing that? I use my screen in landscape mode only. Thanks in advance