• 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 434.0k 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 Dec 20, 2016, 8:48 PM

    @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 Dec 20, 2016, 10:10 PM Reply Quote 0
    • A Offline
      alexyak @trividar
      last edited by Dec 20, 2016, 10:10 PM

      @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 Dec 20, 2016, 10:25 PM

        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 Jan 5, 2017, 11:35 PM Reply Quote 0
        • J Offline
          jdahli1 @trividar
          last edited by Jan 5, 2017, 11:35 PM

          @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.

          I 1 Reply Last reply Jan 6, 2017, 5:09 AM Reply Quote 0
          • I Offline
            in_a_days @jdahli1
            last edited by in_a_days Jan 6, 2017, 5:39 AM Jan 6, 2017, 5:09 AM

            @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 Jan 6, 2017, 11:26 PM Reply Quote 0
            • T Offline
              trividar
              last edited by Jan 6, 2017, 10:28 AM

              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 Jan 6, 2017, 11:26 PM

                @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)

                I 1 Reply Last reply Jan 7, 2017, 12:47 AM Reply Quote 0
                • I Offline
                  in_a_days @jdahli1
                  last edited by Jan 7, 2017, 12:47 AM

                  @jdahli1

                  Unfortunately, I’m pretty new too!

                  To update - my mirror would still freeze (though it might take a couple hours) even after the changes I suggested. For me, the last error before the crash ALWAYS comes from the system status module (same exact ENOMEM error from the @trividar post). With the sys stat module disabled, I seem to be crash free. May not be the same thing you’re experiencing.

                  I also removed Watchdog after reading a bit more about it’s purpose.

                  If you are able to copy the log file from your most recent crash, someone smarter than me may be able to help.

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

                  M 1 Reply Last reply Jan 7, 2017, 7:58 AM Reply Quote 0
                  • M Offline
                    mydiva @in_a_days
                    last edited by mydiva Jan 7, 2017, 8:08 AM Jan 7, 2017, 7:58 AM

                    @in_a_days how did you disabled sys stat module? and what is that? by the way I have the same thing happen like @trividar

                    I 1 Reply Last reply Jan 7, 2017, 5:50 PM Reply Quote 0
                    • I Offline
                      in_a_days @mydiva
                      last edited by in_a_days Jan 7, 2017, 6:40 PM Jan 7, 2017, 5:50 PM

                      @mydiva

                      The system stat module I’m referring to is this one.

                      https://github.com/BenRoe/MMM-SystemStats

                      It would have to be specifically installed by the user. But looking at the screenshot from @trividar, there are a couple different modules throwing up errors. These couple lines show the modules that appear to be crashing the system:

                      0_1483811268365_error.jpg

                      You can see mmm-systemtemperature and MMM-DHT22 producing error events. I would start by commenting out these modules. Just add a

                      /*

                      before and a

                      */

                      after the section of your config.js file that loads these modules. If that eliminates the crashing you can be confident it is these modules causing the problem, and you can either try to fix them or look for alternatives.

                      EDIT: The common theme between my error and the error posted here is the ENOMEM code, and the fact that all these modules are measuring system temperature. MMM-SystemStats, mmm-systemtemperature, and MMM-DHT22 are all reading temperatures. I would be willing to bet there’s a bug or memory leak somewhere in the code that is pulling or logging temperature info. I’m not convinced any of these particular errors are related to the Motion Detector module.

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

                      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