MMM-PIR-Sensor - White Screen

Bangee

so what will I have to do? I’ve removed the MMM-PIR-Module and reinstalled it, but i’ve got still these error… :-(

strawberry 3.141

@Bangee so after the change of the library you still get Error: Module version mismatch. Expected 49, got 48.?

Bangee

Yes… so I’m quiet pissed off… I think I need to reinstall my MM…

mm-0 Loading config ...
mm-0 Loading module helpers ...
mm-0 No helper found for module: alert.
mm-0 WARNING! Could not load config file. Starting with default configuration. Error found: Error: Module version mismatch. Expected 49, got 48.
mm-0 Loading module helpers ...
mm-0 No helper found for module: alert.
mm-0 App threw an error during load
mm-0 Error: Module version mismatch. Expected 49, got 48.
mm-0     at Error (native)
mm-0     at process.module.(anonymous function) [as dlopen] (ELECTRON_ASAR.js:167:20)
mm-0     at Object.Module._extensions..node (module.js:568:18)
mm-0     at Object.module.(anonymous function) [as .node] (ELECTRON_ASAR.js:167:20)
mm-0     at Module.load (module.js:458:32)
mm-0     at tryModuleLoad (module.js:417:12)
mm-0     at Function.Module._load (module.js:409:3)
mm-0     at Module.require (module.js:468:17)
mm-0     at require (internal/module.js:20:19)
mm-0     at bindings (/home/pi/MagicMirror/modules/MMM-PIR-Sensor/node_modules/bindings/bindings.js:76:44)
mm-0 Whoops! There was an uncaught exception...
mm-0 Error: Module version mismatch. Expected 49, got 48.
mm-0     at Error (native)
mm-0     at process.module.(anonymous function) [as dlopen] (ELECTRON_ASAR.js:167:20)
mm-0     at Object.Module._extensions..node (module.js:568:18)
mm-0     at Object.module.(anonymous function) [as .node] (ELECTRON_ASAR.js:167:20)
mm-0     at Module.load (module.js:458:32)
mm-0     at tryModuleLoad (module.js:417:12)
mm-0     at Function.Module._load (module.js:409:3)
mm-0     at Module.require (module.js:468:17)
mm-0     at require (internal/module.js:20:19)
mm-0     at bindings (/home/pi/MagicMirror/modules/MMM-PIR-Sensor/node_modules/bindings/bindings.js:76:44)
mm-0 MagicMirror will not quit, but it might be a good idea to check why this happened. Maybe no internet connection?
mm-0 If you think this really is an issue, please open an issue on GitHub: https://github.com/MichMich/MagicMirror/issues
mm-0 Launching application.

strawberry 3.141

@Bangee did you change your node version at some point?

Bangee

yes, but this was befor the reinstallation
so now I try npm rebuild

Bangee

atm I am using node 5.12.0

Which node are u using?

EDIT
I’ was wrong… I’ve forgot to activate the module in my configuration…

strawberry 3.141

@Bangee I’m using 6.4.0 but I got no pir sensor

paviro

@Bangee so doesn’t the new version work now?

Bangee

Unfortunatly no… :-(

I’ve tried many differet versions of of node…

McSorley

Still a no go for me.

James

The same issue with me, even after a totally re-installation.
@paviro Could you do us a favor to compatible with and get the module work?
Thank you.

paviro

@James please dont be that demanding! You can always fix it yourself if you need it now. I don’t currently have a mirror so I can’t run it on a real Pi and therefore test it but I will see what I can do on the weekend.

KirAsh4

Folks, please keep in mind that all of us have jobs, some of us are still in school, all of us have a life, all of us have other things to do that is not MagicMirror. I know that @paviro has moved recently and is still settling down into a new place. MagicMirror is probably far lower on the list of things to do at the moment for him. I’ve had a bad life event happen recently and have been absent from everything this past month or so and am just now starting to catch up on things. I’m not ready to jump into anything right away. Some days I’m perfectly fine, other days I’m doubled over crying somewhere, unable to do anything, and this is no joke. And @MichMich, I can’t even imagine all the things he does that we don’t know (and I’m not even talking about his harem.)

Point is, there are several aspects of the code that we are aware of that will need some debugging, fixing, or perhaps simply light on fire and start over. I know that, and I’m sure the other guys know that too. Free time isn’t something that we have in abundance. It comes when it comes, and I try to make use of it when I have it. I can’t speak for the others.

A little patience will go along way. I am certain @paviro will get to coding again when he’s available to do that. And eventually, I too will do the same. For now though, just try to keep the boat floating and stick your fingers into any leak you see springing up …

McSorley

I made an attempt at fixing it but I struggled to find many JavaScript/Node.js tutorials out there. I have however managed to compile a straight forward script in Python that I have set up to run with pm2. A workaround for those who are in high demand for the motion sensor to work and to give paviro some breathing space.

Sorry but I don’t know how to add this as code snippets. If a mod could help me out that that would be great.

Open Python 3. File > New. Paste this code in.

from gpiozero import MotionSensor
import os

pir = MotionSensor(4) #4 is the Pin?
while True:
    if pir.wait_for_motion(timeout=10*60): #10 * 60 Seconds
        os.system("/opt/vc/bin/tvservice -p")
    else:
        os.system("/opt/vc/bin/tvservice -o")

You can if you want edit
os.system("/opt/vc/bin/tvservice -p")
to
print("Motion Detected")
to test if your PIR Sensor is working ok. After changing it, save it and press Ctrl + F5 to run the code. It will then spam up with motion detect or undetected depending on what you’ve changed.

Moderator’s note: You can use backticks (`) to highlight code. Check out the help at http://commonmark.org/help/ - scroll down to see the various options for using backticks.

paviro

Hi there,
I think I fixed the problems now, feel free to give it a try :)

Cheers,
Paul

James

@paviro Solved with run npm rebuild --runtime=electron --target=1.3.4 --disturl=https://atom.io/download/atom-shell --abi=49 in the MMM-PIR-Sensor folder with the latest release or it still shows “White Screen”.

Note from admin: Please use Markdown on code snippets for easier reading!

paviro

@James sure this is because of my plugin? I used the latest and it worked :/

James

@paviro maybe 99% sure. FYI what I did yesterday as follows:

Format & rewrite the sd card,
Boot and run sudo apt-get update & upgrade & reboot,
Install MagicMirror2 with the bash command,
git MMM-PIR-Sensor in modules folder and run npm install in MMM-PIR-Sensor folder as well as useradd command,
Add code in config.js with

                {
                        module: 'MMM-PIR-Sensor',
                        config: {
                               sensorPIN: 4
                        }
                },

After rebooting, run MM with pm2 and shows “White Screen”, I checked the pm2 error log shows something like “Expected 49, got 48” as before,
Run npm rebuild --runtime=electron --target=1.3.4 --disturl=https://atom.io/download/atom-shell --abi=49 in the MMM-PIR-Sensor folder,
Run pm2 restart mm and it works.

I found there is another issue when a rebooting finished and MM runs automaticly with pm2, MMM-PIR-Sensor will not work(screen always on) until the sensor captured a motion.

Bangee

this works for me too. without formatting and reinstallation.
I’ve remove the folder node_modules and startet from 4.

Thanks a lot.

zam

Yes itś working …:)
“After rebooting, run MM with pm2 and shows “White Screen”, I checked the pm2 error log shows something like “Expected 49, got 48” as before,
Run npm rebuild --runtime=electron --target=1.3.4 --disturl=https://atom.io/download/atom-shell --abi=49 in the MMM-PIR-Sensor folder,
Run pm2 restart mm and it works.”

Thanks