I had the same issue. Tried Chromium instead Midori, where it works fine.

@cruunnerr it worked… why didnt i think of this haha thanks! it was bothering me for weeks

I went ahead and did the PIR sensor. After a few frustrating days I got it working- very cool. Thank you for the suggestion. I’ve also commented out the update notifications- thank you for pointing out the setup tutorial, there were a few other things on there I’ve missed. Thanks for the help, Tom

@olha wrong screenshot? Or very brash advertisement?

@TS77UK said in MMM-PIR-Sensor wont do anything: echo “4” > /sys/class/gpio/export Ignore that! I was looking at the wrong pin map for my model Pi! I should have been in number 4 not 7! As soon as I typed it I realised the answer lol Thank you for your time

@zeal I have not. By default, the compliments module looks for the compliments.json file in the compliments module folder. I suppose you could try using the path to the file on your server in your config entry remoteFile: "PATH_TO_FILE_ON_SERVER/comliments.json", Dunno if that will work though.

i am wondering why u use MM 2.2.1. The actual release is 2.2.2 i think. Anyhow… Try starting in development mode and take a look at errors: npm start dev or via ssh: DISPLAY=:0 npm start dev

Try Xcode ;) In cyberduck do a right click and say “edit with --> Xcode” For ssh i use “terminus”

I do npm start, it looks like that the app started, but the screen just stays black

@ninjabreadman No i realy happy i got it working thanks everyone for all the help Alot of great support gong on in the forms Big Thumbs up to you all Thanks

appreciate all the help here guys, going to try a few of these options out this afternoon Cheers

@dnzio You start the shell/terminal/bash either directly on the pi, via ssh (putty for example) or via vnc and either type or copy paste the command Then you press enter

I am glad u found out what causes your problem :D Yeah, the RPi is very limited in processor power. That is the reason, why some users went over to old laptops or small x86 solutions :)

So, as in this thread I am trying to use a PIR sensor that powers off my screen via a relay. I’ve had no luck so far. The module MMM-PIR-sensor works nicely as it should, as long as I don’t use relayPIN in the config.js. I also tried doing that via external python scripts, but somehow the relay doesn’t get triggered. Well, it clicks extactly once and that’s it. Has anyone managed to use a PIR sensor with a relay on a Raspberry Pi 3 B? If so, how did you do that? Edit: Btw, gpio -g write 27 0 or gpio -g write 27 1 do absoloutly nothing. Wiringpi v 2.44 is installed.

@dexterbeng I would guess 15-30 seconds. pm2 has to detect that the process has terminated and restart. It depends on the polling interval for pm2 (which, as far as I can tell from their docs/issues, is 100ms, and cannot be changed – seems more frequent than I expected). Why are you killing mm with Ctrl+Q? Better to use pm2 restart mm or even pm2 start mm --watch which will also restart mm after file system changes (you may need to configure which directories to watch).

@Areeba Rotating the screen requires that you edit the /boot/config.txt file. You simply need to add the following line to that file and save. display_rotate=1 Reboot.

@MrRodz If you install MMM-Remote-Control and correctly configure the ipWhiteList, it will install a generic receiver to receive commands to your MM via a local HTTP GET request. You can then use an HTTP GET request like http://192.168.178.240:8080/remote?action=SHOW&module=module_0_MMM-GoogleMapsTraffic to trigger a module/action, switch profiles, or create your own custom actions. I’m terms of GPIO for your doorbell, see MMM-Buttons or MMM-PIR-Sensor. It seems to me you want to receive a GPIO event, switch profiles, and start a timer to later revert your profile to the original – that’s basically MMM-PIR-Sensor (movement, turn on screen, set timer to turn off).

I can confirm that address: "localhost" does not allow access from LAN. That is specifying the interface. So it need to be an interface facing your ethernet/wlan, i.e. “0.0.0.0” (any iface).