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.

    MMM-MyStandings stops

    Scheduled Pinned Locked Moved Troubleshooting
    9 Posts 3 Posters 909 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.
    • G Offline
      ghiesseldorf @sdetweil
      last edited by

      @sdetweil No joy. No errors being posted for mystandings. I am using facial reco as well. And I see messages showing when mystandings (and myscores) indicating the module being hidden, suspended, and resumed according to the personna set in the config file. The same messages are being posted for the myscores module using the same personna definitions which works just fine. But mystands doesn’t appear to be resuming (or unhidden?) on the screen like it should.

      1 Reply Last reply Reply Quote 0
      • mattkabM Offline
        mattkab
        last edited by mattkab

        Sorry to necropost to a 2 year old thread.

        But I’m seeing the same issue, on the same module. Anyone know why this happens?

        I have confirmed that it’s making the proper requests to the API, and the API is responding with a valid JSON object.

        If I restart MM, the standings show up again, but after some period of time, it just disappears. I do use MMM-Carousel to create slides.

        I’ll continue to debug.

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

          @mattkab if you look in the mm console output, from npm start

          you should see a message

          console.log(“MMM-MyStandings : Could not load data.”);

          once this happens it never recovers.

          the message doesn’t provide any info on the cause.

          if you use pm2 to.launch.mm, the the messages are in the pm2 logs

          pm2 logs --lines=nnn

          nnn is some number default 15

          Sam

          How to add modules

          learning how to use browser developers window for css changes

          1 Reply Last reply Reply Quote 0
          • mattkabM Offline
            mattkab
            last edited by

            Thanks! I do see that error. I’ve added a ton more logging information to my local instance, and have restarted MM. If it happens again I’ll have more data to go by.

            When it hits that condition, it doesn’t send a notification, so that probably breaks the timer interval, though I’m not seeing yet how that happens. I’ll continue to debug.

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

              @mattkab correct. it doesn’t reply , so the front end is waiting. it checks the loaded status, and waits til that happens which will never occur.

              the node helper could log the status( it’s not 200) and any error reported in the API callback. to help w this debugging.

              most of the modules have limited to no error recovery

              Sam

              How to add modules

              learning how to use browser developers window for css changes

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