MagicMirror Module to display a calendar with multiple months

A mini-calendar with as many months as the user wants, assuming screen space is available.

Download

https://www.github.com/BKeyport/MMM-Multimonth
[card:BKeyport/MMM-Multimonth]

Installation

Clone this repository in your ~/MagicMirror/modules/ folder ( $ cd ~MagicMirror/modules/ ):

git clone https://github.com/BKeyport/MMM-Multimonth.git

Using the module

To use this module, add it to the modules array in the config/config.js file:

{
  module: 'MMM-Multimonth',
	position: 'top_left', // can be any of the postions
	config: { // Optional - will default to 3 months, with one previous and one next. 
	  startMonth: -1, // Define when you start from current month (negative is before current, zero is current, positive is in future) 
         monthCount: 3, //  How many months to display 
         highlightWeekend: false // highlightWeekend if desired, set to true. 
	}
}

Many thanks to kirash for the inspiration with the monthly_calendar module, sdetweil and lavolp3 for the help in coding and CSS work. Without your help, this would just be a pipe dream.

This is a basic module, but I felt it was good enough for release to the public.

Please, if you have any suggestions for improvement, let me know, I’m learning Javascript and CSS as I write this, and I dream of much bigger things.

Localization is provided by moment.js and controlled by the master language of MagicMirror. Please file any errors with localizations as bugs with the moment.js team - https://github.com/moment/moment/

Please see github for version info and further instructions.

@tippon To speed reinstall - I have my config.js and custom.css symlinked to a common location outside the MagicMirror tree, and a bash script setup to clone and npm install every module I use, and reinstall the symlinks.

easy peasy…

My system backs that up nightly to a private github repository, and bam quick and dirty way to get my system back running when my pi crashes.

MagicMirror Module to display clocks from multiple time zones

After not getting an answer on Sean’s EXCEPTIONAL worldclock module (His first) from the new maintainer, I decided to fork it and start working on it myself. As such, I present to you “MMM-Worldclock”… It’s mostly Sean’s work, with a few fixes here and there right now.

This will be fully supported, much in the spirit of Sean’s work.

This module is derived from default MagicMirror module ‘clock’ and modified. Thanks to michaelteeuw.
This module displays times from around the world.
Modified fork of worldclock by eouia, renamed and improved.

Installation

1. Execute the following commands to install the module:

cd ~/MagicMirror/modules # navigate to module folder
git clone https://github.com/BKeyport/MMM-Worldclock # clone this repository

2. Then, add the following into the modules section of your config/config.js file:

{
  module: 'MMM-Worldclock',
  position: 'top_left', // This can be any of the regions, best results in top_left or top_right regions
  config: {
    // See 'Configuration options' for more information.

    timeFormat: 'hh:mm A', //defined in moment.js format()
    style: 'top', //predefined 4 styles; 'top', 'left','right','bottom'
    offsetTimezone: null, // Or you can set `Europe/Berlin` to get timegap difference from this timezone. `null` will be UTC timegap.
    clocks: [
      {
        title: "Home",
      },
      {
        title: "HOLLYWOOD", // Too long title could cause ugly text align.
        timezone: "America/Los_Angeles", //When omitted, Localtime will be displayed. It might be not your purporse, I bet.
        flag: "us",
      },
      {
        timezone: "Asia/Seoul",
      },
    ]
  }
},

Of course, you should change the configuration values for your purpose.

for configuration options see github.

Updates:

2020-08-06 (BKeyport) Fixed timeFormat per clock to work properly.
2019-02-24 (Sean) offsetTimezone is added.
2017-08-25 (sean) supports MMM-TelegramBot (https://github.com/eouia/MMM-TelegramBot) command /worldclock is added
2017-08-10 (sean) Country flags are supported. HTML/CSS Structures are refined.

** Note: telegram bot may not work in this version, I did not modify that code in the slightest, however, if it’s relying on the module name, it’s broken. I’ll fix it if it gets reported to me.

Thanks to Seongnoh Sean Yi’s (eouia) for his exceptional module and all the wonderful support he’s done over the years. I wouldn’t have the knowledge I have without Sean’s help.

sudo Raspi-config 

Advanced Options -> GL Drivers -> Legacy.

“legacy” and “normal” drivers are the same thing.

The problem with having the mirror and the sensor so close is that the heat from the monitor and the pi itself will mess with the readings of the sensor.

@MMRIZE I’d love to see a plugin store and/or marketplace of sorts. Some other projects uses NPM with a fancy front end web to do so, much like some modules use(d) a web interface to set up the initial config or adjust configs (Sam’s config module, MMM-RTSP, etc)

This would be an ideal marketplace (Simple, to the point, shows everything a user needs) :

Then when the user wants to config:

Homebridge is one of the better ways of doing things, IMO.

https://www.youtube.com/watch?v=RFsIWtmc-WA

Becky Stern walks us through her Magic Mirror design build, including disassembling a monitor, building a frame, etc. It’s a cool setup.

One of the best commands to know is

 npm run config:check

Start at the topmost error and work your way down the file - it’s got lots of problems, but is easily fixed. Also, I highly recommend a graphical type editor if possible - Geany is what I use.

I installed samba on my magic mirror so I can edit with the PC version of Geany and save it right to the Pi. It’s great.

Take a look into https://github.com/MMM-CalendarExt2/MMM-CalendarExt2

It can make your calendars dance.

Really.

FWIW, in the future,

Open a terminal
Type cd MagicMirror and press Enter
Now you’re in the MagicMirror directory
Type npm run config:check and press Enter
MagicMirror will now check your config

@Future-Mirror It may be wayland causing that - Try this:

sudo raspi-config

then use
option 6 “Advanced options”,
option A6, “Wayland”, then
option W1 “X11”
and approve the change.

This will switch you over to the old screen design system, where the instructions in the documentation is known to work.

If you would like, I’d be happy to share my configuration files up to the modules and how I did it. Let me know.

@DarrenO-0 Ahh, gotcha. Yes, this is for two on the same system, which linux treats as one huge monitor.

As I rewrote that section in the docs - I’ll give a (semi) live example (My second mirror is down due to lack of space, I’m working on a solution) - this is what works for me at the moment. I do realize I’m doubling up on some things.

In my Pi’s config, I also reverted to X11 desktop rather than wayland for reasons unrelated. I have not tested this on Wayland.

---

mm.sh

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

mm2.sh

cd /home/bkey1970/MagicMirror
export MM_CONFIG_FILE=config/config2.js
export MM_PORT=8081
DISPLAY=:0 npm start

the start of config.js:

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

The start of config2.js:

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

PM2 commands to tie it all together:

pm2 start /home/<username>/<path>/mm.sh --name "MM Main"
pm2 start /home/<username>/<path>/mm2.sh --name "MM 2nd"
pm2 save

@MarkV It’s documented how to do it. I (re)wrote that documentation personally. Feel free to read https://docs.magicmirror.builders/configuration/introduction.html#advanced-configuration-and-frequently-asked-how-to-configure-examples and ask here if you have any questions, I’ll be more than happy to help.

@sdetweil I simplifed out the details on purpose… Trying to keep it simple, Stupid (KISS)

:)

@DDE12
If simply turning off the monitor. No it does not stop MM or modules.

If stopped with Module Scheduler, maybe. Module Scheduler has to announce that it’s hiding a module, and the module being hidden has to process that announcement.

What I do, is have an external routine to turn off my monitor(s), and then stop the MM process completely upon leaving where my MM is. When I return, another routine turns on my monitors and restarts my MM install.

So, the forum now wants to do this every time I have a notice on any followed thread.

This is not theme dependent.

Thought I’d let y’all know so it could be passed up the chain.

@Cliff365 Usually the APIs change season to season in all sports.

Just the way it is.

@dcazman Clearly, HDMI.

Seriously though

1. one that exposes the ports to the bottom of the case, not out the back. This will make it easier to mount regardless of use.

2. one with a bezel around the front - makes it easier to de-case if you decide to do that. The “zero bezel/minimum bezel” front cases have nasty fronts that make it difficult to use behind custom glass.

3. look through the showcase for other recommendations - they have a LOT of teardown examples.

@KristjanESPERANTO Encoded lines? Oh hell no.

Don’t care if it’s fully documented, if I’m not able to at least look at the code, then it’s a hell no for me.