• Recent
  • Tags
  • Unsolved
  • Solved
  • MagicMirror² Repository
  • Documentation
  • 3rd-Party-Modules
  • Donate
  • Discord
  • Register
  • Login
MagicMirror Forum
  • Recent
  • Tags
  • Unsolved
  • Solved
  • MagicMirror² Repository
  • Documentation
  • 3rd-Party-Modules
  • Donate
  • Discord
  • Register
  • Login
A New Chapter for MagicMirror: The Community Takes the Lead
Read the statement by Michael Teeuw here.

Motion Detector

Scheduled Pinned Locked Moved Utilities
213 Posts 38 Posters 442.8k Views 39 Watching
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • D Offline
    DirkS
    last edited by Nov 1, 2016, 7:29 AM

    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
    
    1 Reply Last reply Reply Quote 1
    • D Offline
      DirkS
      last edited by Nov 3, 2016, 9:19 PM

      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

      1 Reply Last reply Reply Quote 1
      • D Offline
        DirkS
        last edited by Nov 4, 2016, 9:19 AM

        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

        B D 2 Replies Last reply Nov 4, 2016, 6:48 PM Reply Quote 2
        • B Offline
          bibi @DirkS
          last edited by Nov 4, 2016, 6:48 PM

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

          B 1 Reply Last reply Nov 4, 2016, 7:06 PM Reply Quote 0
          • B Offline
            bhepler Module Developer @bibi
            last edited by Nov 4, 2016, 7:06 PM

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

            B 1 Reply Last reply Nov 4, 2016, 11:06 PM Reply Quote 0
            • D Offline
              DirkS
              last edited by Nov 4, 2016, 7:09 PM

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

              B 1 Reply Last reply Nov 4, 2016, 7:36 PM Reply Quote 0
              • B Offline
                bibi @DirkS
                last edited by bibi Nov 4, 2016, 8:02 PM Nov 4, 2016, 7:36 PM

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

                1 Reply Last reply Reply Quote 0
                • B Offline
                  bibi @bhepler
                  last edited by Nov 4, 2016, 11:06 PM

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

                  1 Reply Last reply Reply Quote 0
                  • D Offline
                    done @DirkS
                    last edited by Nov 5, 2016, 12:30 PM

                    @DirkS Thank you. Pi doesn’t die over nights :D

                    But before I mess it up:
                    Would the motion detection with the common script work or not?
                    How did you realize it? Where did you enter your new script?

                    And don’t you want to make an additional motion detector module for those who have the same problem? :)
                    I don’t see the original programmer caring to much. ;)

                    cheers
                    done

                    1 Reply Last reply Reply Quote 0
                    • D Offline
                      DirkS
                      last edited by Nov 5, 2016, 12:46 PM

                      @done as discribed above by @cpramhofer (thanks to you :) ) i created the monitor_on and off.sh script.
                      With FHEM i’m polling the PIR status and use a DOIF to call on or off. Because my homeautomation depends in FHEM i have much more control instead of using a MM module, i switch much more devices with the PIR as well. I have several Pi’s with FHEM installed so it is also on the PI for the Mirror.

                      1 Reply Last reply Reply Quote 1
                      • 1
                      • 2
                      • 9
                      • 10
                      • 11
                      • 12
                      • 13
                      • 21
                      • 22
                      • 11 / 22
                      11 / 22
                      • First post
                        110/213
                        Last post
                      Enjoying MagicMirror? Please consider a donation!
                      MagicMirror created by Michael Teeuw.
                      Forum managed by Sam, technical setup by Karsten.
                      This forum is using NodeBB as its core | Contributors
                      Contact | Privacy Policy