@lavolp3 thank’s a lot man, you are much faster and way more skilled than me :-)
Just a little discussion: your code only adds the if clause to check if it’s longer than a day to prevent single full day events to be displayed as two day. But what about a multi day event beeing displayed one day to long (which is also happening right now)?

thanks for your comments @Nilnik @StrIIker
This solves the problem, but that’s not a solution :-)
It’s more a kind of a hack to hide the problem. I use it to show my daily apointments inclunding multiday ones. Having the mirror show only e.g. my holiday started 5 days ago without a duration is kind of useless.
As I’m not the only one having that, did anyone ever looked into deeply? Where does this start? Is it a problem with timezones incorrectly submitted by google calendar? Is it a problem of fetching in MM?
If anyone has a guess, I would greatly appreciate any help. When I know where to look, I might also try to search the root of that bug.
Are there some people using it and where it works correctly? Or is simply no one using this module at all (without that hack)?

I just checked, my google account is set to timezone Berlin and my raspberry is too (set in raspi-config). Is there an additional setting for the magicmirror?

Hi,

I use the standard calendar module and it works to my expactations. Only one thing is strange: when I enter a full day event in my google calendar, no matter if 1 day or multiple days, it will be displayed to be on day longer on the MagicMirror.
So a full day event for today (12th october) would be display for today and tomorrow (12th to 13th october). Does anyone know why?

Regards,
Anduril

It seems to be working fine again here… I don’t have any idea what has happened. But I will keep an eye out for further problems.

Hey,

a few days ago I upgraded to 2.5.0. I don’t know if it’s correlated, but I can’t exclude…
This morning I noticed my Mirror showing the desktop and not the mirror interface. It seems to be in a restarting loop, but I don’t see any reason why. I also tried to start it manually without pm2, but I just said Launching application.and returned to the console. Has anyone an idea how to find the cause?

Regards,
Anduril

pi@Spieglein:~ $ pm2 logs MagicMirror
[TAILING] Tailing last 15 lines for [MagicMirror] process (change the value with --lines option)
/home/pi/.pm2/logs/MagicMirror-out.log last 15 lines:
0|MagicMir | No helper found for module: MMM-doomsDay.
0|MagicMir | No helper found for module: MMM-forecast-io.
0|MagicMir | All module helpers loaded.
0|MagicMir | Starting server on port 8080 ...
0|MagicMir | You're using a full whitelist configuration to allow for all IPs
0|MagicMir | Server started ...
0|MagicMir | Connecting socket for: MMM-Remote-Control
0|MagicMir | Starting node helper for: MMM-Remote-Control
0|MagicMir | Connecting socket for: updatenotification
0|MagicMir | Connecting socket for: MMM-DVB
0|MagicMir | Starting module helper: MMM-DVB
0|MagicMir | Connecting socket for: calendar
0|MagicMir | Starting node helper for: calendar
0|MagicMir | Sockets connected & modules started ...
0|MagicMir | Launching application.

/home/pi/.pm2/logs/MagicMirror-error.log last 15 lines:
0|MagicMir | libGL error: MESA-LOADER: failed to retrieve device information
0|MagicMir | libGL error: MESA-LOADER: failed to retrieve device information
0|MagicMir | libGL error: MESA-LOADER: failed to retrieve device information
0|MagicMir | libGL error: MESA-LOADER: failed to retrieve device information
0|MagicMir | libGL error: MESA-LOADER: failed to retrieve device information
0|MagicMir | libGL error: MESA-LOADER: failed to retrieve device information
0|MagicMir | libGL error: MESA-LOADER: failed to retrieve device information
0|MagicMir | libGL error: MESA-LOADER: failed to retrieve device information
0|MagicMir | libGL error: MESA-LOADER: failed to retrieve device information
0|MagicMir | libGL error: MESA-LOADER: failed to retrieve device information
0|MagicMir | libGL error: MESA-LOADER: failed to retrieve device information
0|MagicMir | libGL error: MESA-LOADER: failed to retrieve device information
0|MagicMir | libGL error: MESA-LOADER: failed to retrieve device information
0|MagicMir | libGL error: MESA-LOADER: failed to retrieve device information
0|MagicMir | libGL error: MESA-LOADER: failed to retrieve device information

pi@Spieglein:~/MagicMirror $ DISPLAY=:0 npm start dev

> magicmirror@2.5.0 start /home/pi/MagicMirror
> sh run-start.sh "dev"

Starting MagicMirror: v2.5.0
Loading config ...
Loading module helpers ...
No helper found for module: alert.
Initializing new module helper ...
Module helper loaded: MMM-Remote-Control
Initializing new module helper ...
Module helper loaded: updatenotification
Initializing new module helper ...
Module helper loaded: MMM-DVB
No helper found for module: clock.
Initializing new module helper ...
Module helper loaded: calendar
No helper found for module: compliments.
No helper found for module: MMM-doomsDay.
No helper found for module: MMM-forecast-io.
All module helpers loaded.
Starting server on port 8080 ...
You're using a full whitelist configuration to allow for all IPs
Server started ...
Connecting socket for: MMM-Remote-Control
Starting node helper for: MMM-Remote-Control
Connecting socket for: updatenotification
Connecting socket for: MMM-DVB
Starting module helper: MMM-DVB
Connecting socket for: calendar
Starting node helper for: calendar
Sockets connected & modules started ...
Launching application.
pi@Spieglein:~/MagicMirror $

some additional information: when running fine, pm2 seems to be the parent process:

  612 ?        Ssl    0:34 PM2 v3.1.3: God Daemon (/home/pi/.pm2)
  797 ?        Ss     0:00  \_ bash /home/pi/MagicMirror/installers/mm.sh
  799 ?        Sl     0:04      \_ npm
  946 ?        S      0:00          \_ sh -c sh run-start.sh
  947 ?        S      0:00              \_ sh run-start.sh
  949 ?        Sl     0:01                  \_ node /home/pi/MagicMirror/node_modules/.bin/electron js/electron.js
  958 ?        Sl     8:43                      \_ /home/pi/MagicMirror/node_modules/electron/dist/electron js/electron.js
  960 ?        S      0:00                          \_ /home/pi/MagicMirror/node_modules/electron/dist/electron --type=zygote --no-sandbox
 1088 ?        Sl     4:50                          |   \_ /home/pi/MagicMirror/node_modules/electron/dist/electron --type=renderer --no-sandbox --service-pipe-token=756DBD94487A30A46611ABEDF5588C31 --
 1087 ?        Sl     0:05                          \_ /home/pi/MagicMirror/node_modules/electron/dist/electron --type=gpu-process --no-sandbox --supports-dual-gpus=false --gpu-driver-bug-workarounds=9

but as soon as I stop MM in pm2 I see 2 different parent processes:

  612 ?        Ssl    0:34 PM2 v3.1.3: God Daemon (/home/pi/.pm2)
  958 ?        Sl     8:45 /home/pi/MagicMirror/node_modules/electron/dist/electron js/electron.js
  960 ?        S      0:00  \_ /home/pi/MagicMirror/node_modules/electron/dist/electron --type=zygote --no-sandbox
 1088 ?        Sl     4:51  |   \_ /home/pi/MagicMirror/node_modules/electron/dist/electron --type=renderer --no-sandbox --service-pipe-token=756DBD94487A30A46611ABEDF5588C31 --lang=de --app-path=/home
 1087 ?        Sl     0:05  \_ /home/pi/MagicMirror/node_modules/electron/dist/electron --type=gpu-process --no-sandbox --supports-dual-gpus=false --gpu-driver-bug-workarounds=9,27,84 --disable-gl-exte

so pm2 is still running, but left the electron browser also running now without a parent.

Hey there,

always after restarting I get an error EADDRINUSE. To investigate I looked at `netstat -lptn’ to see which program uses what port.
At startup I see only one line coresponding to MM which is this:

tcp        1      0 0.0.0.0:8088            0.0.0.0:*               LISTEN      1019/electron.js

But when I use `pm2 stop mm’ I still see this line. I also tried to change the port for each restart with the result of having multiple instances of electron listening on the coresponding ports.
When starting it manually without pm2 in the console it opens and closes correctly after quitting.
Has anyone a guess how to solve this?

Hi @Mykle1,
great module! Is it also possible to show only the days left? It’s kind of useless to show for example seconds until a specific date (vacation, birthday,…) :-)
Maybe you could add an option in the config to display only dd or dd:hh or dd:hh:mm.

I use crontab and added
@reboot tvservice -o to deactivate hdmi output on start. You can activate it on demand (as I do) or maybe after 60 seconds

well something strange I noticed… (don’t know if that’s related)
My Desktop used to be PIXEL I think (this nice road wallpaper and menu bars at the top. Now it looks like it is running Openbox. I don’t know how this happened, but it was not intended by me. Was that changed in the newest version because of my upgrades?

I did use CTRL + ALT + RIGHT or LEFT, but that didn’t helped either. Only change was that in the middle of the VNC-session was a small blue notification saying Desktop 1 so I suppose I have only one virtual desktop active.

trying your script or chvt 6 [or 7] manually does result in this error:

Konnte keinen Dateideskriptor finden, der auf die Konsole verweist.

The monitor is turning on correctly and I can see the background dark grey in the mirror, but it simply does not show the mirror. Maybe it somehow has multiple desktops defined and just showing the wrong on hdmi output…

well that didn’t worked. I still only see a black monitor. I did also reinstall MagicMirror and connected to it via VNC. Strange thing is that I can see my MM on my VNC client, but not on my monitor. I didn’t even thought this would be possible…

ok, I found a simply way to make chromium start in full screen mode, but how do I have to disable electron from entering full screen?

ok I did use npm remove, but on installing electron@1.7.9 I got this:

pi@Spieglein:~/MagicMirror $ npm install electron@1.7.9

> electron@1.7.9 postinstall /home/pi/MagicMirror/node_modules/electron
> node install.js

events.js:160
      throw er; // Unhandled 'error' event
      ^

Error: EIO: i/o error, read
    at Error (native)
npm ERR! Linux 4.14.44-v7+
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install" "electron@1.7.9"
npm ERR! node v6.14.2
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE

npm ERR! electron@1.7.9 postinstall: `node install.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the electron@1.7.9 postinstall script 'node install.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the electron package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node install.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs electron
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls electron
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/pi/MagicMirror/npm-debug.log

I tried to use only npm install and see what version it installes:

pi@Spieglein:~/MagicMirror $ npm install

> electron@1.8.7 postinstall /home/pi/MagicMirror/node_modules/electron
> node install.js


> magicmirror@2.3.1 install /home/pi/MagicMirror
> cd vendor && yon install

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})

> magicmirror@2.3.1 postinstall /home/pi/MagicMirror
> sh installers/postinstall/postinstall.sh && yon run install-fonts

MagicMirror installation successful!

> magicmirror@2.3.1 install-fonts /home/pi/MagicMirror
> cd fonts && yon install

magicmirror@2.3.1 /home/pi/MagicMirror
└─┬ electron@1.8.7
  ├── @types/node@8.10.19
  └─┬ electron-download@3.3.0
    ├─┬ fs-extra@0.30.0
    │ └── klaw@1.3.1
    ├── home-path@1.0.6
    └─┬ sumchecker@1.3.1
      └── es6-promise@4.2.4

So version 1.8.7 installes without problem but doesn’t work. Any further ideas?

what do you mean with uninstall? I did remove ~/MagicMirror/node_modules/electron and reinstalled via npm install in the MagicMirror folder. But still black screen.

Hey there,

up to yesterday my mirror worked fine. I did install a few modules (to name them MMM-Remote-Control and MMM-forecast-io) and prepared to install facial recognition. For this last point I followed the instructions on github MMM-Facial-Recognition-OCV3. I did the following:

sudo apt-get update
sudo apt-get upgrade
sudo rpi-update
sudo reboot
sudo apt-get install build-essential git cmake pkg-config
sudo apt-get install libjpeg-dev libtiff5-dev libjasper-dev libpng12-dev
sudo apt-get install libavcodec-dev libavformat-dev libswscale-dev libv4l-dev
sudo apt-get install libxvidcore-dev libx264-dev
sudo apt-get install libgtk2.0-dev
sudo apt-get install libatlas-base-dev gfortran
cd ~
git clone https://github.com/Itseez/opencv.git
cd opencv
git checkout 3.3.0
cd ~
git clone https://github.com/Itseez/opencv_contrib.git
cd opencv_contrib
git checkout 3.3.0
wget https://bootstrap.pypa.io/get-pip.py
sudo apt-get install python3-dev
sudo python3 get-pip.py

I did not yet started building OpenCV. After that I noticed my mirror turned black (didn’t checked inbetween these steps). Just to check I disabled the modules installed since last known working condition, but without success. I only checked the modules after installing from both my Windows pc and my smartphone. That worked fine at all times.
My suspicion is that the updating in the beginning of MMM-Facial-Recognition-OCV3 did break something.
I tried npm install electron@1.4.15 and checked the logs, but there is no entry. My node is version 6.14.2 and npm is 3.10.10
Can anyone give me a hint on what to check for?

Best regards,
Anduril

Hey,

up to now my MagicMirror was only in test mode and accessed via browser. Now I wanted to install it with a monitor on my mirror. If the RPi is not connected to HDMI, it works great. But as soon as I connect it and reboot it does not work. I can see the bootup of the RPi and a splash screen of MagicMirror saying “booting up”, but after that only a period of time a black cross and than the desktop. I also can not connect via browser, so MM is definetly not running. I will append the ~/MagicMirror/npm-debug.log
pm2 is listing MagicMirror as running.
When I disconnect the HDMI and reboot it works again from my browser. Can anyone please help?

0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'start' ]
2 info using npm@3.10.10
3 info using node@v6.13.0
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle magicmirror@2.2.2~prestart: magicmirror@2.2.2
6 silly lifecycle magicmirror@2.2.2~prestart: no script for prestart, continuing
7 info lifecycle magicmirror@2.2.2~start: magicmirror@2.2.2
8 verbose lifecycle magicmirror@2.2.2~start: unsafe-perm in lifecycle true
9 verbose lifecycle magicmirror@2.2.2~start: PATH: /usr/lib/node_modules/npm/bin/node-gyp-bin:/home/pi/Magic$
10 verbose lifecycle magicmirror@2.2.2~start: CWD: /home/pi/MagicMirror
11 silly lifecycle magicmirror@2.2.2~start: Args: [ '-c', 'sh run-start.sh' ]
12 silly lifecycle magicmirror@2.2.2~start: Returned: code: 1  signal: null
13 info lifecycle magicmirror@2.2.2~start: Failed to exec start script
14 verbose stack Error: magicmirror@2.2.2 start: `sh run-start.sh`
14 verbose stack Exit status 1
14 verbose stack     at EventEmitter. (/usr/lib/node_modules/npm/lib/utils/lifecycle.js:255:16)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at EventEmitter.emit (events.js:191:7)
14 verbose stack     at ChildProcess. (/usr/lib/node_modules/npm/lib/utils/spawn.js:40:14)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at ChildProcess.emit (events.js:191:7)
14 verbose stack     at maybeClose (internal/child_process.js:920:16)
14 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:230:5)
15 verbose pkgid magicmirror@2.2.2
16 verbose cwd /home/pi/MagicMirror
17 error Linux 4.9.35-v7+
18 error argv "/usr/bin/node" "/usr/bin/npm" "start"
19 error node v6.13.0
20 error npm  v3.10.10
21 error code ELIFECYCLE
22 error magicmirror@2.2.2 start: `sh run-start.sh`
22 error Exit status 1
23 error Failed at the magicmirror@2.2.2 start script 'sh run-start.sh'.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the magicmirror package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error     sh run-start.sh
23 error You can get information on how to open an issue for this project with:
23 error     npm bugs magicmirror
23 error Or if that isn't available, you can get their info via:
23 error     npm owner ls magicmirror
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]

Hey there,

I have this running for quite some time and it works in general. But after some hours it gets really slow and unresponsiv. A motion need a few seconds before it is detected. I already have enabled a daily reboot, but still these few hours are enough. I also tried only restarting motion via pm2, but this leads to problems. I checked it with pm2 monit and got this:

motion > [0] [NTC] [ALL] main: Waiting for threads to finish, pid: 13536 
motion > [1] [NTC] [ALL] motion_init: Thread 1 started , motion detection Enabled
motion > [1] [ALR] [VID] mmalcam_start: MMAL Camera thread starting... for camera (vc.ril.camera) of 640 x 480 at 4 fps
motion > [1] [ALR] [VID] mmalcam_start: MMAL Camera using video capture
motion > [0] [ERR] [ALL] main: Thread 1 - Watchdog timeout, trying to do a graceful restart
motion > [0] [ERR] [ALL] main: Thread 1 - Watchdog timeout, did NOT restart graceful,killing it! 
motion > [0] [NTC] [STR] stream_stop: Closing motion-stream listen socket & active motion-stream sockets 
motion > [0] [NTC] [STR] stream_stop: Closed motion-stream listen socket & active motion-stream sockets
motion > [0] [INF] [ALL] motion_cleanup: Calling vid_close() from motion_cleanup 
motion > [0] [INF] [VID] vid_close: calling video source cleanup 
motion > [0] [ALR] [VID] MMAL Camera cleanup 
motion > /home/pi/motion.sh: Zeile 2: 13536 Speicherzugriffsfehler  (Speicherabzug geschrieben) ./motion -c motion.conf
PM2 > App [motion] with id [0] and pid [13532], exited with code [139] via signal [SIGINT] 
PM2 > Starting execution sequence in -fork mode- for app name:motion id:0
PM2 > App name:motion id:0 online
motion > [0] [NTC] [ALL] conf_load: Processing thread 0 - config file motion.conf
motion > [0] [NTC] [ALL] motion_startup: Motion mmaltest Started 
motion > [0] [NTC] [ALL] motion_startup: Logging to syslog 
motion > [0] [NTC] [ALL] motion_startup: Using log type (ALL) log level (INF)
motion > [0] [NTC] [ENC] ffmpeg_init: ffmpeg LIBAVCODEC_BUILD 3670272 LIBAVFORMAT_BUILD 3670272
motion > [0] [NTC] [ALL] main: Thread 1 is from motion.conf
motion > [0] [NTC] [ALL] main: Thread 1 is device: /dev/video0 input -1
motion > [0] [NTC] [ALL] main: Stream port 8081
motion > [0] [NTC] [ALL] main: Waiting for threads to finish, pid: 13583 
motion > [1] [NTC] [ALL] motion_init: Thread 1 started , motion detection Enabled
motion > [1] [ALR] [VID] mmalcam_start: MMAL Camera thread starting... for camera (vc.ril.camera) of 640 x 480 at 4 fps
motion > [1] [ALR] [VID] mmalcam_start: MMAL Camera using video capture

Can anyone suggest how to correctly restart motion?