Which version of Debian are people using for their MMs?
I’m currently still running my MM on Debian 11 as I have an issue with moving building a new MM on Debian 12.

The issue I have is that when I build a new Debian 12 machine (bare metal or virtual) I cannot seem to get the MM to automatically display and Debian only ever displays the Activities Overview.
During the Desktop environment section of the OS installation, I only opt to install the default Desktop environment and unselect the Gnome environment.

What do/have people done to get around this?

@sdetweil I’ve seen a similar post where you mentioned that you set the value for maximumEntries to 200, so I’ve now tried this and the calendar events show in the desired module.

Thanks

@plainbroke Are you running from a Pi?
I used to have scheduled on/off times like this and I used to turn on/off the HDMI port of the Pi at the specified times.
As the screen I had it attached to no longer detected an output source, it would then go into sleep mode until the assigned time the script enabled the HDMI interface again.

I don’t recall the actual command/settings I used to do it, but it was similar to :
// To turn off
xrandr --output HDMI-1 --off
//to turn on.
xrandr --output HDMI-1 --auto

@sdetweil my maximumEntries setting is configured for 50, but I do have it in the general config{} section of the module.
Should it be in the calendars[] section with the calendar’s URL?

@sdetweil OK, thanks.
I’ll get back to you later on what exactly I have in my config.

@sdetweil Do you mean the maximumEntries setting, as I could not find a maximumEvents setting listed on the module’s config options?
Not able to check right now, but I believe my setting for the maximumEntries setting is either 25 or 50, just based on what I recall seeing displayed by the default Calendar module when I uncommented the position: top_left setting.

I’ve just updated to v2.30.0 and the events of my Google Calendar are no longer showing via the MMM-MonthlyCalendar module.

I noted the changes to the default Calendar module and added all options to my config.js file, setting applicable options as required, but the events are still not displayed.

When I enable the default Calendar to be displayed (top_left), events show as expected.

@sdetweil
It would just display a blank calendar with no events - past or future

I resolved the issue 5 minutes after I posted my enquiry and it is working as expected now.
Not 100% sure, but I think I had mistyped the URL, specifically the /private-…/basic.ics section.

Hi all
I’ve installed the MMM-MonthlyCalendar from kolbyjack (https://github.com/kolbyjack/MMM-MonthlyCalendar).
The module displays the current month without an issue, but it is not displaying the desired calendar.

I assume the module utilises the MM’s default Calendar module to access my Google calendar as there are no details about adding the calendar within the config of the MMM-MonthlyCalendar module.
My Google calendar displays fine within the default module, just not in this module from kolbyjack.

If anyone has any pointers on what I should/need to do, it would be greatly appreciated.
Thanks

@sdetweil
yeah, I started it via the mm2.sh script that had the “npm run server” command
I’ve now started the second instance as “pm2 start pm2_MagicMirror2_new.json” and “pm2 status” does show both instances running.
Ran “pm2 save”, rebooted the host and both instances are showing as expected - MM#1 on the display connected to the host device, with MM#1 and MM#2 via a browser on a remote device/devices.

@sdetweil
Fair enough.
So i’ll have to have a physical computer like a Pi, NUC or MiniPC attached to the TV via HDMI to display the MM via that computer’s browser.
Not a big deal as the TV would be used for viewing TV channels and online streaming content anyway.

@sdetweil
after running the mm2.sh script (runs as “npm run server”) and then I initiate a new SSH to the MM, I still only see a single instance (the original instance from mm.sh) of MM running when I issue a pm2 status command.
Although I can physically see the second MM displayed as desired in my browser, I’m not seeing the second instance via the pm2 status command.

@BKeyport
isn’t this to run two MM’s on a single display and have the second MM displayed from the 1920th pixel on the x axis?

I’m wanting to run two MM’s, each instance on isolated displays - one on the display connected to the host in the traditional method and the other on a remote display like another computer, or TV with an in-built browser.

@sdetweil
OK, so I launched the second instance of MM via mm2.sh with the “npm run server” command.
I then launched a second SSH session to the MM device and issued a “pm2 save” command.
Rebooted the MM device from the second SSH session but the second MM instance didn’t come up.

@sdetweil
so mm2.sh should/would be:
#!/bin/bash
cd ~/MagicMirror
export MM_CONFIG_FILE=config/config2.js
export MM_PORT=8081
npm run server
#DISPLAY=:0 npm start

while mm.sh remains untouched

When I have this in place:

• instance #1 correctly displays on the screen attached to the MM host… tick
• i can also view instance #1 on a browser (on port 8080)… tick
• can view instance #2 in a browser (on port 8081)… tick

However, when I run mm2.sh while I am SSH’d to the MM, I am not returned to the command line so I can save the pm2 setup.
I just have a prompt saying “Ready to go! Please point your browser to http://ipaddress:8081”

I have to Ctrl-C to cancel out, which then stops the server function and the #2 instance is no longer displayed

@sdetweil
OK, so no requirement to update the “name” and “watch” values in the .json file, but it doesn’t hurt to do so from an fyi perspective, right???

When I run “pm2 start config2.js”, I can then access the second instance via browser on another device with no issue, but it also takes over the display directly connected to the MM host device.
I can view both MM instances via a browser on different devices (great, as that was one of my original questions), but what if i want to view instance #1 via the display directly connected to the MM host device and instance #2 via a remote browser (or vice versa?

My .sh files to start each MM instance are as follows:

mm.sh
#!/bin/bash
cd ~/MagicMirror
DISPLAY=:0 npm start

mm2.sh
#!/bin/bash
cd ~/MagicMirror
export MM_CONFIG_FILE=config/config2.js
export MM_PORT=8081
npm start
#DISPLAY=:0 npm start

Should I change anything, or what would I need to change, to have the desired outcome described above?

@sdetweil
Thanks. That has sort of help me out and pointed me in the right direction.

Is it just as simple as copying the existing:

• mm.sh file -->> mm2.sh
• pm2_MagicMirror_new.json -->> pm2_MagicMirror2_new.json

and editing the pm2_MagicMirror2_new.json file to reference:

• the app name of MagicMirror2
• the script of mm2.sh (is there anything to change in this?)
• watching the config2.js file for changes

and then executing pm2 start config2.js --name MagicMirror2

Is it possible to run multiple mirrors from a single device?

My current MM utilises the default Calendar module to display family member calendars from Google in the top_left section and the MMM-CalendarWeek module in the bottom_bar section to display another Google calendar.
I know I can display the MM via a web browser on any number of devices, but this is just a duplicate of what I see from the directly-connected host device.

I want to output the family calendars on one display while the other calendar displays on another.
This could be where one is displayed to a directly-connected output, while the other is viewed from a browser, or possibly, both are displayed via a browser if physically locating the host with either display isn’t possible.

Is this sort of setup doable?

I had read online that I would have to create a second config.js file, configured as required for the alternate view.
Within that file, I would have to specify an alternate port (say 8081) and initiate a secondary instance of MM.
However, the instructions never indicated or specified how the second config.js file would be referenced in order to display the appropriate output.

@sdetweil Thanks Sam

I’ve removed the git reset --hard from my .sh script
I had some small changes (gap-body-top/right/bottom/left set to 10px) in main.css which were reset back to the default 60px when I ran the git reset --hard command, so added those line specifically in the custom.css file instead and left the default vaules in the main.css file.

For the updatenotification module, does the git pull command, for the respective specified modules not work?
I thought having a git pull command for the modules would negate the need to update them rather than have something display. I’m happy for the core MM update notification but didn’t want notifications for installed modules.
Am I, instead better off updating them as per the .sh script above?

One last thing, when I update the config.js file, MM would normally auto-restart with file being rewritten.
Now, for some reason, it doesn’t. How can I get it to do so?

I created the following script that updates MM and the modules that i use.
The script is scheduled to run via a systemd timer at a given date and time :

#!/bin/bash
cd ~/MagicMirror
git reset --hard
bash -c “$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)” apply
cd ~/MagicMirror/modules/MMM-CalendarWeek
git pull
cd ~/MagicMirror/modules/MMM-OpenmapWeather
git pull
cd ~/MagicMirror/modules/MMM-Wallpaper
git pull
cd

My questions are :
1 - do I have to run a “git reset --hard” at all prior to running the update-script.sh script?
2 - if I have also configured the updatenotification module for those listed 3x modules, do I have to perform the “git pull” command in my own script if the command for those modules is specified?
{
module: “updatenotification”,
position: “bottom_bar”, //#position: “top_bar”,
config: {
updateInterval: 600000, // must be greater than 60000 (1 minute)
ignoreModules: [], // [“MMM=ExampleModule1”, “MMM-ExampleModule2”]
updateTimeout: 120000, // 2 minutes
updateAutorestart: true, // true, false
updates: [
{
“MMM-Wallpaper”: “git pull”,
},
{
“MMM-OpenmapWeather”: “git pull”,
},
{
“MMM-CalendarWeek”: “git pull”,
},
],
},
},

Thanks.