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.

    MM shuts down after an hour

    Scheduled Pinned Locked Moved Bug Hunt
    18 Posts 3 Posters 5.4k Views 3 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.
    • S Offline
      sdetweil @Lazershrimp
      last edited by

      @Lazershrimp you are wrong

      if you have a black screen

      you look at the messages put out from npm start

      if you see

      cannot find module xxxx

      then this mm module has the problem

      the fix is to install the missing library (called module in the message,) IN the mm module folder

      NOW as part of the fix process we want the file put in the right place NOT in the MagicMirror folder.

      to DO THAT , the mm module MUST supply a package.json file

      this is where the ls command comes in to the fix process

      it it already exists, cool, do the npm install for the missing library

      if it does NOT exist, create it it with the npm init -y command
      AND then do the npm install for the missing library.

      but, the 1st step is to identify the missing library from the message output.
      if that is NOT the problem, then the rest of the instructions don’t matter

      there are.multiple libraries that could cause the problem, that’s why I have to read the messages to determine which ones are needed

      Sam

      How to add modules

      learning how to use browser developers window for css changes

      L 1 Reply Last reply Reply Quote 0
      • L Offline
        Lazershrimp @sdetweil
        last edited by

        @sdetweil I am having trouble following you, but that would most likely be due to my poor understanding of programming and its terminology.

        You say

        @sdetweil said in MM shuts down after an hour:

        look at the messages put out from npm start
        if you see
        cannot find module xxxx
        then this mm module has the problem

        … I don’t even understand what you mean by “messages put out from npm start”. Is that the “start screen” for MM, the one that appears if you have a say an error in your config file?

        However, I’m thinking that’s not the issue here. As I mentioned, I did follow your guide “fix for black screen in 2.16 …”, and the output was normal. Also, I don’t always get black screens, sometimes it’s a login screen.

        The screensaveroff script didn’t help either. MM still shuts down after a while. It’s not always after an hour, seems to vary. Earlier today it had shut down after 39 mins, now it’s been running for over 40 mins.

        Again, I’m sorry for my bad skills at this. Any help would be much appreciated!

        S 1 Reply Last reply Reply Quote 0
        • S Offline
          sdetweil @Lazershrimp
          last edited by sdetweil

          @Lazershrimp I only have one more question

          does it shutdown if MagicMirror is not running?

          Sam

          How to add modules

          learning how to use browser developers window for css changes

          L 1 Reply Last reply Reply Quote 0
          • L Offline
            Lazershrimp @sdetweil
            last edited by

            @sdetweil said in MM shuts down after an hour:

            I only have one more question
            does it shutdown if MagicMirror is not running?

            Thanks for your patience, Sam.

            Haven’t actually tried not running the MM, since it autostarts. And I don’t have a mouse/keyboard attached to the mirror setup. Good question though.

            But - I think I might actually have figured out what the problem is! I pulled out a long ethernet cable to hardwire the Pi to internet. And - it’s been running for three hours straight now. Thinking that this might actually be a hardware issue.

            If it still runs tomorrow morning, I will call this a faulty Wifi circuit issue. Strange though, that it would coincide with the software update.

            What do you you think? Could a dodgy Wifi crash the MM app?

            S 1 Reply Last reply Reply Quote 1
            • S Offline
              sdetweil @Lazershrimp
              last edited by sdetweil

              @Lazershrimp dodgie wifi creates dodgie data, which crashes all kind of apps

              Sam

              How to add modules

              learning how to use browser developers window for css changes

              L 1 Reply Last reply Reply Quote 0
              • L Offline
                Lazershrimp @sdetweil
                last edited by

                MM has been running flawlessly for >24h now, with assistance of a LAN cable. I consider the issue solved. Have ordered a wifi usb dongle as a more permanent solution. I consider this issue solved.

                S 1 Reply Last reply Reply Quote 2
                • S Offline
                  sdetweil @Lazershrimp
                  last edited by

                  @Lazershrimp awesome detective work!!

                  Sam

                  How to add modules

                  learning how to use browser developers window for css changes

                  1 Reply Last reply Reply Quote 0
                  • 1
                  • 2
                  • 2 / 2
                  • 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