@sdetweil

is this breaking the update notification? is there something I can do? Or is the lack of suspend/resume methods ultimately a show stopper here for now?

@sdetweil

sure…

{
         "module": "MMM-Carousel",
         "position":"bottom_bar",
         "showPageIndicators":true,
         "config": {
           "transitionInterval": 20000,
           "mode": "positional",
           "bottom_left": { "enabled": true, "ignoreModules": []  }
         }
      },    

      {
          module: "MMM-MyScoreboard",
          position: "bottom_left",
          classes: "default everyone",
          config: {
             showLeagueSeparators: true,
             colored: true,
             viewStyle: "smallLogos",
             rolloverHours: 11,
             teams: ["BOS"],
             sports: [
               {
                 league: "NHL",
               },
               {
                   league: "MLB",
                   teams: ["BOS"]
               },
               {
                   league: "NFL",
                   teams: ["NE"]
               }
               ]
          }
      },
      {
         "module":"MMM-MyStandings",
         "position":"bottom_left",
         "config":{
            "rotateInterval":2 * 60 * 1000,
            "sports":[
               {
                  "league":"MLB",
                  "groups":[
                     "American League East"
                  ]
               },
               {
                  "league":"NFL",
                  "groups":[
                     "ACF East"
                  ]
               }
            ]
         }
      },

without MMM-Carousel and with the manual updates in the referenced item above, MMM-MyStandings updated properly.

MMM-Carousel was swapping MMM-MyStandings and MMM-MyScoreboard. all this time that standings was not updating, MMM-MyScoreboard was. Scores were updated along with the live game action.

Feels like an issue combining MMM-Carousel and MMM-MyStandings, maybe some kind of notification crossup

ill check tomorrow

has not updated since patch and restart. I think ill try without carousel

Update applied, ill know tomorrow if it worked…thanks.

MMM-MyScorboard and MMM-MyStandings configured within MMM-Carousel as ‘positional’ The bottom_left rotates these two modules.

not sure if MMM-Carousel plays into this, just wanted to add

I see in the server output the fetch on regular intervals

[2025-07-22 11:24:18.047] ^[[44m[DEBUG]^[[49m [MMM-MyStandings] https://site.api.espn.com/apis/v2/sports/baseball/mlb/standings?level=3&sort=gamesbehind:asc,winpercent:desc fetched

I have manually pulled the data and it looks correct, however the data on the screen is not updated. If I refresh the screen r, the data is updated.

@sdetweil thanks…I was getting used to “git pull” in the modules.

All is good

I had a backup and restored. everything works again…back to two commits behind

I am similar…undefined in weather, notifications, news

Use --update-env to update environment variables
[PM2] Applying action restartProcessId on app [all](ids: [ 0 ])
[PM2] MagicMirror ✓
┌────┬────────────────┬─────────────┬─────────┬─────────┬──────────┬────────┬──────┬───────────┬──────────┬──────────┬──────────┬──────────┐
│ id │ name │ namespace │ version │ mode │ pid │ uptime │ ↺ │ status │ cpu │ mem │ user │ watching │
├────┼────────────────┼─────────────┼─────────┼─────────┼──────────┼────────┼──────┼───────────┼──────────┼──────────┼──────────┼──────────┤
│ 0 │ MagicMirror │ default │ 2.32.0 │ fork │ 3212 │ 0s │ 3 │ online │ 0% │ 2.7mb │ chris │ enabled │
└────┴────────────────┴─────────────┴─────────┴─────────┴──────────┴────────┴──────┴───────────┴──────────┴──────────┴──────────┴──────────┘
chris@raspberrypi:~/MagicMirror $ npm run install-mm

magicmirror@2.32.0 install-mm
npm install --no-audit --no-fund --no-update-notifier --only=prod --omit=dev

npm error code EBADENGINE
npm error engine Unsupported engine
npm error engine Not compatible with your version of node/npm: @jest/console@30.0.2
npm error notsup Not compatible with your version of node/npm: @jest/console@30.0.2
npm error notsup Required: {“node”:“^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0”}
npm error notsup Actual: {“npm”:“10.9.2”,“node”:“v23.11.0”}
npm error A complete log of this run can be found in: /home/chris/.npm/_logs/2025-07-02T14_09_26_052Z-debug-0.log