@MichMich Thanks for all you’ve done for the project, and rest assured - it’s in good hands.

@Kelemvor If you don’t want to do a global change, each module will likely have it’s own CSS to do it, best to load your mirror in a browser that has dev tools, and find it that way, changing in custom.css, for example…

/* CalendarExt3Agenda */
.CX3A {
	font-size: 20px;
}

@Bungle68 I do it on a per module basis as there’s really no front end for it. Get the notification from the app, go to the module’s directory, and git pull and npm install to update.

As for the main unit, I used @sdetweil 's script to install, so I use his update script to update - Don’t know if you can update without the initial install being his script.

@nakulbende Looks like you might have missed a step in installing your mirror from my point of view. the module “fetch” is missing, which indicates “npm install” may not have been run from the MagicMirror directory. How did you install?

@nakulbende 90% of the time this can be ignored. If you’re getting your mirror up on screen, there’s no issue.

@csongor-varga-0 List view is provided by either the main calendar module itself, or CX3Agenda. (Same name, just add Agenda on the back)

@csongor-varga-0 the CX3 line of products are basically a whole new product from CX2, same as CX2 was a whole new product over CX. They really don’t have anything to do with each other, other than name.

@zdenek I’ve never been able to get any stream working out of RTSPStream other than OMXPlayer, which is quite dead, sadly. What I’ve done is use an old pi I had lying around to run MotionEyeOS to convert the image, then MMM-EmbedURL to embed the web “Photo” generated by MotionEyeOS. I need a modern solution, but it works.

With RTSPStream going unsupported, I would look for another solution.

That being said, it does appear to have a direct URL = http://user:pass@192.168.X.X/axis-cgi/mjpg/video.cgi

If that produces a image stream DIRECTLY IN A BROWSER, you can use MMM-EmbedURL and the like to point directly at that and bam you’ve got it without a fuss. If it attempts to load a video player, no dice.

@sdetweil alternatively, use the single custom.css file if there’s no conflict.

It has to be brackets on my system, FYI.

@bebetter14 Avoid the AI engines. They’re mostly useless, just FYI. Enjoy the process. If you end up with a releasable module, great, if not, hey, it’s a learning experience.

@bebetter14 I started out that way. What I did personally, was take a dead module that I really liked and started trying to figure out how it worked. Looked up the commands (Lots of searches for “XYZ Javascript” etc and playing on Jsfiddle.net – -Once I got that figured out, I built up my own module (MMM-Multimonth) and got help from some amazing people on here, including Sam and mmrize - major contribution was from a user who CSSified the whole thing and showed me how to do it.

Knowledge grows as you jump in.

@Kelemvor there’s multiple WOTD modules, some that can be controlled through CSS, some that can’t. If yours has a .CSS file, check to see if there’s an element with “width” as a tag, if so, you can set ‘max-width’ in that tag and cut it back. You may need other tags to force it to wrap, etc, however.

@Kelemvor That is a very old, and very unsupported module. I would recommend that you instead take a look at MMM-CalendarExt3Agenda instead, or stick with the default Calendar module if you want to keep the default look.

@sdetweil I figured I might as well make it as clear as possible…

Here’s the answer for @1a2a3a (Edited to show below changes)

Here’s how to do it cleanly: (replace <username> with your pi login name., with width of first monitor)

1. create two starting scripts:

First, mm.sh is as follows:

cd /home/<username>/MagicMirror
DISPLAY=:0 npm start

Second, mm2.sh is as follows:

cd /home/<username>/MagicMirror
export MM_CONFIG_FILE=${pwd}/config/config2.js
DISPLAY=:0 npm start

2. Two config files in magicmirror/config next:

First, config.js (this is your second monitor):

       var config = { 
       electronOptions: { x: <width> },
        address: "0.0.0.0",
        port: 8080,
        ipWhitelist: [],
        language: "en",
        timeFormat: 12,
        units: "imperial",
        //logLevel: ["INFO", "LOG", "WARN", "ERROR", "DEBUG"],
        modules: [
...

Second config2.js (this is your first monitor):

       var config = { 
        address: "0.0.0.0",
        port: 8081,
        ipWhitelist: [],
        language: "en",
        timeFormat: 12,
        units: "imperial",
        //logLevel: ["INFO", "LOG", "WARN", "ERROR", "DEBUG"],
        modules: [
...

electronOptions will only work in the file that isn’t redirected to a new config - so use that in the config.js only.

Interesting - although, now, it’s ignoring the electronOptions: item.

@BKeyport What I did was two directories, with seperate configs, then mm.sh does:

cd /home/bkey1970/MagicMirror
DISPLAY=:0 npm start

and mm2.sh does:

cd /home/bkey1970/MagicMirror2
DISPLAY=:0 npm start

To get the 2nd on the 2nd monitor, I added:

        electronOptions: {
    x: 1920
},

to the 2nd config.js, right below the address line, and changed the port to 8081.

@sdetweil heck, I’m a little lost there. Can you explain it out a bit better for us? I’m currently running two Magicmirrors back to back with two MM Directories and custom mm.sh files, if I could simplify that, I want to.