MMM-PIR-Sensor - White Screen

[bhepler]

@Them-Russians

When i ran the “npm install” in the MM directory, i got this error:
npm warn grunt-yamllint@0.2.0 requires a peer of grunt@~0.4.0 but none was installed

Don’t worry about this one. The log file format is [process] [debug level] [error message]. In this case, “warn” is the level of severity of the message. If it said “err” then it would require your attention.

I suspect your nodejs version is out of date. Try running this command: nodejs -v and then npm -v. It should spit out the version of node and NPM you’re using. Personally, I’m on v7.4.0 and v4.0.5 respectively. If you’re running a few versions behind, you may wish to run these commands from your home folder:

curl -sL https://deb.nodesource.com/setup_7x | sudo -E bash -
sudo apt-get install -y nodejs
sudo npm install -g npm
sudo npm install -g npm

And yes, you may have to run that last command twice. For some reason, NPM sometimes requires a double-tap to update itself. Thank you, StackExchange.

Run nodejs -v again and verify that your node version is up to snuff.

[Them Russians]

@bhepler

Hey there, thank you for the suggestion. updated both nodejs and npm to 7.4.0 and 4.0.5.

I think removed the MMM-PIR-Sensor folder, grabbed it again from github, and then tried to run npm install on it, and the install failed again.

An unhandled error occurred inside electron-rebuild
Unable to find electron-prebuilt’s version number, either install it or specify an explicit version
Error: Unable to find electron-prebuilt’s version number, either install it or specify an explicit version
at _callee$ (/home/pi/MagicMirror/modules/MMM-PIR-Sensor/node_modules/electron-rebuild/lib/cli.js:74:17)
at tryCatch (/home/pi/MagicMirror/modules/MMM-PIR-Sensor/node_modules/babel-runtime/node_modules/regenerator-runtime/runtime.js:63:40)
at Generator.invoke [as _invoke] (/home/pi/MagicMirror/modules/MMM-PIR-Sensor/node_modules/babel-runtime/node_modules/regenerator-runtime/runtime.js:337:22)
at Generator.prototype.(anonymous function) [as next] (/home/pi/MagicMirror/modules/MMM-PIR-Sensor/node_modules/babel-runtime/node_modules/regenerator-runtime/runtime.js:96:21)
at Generator.tryCatcher (/home/pi/MagicMirror/modules/MMM-PIR-Sensor/node_modules/bluebird/js/release/util.js:16:23)
at PromiseSpawn._promiseFulfilled (/home/pi/MagicMirror/modules/MMM-PIR-Sensor/node_modules/bluebird/js/release/generators.js:97:49)
at /home/pi/MagicMirror/modules/MMM-PIR-Sensor/node_modules/bluebird/js/release/generators.js:201:15
at Object. (/home/pi/MagicMirror/modules/MMM-PIR-Sensor/node_modules/electron-rebuild/lib/cli.js:197:4)
at Module._compile (module.js:571:32)
at Object.Module._extensions…js (module.js:580:10)
at Module.load (module.js:488:32)
at tryModuleLoad (module.js:447:12)
at Function.Module._load (module.js:439:3)
at Module.runMain (module.js:605:10)
at run (bootstrap_node.js:420:7)
at startup (bootstrap_node.js:139:9)

I tried running the rebuild with my electron version number (1.5.7) but still no luck. Any thoughts on what else I could try? I am drawing a blank here, unfortunately.

[ostfilinchen]

@Them-Russians i also thought i have a higher electron-version. but i tried

npm rebuild --runtime=electron --target=1.4.3 --disturl=https://atom.io/download/atom-shell --abi=50

and it worked for me.

[bungee09]

@Them-Russians I think you definitely need to rebuild electron. I can’t see what else is causing the issue. Try with different electron version numbers. Otherwise I’m all out of ideas. Sorry!

[Jopyth]

@Them-Russians Try changing line 24 in package.json as shown here and reinstall with npm install in the module folder. Does that help?

Also: Please continue discussion about install issues here. There is already info on how it can be solved. For other problems with the PIR-Sensor Module please open a new thread in the modeul troubleshooting section.

[djbosman]

@Bangee

Thanx a Million, Bro’ !!

The step-by-step did it for me!

I couldn’t understand that everybody’s was working so cool and mine dis diddly-squat?!?

So removing the module and reinstalling was the answer. No idea what went wrong first time round; Just grateful it is now working as expected.

Thanx for your great post!!

[Bangee]

I’m glad to hear that! :-D

[Coda]

@Medo Solved it for me, thanks!

[MobbareKurtZ]

This post is deleted!