Motion Detector

bhepler

I’m still working this problem. To help with @paphko 's concern about processor utilization, I finally figured out how and where to put a delay in the main image comparison loop. @alexyak is using the RequestAnimationFrame feature to run the comparison as fast as the browser can render the UI.

If you wish to include a delay, modify your motion.js file’s main function to read as such:

function main(frequency) {
	render();

	if(rendering == true) {
		setTimeout(function() {
			raf(main.bind(this));
		}, 500);
	}
}

That last number (the 500) is the milliseconds between each image comparison. I think half a second between comparisons is enough to keep the CPU usage down and the effectiveness up.

done

Thx @bhepler
this helped to reduce my temperature from 80 °C to 50-60 °C.
Maybe the 80 °C even caused the wake up problem? :)

Anyway, I think I’ll try the voice activation module tomorrow.
Somehow it’s even very sweet to say “Mirror, Mirror on the wall. Wake up!”.

DirkS

That is the reason why my screen doesn’t switch on after a couple of hrs switched off.
Any idea what the cause of unavailable tvservice is?

Testwise i used the scripts reported here before. They where called if a PIR detects motion or no motion.

Nov  1 08:22:00 MagicMirror kernel: [86411.138649] raspberrypi-firmware soc:firmware: Request 0x00048003 returned status 0x80000001
Nov  1 08:22:00 MagicMirror kernel: [86411.138665] bcm2708_fb soc:fb: Failed to allocate GPU framebuffer (-22)
Nov  1 08:22:00 MagicMirror kernel: [86411.138670] detected fb_set_par error, error code: -22
Nov  1 08:22:00 MagicMirror kernel: [86411.139138] raspberrypi-firmware soc:firmware: Request 0x00048003 returned status 0x80000001
Nov  1 08:22:00 MagicMirror kernel: [86411.139148] bcm2708_fb soc:fb: Failed to allocate GPU framebuffer (-22)
Nov  1 08:22:00 MagicMirror kernel: [86411.139152] detected fb_set_par error, error code: -22
Nov  1 08:22:00 MagicMirror kernel: [86411.140642] raspberrypi-firmware soc:firmware: Request 0x00048003 returned status 0x80000001
Nov  1 08:22:00 MagicMirror kernel: [86411.140654] bcm2708_fb soc:fb: Failed to allocate GPU framebuffer (-22)
Nov  1 08:22:00 MagicMirror kernel: [86411.140659] detected fb_set_par error, error code: -22
Nov  1 08:22:00 MagicMirror kernel: [86411.140777] raspberrypi-firmware soc:firmware: Request 0x00048003 returned status 0x80000001
Nov  1 08:22:00 MagicMirror kernel: [86411.140785] bcm2708_fb soc:fb: Failed to allocate GPU framebuffer (-22)
Nov  1 08:22:00 MagicMirror kernel: [86411.140789] detected fb_set_par error, error code: -22
Nov  1 08:22:00 MagicMirror kernel: [86411.140856] raspberrypi-firmware soc:firmware: Request 0x00048003 returned status 0x80000001
Nov  1 08:22:00 MagicMirror kernel: [86411.140863] bcm2708_fb soc:fb: Failed to allocate GPU framebuffer (-22)
Nov  1 08:22:00 MagicMirror kernel: [86411.140868] bcm2708_fb_pan_display(0,0) returns=-22
Nov  1 08:22:00 MagicMirror systemd[1]: Started Getty on tty6.
Nov  1 08:22:00 MagicMirror kernel: [86411.256398] raspberrypi-firmware soc:firmware: Request 0x00048003 returned status 0x80000001
Nov  1 08:22:00 MagicMirror kernel: [86411.256413] bcm2708_fb soc:fb: Failed to allocate GPU framebuffer (-22)
Nov  1 08:22:00 MagicMirror kernel: [86411.256418] detected fb_set_par error, error code: -22
Nov  1 08:22:00 MagicMirror kernel: [86411.256758] raspberrypi-firmware soc:firmware: Request 0x00048003 returned status 0x80000001
Nov  1 08:22:00 MagicMirror kernel: [86411.256770] bcm2708_fb soc:fb: Failed to allocate GPU framebuffer (-22)
Nov  1 08:22:00 MagicMirror kernel: [86411.256775] bcm2708_fb_pan_display(0,0) returns=-22
Nov  1 08:22:00 MagicMirror kernel: [86411.296428] raspberrypi-firmware soc:firmware: Request 0x00040002 returned status 0x80000001
Nov  1 08:22:00 MagicMirror kernel: [86411.296455] bcm2708_fb soc:fb: bcm2708_fb_blank(0) failed: -22

2016.11.01 08:05:04 2: KuMagicScreen: {system("sudo /opt/fhem/monitor_off.sh &")}: -1
tvservice-client: Failed to connect to TV service: -1
[E] Failed to power off HDMI
Powering off HDMI
2016.11.01 08:05:57 2: KuMagicScreen: {system("sudo /opt/fhem/monitor_on.sh &")}: -1
tvservice-client: Failed to connect to TV service: -1
[E] Failed to set property 4
2016.11.01 08:07:37 2: KuMagicScreen: {system("sudo /opt/fhem/monitor_off.sh &")}: -1
tvservice-client: Failed to connect to TV service: -1
[E] Failed to power off HDMI
Powering off HDMI
2016.11.01 08:09:00 2: KuMagicScreen: {system("sudo /opt/fhem/monitor_on.sh &")}: -1
tvservice-client: Failed to connect to TV service: -1
[E] Failed to set property 4
2016.11.01 08:09:42 2: KuMagicScreen: {system("sudo /opt/fhem/monitor_off.sh &")}: -1
tvservice-client: Failed to connect to TV service: -1
[E] Failed to power off HDMI
Powering off HDMI
2016.11.01 08:09:59 2: KuMagicScreen: {system("sudo /opt/fhem/monitor_on.sh &")}: -1
tvservice-client: Failed to connect to TV service: -1
[E] Failed to set property 4
ping: icmp open socket: Operation not permitted
2016.11.01 08:10:41 2: KuMagicScreen: {system("sudo /opt/fhem/monitor_off.sh &")}: -1
tvservice-client: Failed to connect to TV service: -1
[E] Failed to power off HDMI
Powering off HDMI
ping: icmp open socket: Operation not permitted
2016.11.01 08:21:59 2: KuMagicScreen: {system("sudo /opt/fhem/monitor_on.sh &")}: -1
tvservice-client: Failed to connect to TV service: -1
[E] Failed to set property 4
2016.11.01 08:22:50 2: KuMagicScreen: {system("sudo /opt/fhem/monitor_off.sh &")}: -1
tvservice-client: Failed to connect to TV service: -1
[E] Failed to power off HDMI
Powering off HDMI

DirkS

So here i found a workaround. Maybe it fixes the issue but let’s see. I just modified my test script and need to see it the next hrs/days

https://github.com/raspberrypi/documentation/pull/245/files

https://github.com/raspberrypi/linux/issues/487

DirkS

Hi,

for all the people here I wrote it more cleary :D

i had big problems by switching off my screen with the PIR or another module with camera. The problem was not the module itself it is a firmware problem of the PI. I could see the same problem outside of MagicMirror as well by trying different things.

Reported also here:
https://github.com/raspberrypi/linux/issues/487

The symptom is that after a while of switching on and off the screen it remains off.

Dmesg reports the problem:

Nov  1 08:22:00 MagicMirror kernel: [86411.138649] raspberrypi-firmware soc:firmware: Request 0x00048003 returned status 0x80000001
Nov  1 08:22:00 MagicMirror kernel: [86411.138665] bcm2708_fb soc:fb: Failed to allocate GPU framebuffer (-22)
Nov  1 08:22:00 MagicMirror kernel: [86411.138670] detected fb_set_par error, error code: -22
Nov  1 08:22:00 MagicMirror kernel: [86411.139138] raspberrypi-firmware soc:firmware: Request 0x00048003 returned status 0x80000001
Nov  1 08:22:00 MagicMirror kernel: [86411.139148] bcm2708_fb soc:fb: Failed to allocate GPU framebuffer (-22)
Nov  1 08:22:00 MagicMirror kernel: [86411.139152] detected fb_set_par error, error code: -22
Nov  1 08:22:00 MagicMirror kernel: [86411.140642] raspberrypi-firmware soc:firmware: Request 0x00048003 returned status 0x80000001
Nov  1 08:22:00 MagicMirror kernel: [86411.140654] bcm2708_fb soc:fb: Failed to allocate GPU framebuffer (-22)
Nov  1 08:22:00 MagicMirror kernel: [86411.140659] detected fb_set_par error, error code: -22
Nov  1 08:22:00 MagicMirror kernel: [86411.140777] raspberrypi-firmware soc:firmware: Request 0x00048003 returned status 0x80000001
Nov  1 08:22:00 MagicMirror kernel: [86411.140785] bcm2708_fb soc:fb: Failed to allocate GPU framebuffer (-22)
Nov  1 08:22:00 MagicMirror kernel: [86411.140789] detected fb_set_par error, error code: -22
Nov  1 08:22:00 MagicMirror kernel: [86411.140856] raspberrypi-firmware soc:firmware: Request 0x00048003 returned status 0x80000001
Nov  1 08:22:00 MagicMirror kernel: [86411.140863] bcm2708_fb soc:fb: Failed to allocate GPU framebuffer (-22)
Nov  1 08:22:00 MagicMirror kernel: [86411.140868] bcm2708_fb_pan_display(0,0) returns=-22
Nov  1 08:22:00 MagicMirror systemd[1]: Started Getty on tty6.
Nov  1 08:22:00 MagicMirror kernel: [86411.256398] raspberrypi-firmware soc:firmware: Request 0x00048003 returned status 0x80000001
Nov  1 08:22:00 MagicMirror kernel: [86411.256413] bcm2708_fb soc:fb: Failed to allocate GPU framebuffer (-22)
Nov  1 08:22:00 MagicMirror kernel: [86411.256418] detected fb_set_par error, error code: -22
Nov  1 08:22:00 MagicMirror kernel: [86411.256758] raspberrypi-firmware soc:firmware: Request 0x00048003 returned status 0x80000001
Nov  1 08:22:00 MagicMirror kernel: [86411.256770] bcm2708_fb soc:fb: Failed to allocate GPU framebuffer (-22)
Nov  1 08:22:00 MagicMirror kernel: [86411.256775] bcm2708_fb_pan_display(0,0) returns=-22
Nov  1 08:22:00 MagicMirror kernel: [86411.296428] raspberrypi-firmware soc:firmware: Request 0x00040002 returned status 0x80000001
Nov  1 08:22:00 MagicMirror kernel: [86411.296455] bcm2708_fb soc:fb: bcm2708_fb_blank(0) failed: -22

Switching off the screen with

/opt/vc/bin/tvservice -o

and on with

/opt/vc/bin/tvservice --preferred && sudo chvt 6 && sudo chat 7

does not work reliable! The git issue tells you more about.

The workaround is a not yet described solution inside the config.txt

https://github.com/raspberrypi/documentation/pull/245/files

the option “hdmi_blanking=1” is your friend in this case! :D

Now i’m switching off the screen with

vcgencmd display_power 0

and on with

vcgencmd display_power 1

And it is working now like a charm! Did started to use it one day before this report and it is still working without any issue :)

Honestly speaking i don’t use any MM module for switching off anymore. But maybe my discovered solution will help any other and might be a way to change the module as well.

If you have trouble with on/off as well please check the output of dmesg. If you have the frambuffer problem you can fix it.

My personal solution is to have the PIR state at FHEM and from FHEM i’m using a script to switch the screen. But that’s a special case and for the most people here the usage of a MM Module will be the better way.

regards
Dirk

bibi

@DirkS thx for sharing! one question please : where is located the option : “hdmi_blanking=1” ???

bhepler

@bibi Based on that pull request, it looks like it’s in the config.txt of your Pi. So /boot/config.txt

DirkS

@bibi yes you need to include it into /boot/config.txt

bibi

@Dirks Thx!
@bhepler Thx! i will add this option there under HDMI hotplug as i don’t know where else to add.

bibi

@bhepler and @DirkS : any idea why my screen doesn’t stay off as long as no motion is detected??