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 486.7k 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.
    • T Offline
      trividar
      last edited by

      Hi Alex,
      thank you so much for your work! Unfortunately my MM start with a black screen after the update. I tried to reboot my Raspi but it didn’t help. Should I make a npm install after the update?
      THX

      1 Reply Last reply Reply Quote 0
      • T Offline
        trividar
        last edited by

        and this is the error:
        error

        A 1 Reply Last reply Reply Quote 0
        • A Offline
          alexyak @trividar
          last edited by

          @trividar My apologies. This should be fixed. Just pull the latest.

          1 Reply Last reply Reply Quote 0
          • T Offline
            trividar
            last edited by

            @alexyak Now my MM start. But after awhile (2 min) i got this error and my MM freeze:

            alt text

            I disabled the DHT module but than i got this error:

            alt text

            Do you have also a solution for this? THX a lot!

            A 1 Reply Last reply Reply Quote 0
            • A Offline
              alexyak @trividar
              last edited by

              @trividar I don’t see anything related to the motiondetector in your logs. It seems the error coming from the mmm-systemperature/node_helper.js

              1 Reply Last reply Reply Quote 0
              • T Offline
                trividar
                last edited by

                I disabled mmm-systemperature and now I have no errors on my log but after first deactivation of the monitor my raspberry freeze completely. Before the pull everything works perfekt beside DHT, now nothing works ;o( strange…

                J 1 Reply Last reply Reply Quote 0
                • J Offline
                  jdahli1 @trividar
                  last edited by

                  @trividar I’m having a similar issue. My mirror will turn on and off a few times, but after a few minutes it will peg the RAM and completely lock up the pi. Not sure what to try next.

                  in_a_daysI 1 Reply Last reply Reply Quote 0
                  • in_a_daysI Offline
                    in_a_days @jdahli1
                    last edited by in_a_days

                    @jdahli1

                    I have also experienced something similar, always while running under a heavy load. Are you running a lot of modules, or anything that is very intensive? Some tasks like video streaming are incredibly demanding on the CPU.

                    My working solution was to modify my module selection so I’m not overworking the processor, and to increase the ‘updateInterval’ in my SystemStats section of config.js. Maybe try 15000 or 20000ms, see if it the crash occurs less often. I also run WatchDog and it would register the SystemStats failure. I don’t see WatchDog in these logs so this may not apply, but I also added increased ‘interval’ and ‘timeout’ settings to config.js. I have not seen this SystemStats crash for quite a while.

                    FWIW - after this crash WatchDog/pm2 does NOT restart my mm shell. All the other failures auto-restart, but something about this one crashes to the desktop. Also - sorry for threadjacking a “Motion Detection” thread!

                    What ship would bear me ever back across so wide a Sea?

                    J 1 Reply Last reply Reply Quote 0
                    • T Offline
                      trividar
                      last edited by

                      I tried to increase the updateInterval to 200000ms and disabled all other modules, but always after the second time the monitor turn off my raspberry freeze completely and I have to reboot. My CPU is around 9 -15% when they freeze. I try again with the old version oft he motion-detector and it works, not perfect but works.

                      1 Reply Last reply Reply Quote 0
                      • J Offline
                        jdahli1 @in_a_days
                        last edited by

                        @in_a_days I guess I do run more modules than what “fit” the screen, but they’re cool and I can’t make up my mind which ones I want to keep lol.

                        However, I don’t believe that is the issue here. I have disabled all but three modules and still face the same issue. The second time the screen goes to sleep, it will not wake up. It doesn’t seem to matter what the CPU load or RAM is at.

                        Watching the pm2 logs, I get an uncaught exception error when the screen is supposed to wake up, but that is all the details I get from it. (That I know how to see, still new to this)

                        in_a_daysI 1 Reply Last reply Reply Quote 0
                        • 1
                        • 2
                        • 11
                        • 12
                        • 13
                        • 14
                        • 15
                        • 21
                        • 22
                        • 13 / 22
                        • First post
                          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