Magic mirror dual screen

[sdetweil]

@BKeyport @1a2a3a

copy the second config.js to the first mm config directory as config2.js

edit the mm2.sh

cd to the first mm directory(instead of the second)
and add a line

export MM_CONFIG_FILE=${cwd}/config/config2.js
npm start

now. make sure all the modules needed by both instances are installed in the modules folder of the 1st instance.

if they aren’t used by a particular instance, no big deal, same as setting disabled:true on a module config

[BKeyport]

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

[BKeyport]

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.

[sdetweil]

@BKeyport nice description

[BKeyport]

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

[1a2a3a]

Thanks all! I’ll give this a go once the monitor arrives!

[sdetweil]

@1a2a3a @BKeyport

the MM_CONFIG_FILE problem is mine

the correct stmt would be

export MM_CONFIG_FILE=$(pwd)/config/config2.js

notice I changed the brackets to parens and changed the command name

[BKeyport]

This post is deleted!

[sdetweil]

@BKeyport I just fixed it

[BKeyport]

It has to be brackets on my system, FYI.

[sdetweil]

@BKeyport ok…

[1a2a3a]

btw, how do i configure the css for the 2 screen?

[sdetweil]

@1a2a3a you would set the css filename in its config.js

so you would have css/custom.css and css/custom2.css, one for each instance

from the doc
https://docs.magicmirror.builders/configuration/introduction.html

customCss	The path of the custom.css stylesheet. The default is css/custom.css.

[BKeyport]

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

[sdetweil]

@BKeyport yeh but I assumed there was a conflict, else he wouldn’t have known there was an issue.

[1a2a3a]

Decided to drop this for now guys. The new monitor is a 27 qhd compared to the previous 24 fhd. With the extra real estate, everything doesn’t seems to be so cluttered now.