@goldyfruit Very cool! 🚀Don’t forget to add MMM-ShareToMirror to the module list 🙂

If --run is a bad option let’s try run the long command directly and see what happens.

So instead of npm run, try this:

On Wayland:

WAYLAND_DISPLAY="${WAYLAND_DISPLAY:=wayland-1}" ./node_modules/.bin/electron js/electron.js --enable-features=UseOzonePlatform --ozone-platform=wayland

On X11:
DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js

This may show us the real core of the problem, or it works and starts MM properly and we could make it a little more comfortable (even if it is a bit hacky).

@OliWer Thanks for reporting. Please check https://github.com/MMM-CalendarExt2/MMM-CalendarExt2/issues/401.

@Lmagenis I can’t find MMM-TitanSchoolMenu on the module list.

@PierreGode The wiki page is empty :-(

Nice :-) Don’t forget to add it to the modules list: https://github.com/MagicMirrorOrg/MagicMirror/wiki/3rd-party-modules

@jimbocz Seems that the position setting isn’t optional anymore. This works for me:

  modules: [
    {
      module: "alert"
    },
    {
      module: "updatenotification",
      position: "top_bar"
    },
    {
      module: "clock",
      position: "top_left"
    },
    {
      module: "MMM-BackgroundSlideshow",
      disabled: false,
      position: "fullscreen_below",
      config: {
        imagePaths: ["modules/MMM-BackgroundSlideshow/exampleImages/"],
        transitionImages: false,
        randomizeImageOrder: true,
        slideshowSpeed: 30000,
        resizeImages: true,
        maxWidth: 1024,
        maxHeight: 600,
        backgroundSize: "contain"
      }
    },
    {
      module: "weather",
      position: "bottom_right",
      config: {
        weatherProvider: "openmeteo",
        type: "current",
        lat: "51.5085",
        lon: "-0.1257"
      }
    },
    {
      module: "MMM-Carousel",
      position: "bottom_right",
      config: {
        transitionInterval: 10000,
        ignoreModules: [
          "MMM-BackgroundSlideshow",
          "alert",
          "updatenotification"
        ],
        mode: "global"
      }
    },
  ]

@AndyHazz Unfortunately, I don’t know if I can help any further here. The error message ([ERROR] table not found in HTML.) is indeed from MMM-Scrapey - I have created a pull request for the module to improve logging, at least in the future.

@AndyHazz said in 2.32.0 Calendar module limitDays and excludedEvents stopped working:

but in case you’re onto something

Not sure, but you have a rather old version of MMM-Remote-Control which is only compatible to a limited extent with MM 2.32.0. If you update MMM-Remote-Control, the start of MM may not abort like above.

@AndyHazz said in 2.32.0 Calendar module limitDays and excludedEvents stopped working:
Looks like an issue with MMM-Remote-Control.

Which version are you using? Run grep '"version":' package.json in MMM-Remote-Control’s directory to find out.

@mumblebaj Cool!

But one hint because I saw this change to the license file: You cannot relicense GPL software under MIT. If you fork a project under the GNU General Public License (GPL), your modified version must also stay under GPL. The GPL’s rules are strict — you can’t change it to a more permissive license like MIT.

@MrPinner141 I can’t take a closer look at it right now, but I have an idea for a workaround: But it only works if MM restarts regularly. Some users shut MM down at night and start it up again in the morning. Then you could set the timer for the homepage to over 24 hours, this should have the desired effect that the homepage is always visible.

@mumblebaj Just an idea: Maybe the node version used in Cron could be to old. When you run a script manually in your terminal, your full user environment (including things like .bashrc or .zshrc) is loaded. Cron runs in a much more minimal environment — it often doesn’t load your shell config files, so tools like nvm (Node Version Manager) might not be available.

How to fix it:

• Use the full path to Node: Find it with which node and use that path in your cron job.
• Set the environment manually in cron: You can define your PATH at the top of the cron file.
• Source nvm in your script: If you use nvm, add source ~/.nvm/nvm.sh and nvm use <version> before calling node.

@mumblebaj said in Starting MM Crontab:

DISPLAY=0 node --run start:X11

It should be start:x11 and not start:X11.

Are you still using X11?

Does it run when you start it manually?

Can you provide the logs from the startup?

@MrPinner141 said in MMM-Pages:

        timings: {
            default: 0,               // rotate every 5 seconds   
            0: 0,                     // page 0 rotates every 20 seconds
            1: 20000,
        },

To understand your setting better:

• What do you want to achieve with 0 ms for 0 and default?
• Does the behavior also occur if you enter values above 0 at 0 and default?

@sdetweil said in MMM-Chores - Manage and keep track of your household Chores:

or use unclutter (have apt install it) will only be visible when you move it

I think unclutter doesn’t work on modern systems (Wayland).

@PierreGode said in MMM-Chores - Manage and keep track of your household Chores:

What i found hard is that the mouse is invisible on magic mirror

MMM-Cursor can solve that 🙂

@schlomm There is a PR that seems to fix the issue: https://github.com/MarcLandis/MMM-Buttons/pull/11

@mumblebaj said in MagicMirror Container:

Well, I wanted to see how it works

That’s a pretty good reason 👍

Just out of curiosity: What made you decide to build a container yourself? 🙂