@feigi Hmm… I’ll have to test on my test rig tomorrow, maybe something is broken… What are you running on? I have not tried it on a RPi, so I don’t know if the Pi can handle the video-tag correctly… Is there anyone else here who can test it on a Pi? :)

Hi, I had the same issue when I built my mirror… Here is how I solved it. Made a .sh script with all the information: :)

#!/bin/bash

# Before I just tested with the xinput command directly in the autostart file, but that did not work. So now instead I just created a script called xin.sh.
# nano ~/xin.sh
# Then added
# DISPLAY=:0.0 xinput --set-prop "Multi touch Multi touch overlay device" "Coordinate Transformation Matrix" 0 1 0 -1 0 1 0 0 1
# There should actually be 3 spaces between “Multi touch” and “Multi touch overlay device”. For some reason the board removes the extra spaces here.
#
# You can actually find the “name” of the device with this command form a console: DISPLAY=:0.0 xinput list
# Shows something like this:
#
# Virtual core pointer id=2 [master pointer (3)]
#   Virtual core XTEST pointer id=4 [slave pointer (2)]
#   Multi touch Multi touch overlay device id=6 [slave pointer (2)]
# Virtual core keyboard id=3 [master keyboard (2)]
# Virtual core XTEST keyboard id=5 [slave keyboard (3)]
#
# Depending on what you have connected to your RPi. 🙂
# 
# So, after creating the xin.sh I added that to the autostart file for LXDE:
# Like this:
# nano ~/.config/lxsession/LXDE-pi/autostart
# Added at the end of the file.
# @/home/pi/xin.sh
# Restarted and it works.
#
DISPLAY=:0.0 xinput --set-prop "Multi touch   Multi touch overlay device" "Coordinate Transformation Matrix" 0 1 0 -1 0 1 0 0 1

Maybe you guys can use it some how? :)

Description:

This Module adds a video player in any of the regions, you define what files to play.

Screenshots:

Simple video showing the module when playing a video and whats happen when hiding / showing it.

Download:

https://github.com/Snille/MMM-Videoplayer

Custom-CSS

If you want to change the size of the player.

.MMM-Videoplayer video {
    width: 1080px;
    height: 1920px;
}

Tip:
Let’s say run the module in “fullscreen_below” and have a mirror in portrate mode (as in the CSS example above). You many want to turn the player 90 degrees…
Then set the CSS to:

.MMM-Videoplayer video {
    width: 1080px;
    height: 1920px;
    -moz-transform:rotate(90deg);
    -webkit-transform:rotate(90deg);
    -o-transform:rotate(90deg);
    -ms-transform:rotate(90deg);
    transform:rotate(90deg);
}

Normally you just need to add the line:

    transform:rotate(90deg);

But for comparability reasons, you can add all of them. :)

And, as you will probably notice with the above CSS code. The video player will not really “fill” the whole background when you turn it 90 degrees. So, then you need to to this:

.MMM-Videoplayer video {
    position: absolute;
    transform:rotate(90deg);
    transform-origin: bottom left;
    width: 100vh;
    height: 100vw;
    margin-top: -100vw;
    object-fit: cover;
}

Also, if you have other stuff in the same region (in my case “fullscreen_below”), it’s a good idea to add the video module before any other module in the same region in the config, Then when you actually display the video module it pops up “on top of” all other stuff. :)

Version 0.4

• Added “hideonstart” - If set to true, the player will hide it self when a clip is loaded (and just started playing (clip will be paused when the player is hidden)). Then when the player is shown again it will continue play the clip and hide itself again when the next clip is loaded (and just starts playing) and so on…

Version 0.3

• Added more “notification” commands (“REPLAY” and “NEXT”).
• Also fixed so all videos will be played when in radom, before a video is played again (if in loop mode).

Version 0.2

• Added a video list option (you can define multiple video files).
• Added a option to “randomize” the videos played from the list.

Version 0.1

• Initial release.

@gaudouy Hi, no, it can only show and hide one/ or multiple instances of the same type of module on one button, but not two different types of modules on one button.

Added a video (two years later): https://youtu.be/2Hi9IDfrqPQ
The Mirror is used daily and I have upgraded from a RPi 3 to a NUC instead to get more CPU-Power to play with. :)

@sdetweil Thanks! :)

I could not find a “good enough” Home Assistant Module for the Mirror, so I forked and developed a bit on the one I thought worked the best.

Description:

Adds the defined Home Assistant Sensors to your Magic Mirror.

Screenshots:

Simplest possible:

Different pictures depending on values from the sensors (with some modified CSS):

Different icons depending on values from the sensors:

And here is my personal advanced “look”… :)

Download:

[card:Snille/MMM-homeassistant-sensors]

@ooskay Hi! I get this error to. What modules do you run in your mirror? I think it may be one of my modules causing the problem.

This is my list:
calendar_monthly
mm-hide-all
MMM-CalendarExt
MMM-Chart
MMM-cryptocurrency
MMM-Globe
MMM-iFrameReload
MMM-JSONStatusChecker
MMM-Memo
MMM-Modulebar
MMM-ModuleScheduler
MMM-MotionEye
MMM-MyCalendar
MMM-MyCommute
MMM-newsfeedtouch
MMM-plex-recently-added
MMM-Profilepicture
MMM-ProfileSwitcher
MMM-Remote-Control
MMM-Sonos
mmm-suncalc
MMM-TextClock
MMM-Tools
MMM-TouchNavigation
MMM-WunderGround

What do you have?

@andurii I get the same error message “Couldn’t get a file descriptor referring to the console” but the monitor turn on… :)

I have tow desktops as well, the Mirror shows up on one of them… I can use (in VNC) CTRL + ALT + Right or Left arrow key to switch between virtual desktops.

@andurii Hmm… Sounds like your monitor has gone to standby.
Login via SSH:

Make a sh file named: monitor.sh

Add the flowing to the file:

#!/bin/bash

if [ "$1" == 'on' ]; then
  tvservice -p;
  chvt 6;
  chvt 7;
fi

if [ "$1" == 'off' ]; then
  tvservice -o
fi

Then make it executable with: chmod +x monitor.sh
Turn on them monitor it like this: ./monitor.sh on
Turn it off like this: ./monitor.sh off

And of course, make sure you are on the correct input to actually see the Pi… :)

That should “turn on” (or off) the screen from SSH. :)