I completed my box construction yesterday. My solution to the monitor-is-smaller-than-box problem was to build an internal bracing system using a couple of channels for the edge of the monitor. It sounds more complicated than it is.

Monitor braces:

Everything in place:

@BlackTalon I don’t think so, no. I’m running this on either my development PC, my work desktop or a microPC. Win10 or Ubuntu 16, respectively.

It looks like the electron browser thingy doesn’t support some of the commands used by the module. Possibly. We may need a workaround. Still investigating.

Everyone! Please, use the Markdown features of the forum when posting code.

@rasmus-rytter said in 24 Hour clock problem:

Everything has gone except of the clock?

Looking at your config.js file, you are missing the code to include the clock module entirely. @Mykle1 has it correct: It’s best at this point to copy the config.js.sample file to config.js and just start from a known working baseline.

@artworks79 Sure, no problem.
For starters, you probably copied the config.js.sample file to config.js to get you started. That’s great, as the config.js file is what the Magic Mirror software reads in order to arrange and configure the various modules. For future installations, I recommend making a local copy of the config.js file and then dropping that in your new mirrors.

In the config.js file, you’ll see an entry for the compliments module that tells the system which module to load (compliments), where to place it and what configuration values to pass into the module (config: {...}). This part of the config.js file modifies how the Magic Mirror software treats the compliments module.

Inside that config section, you can modify the behavior of the module itself. You can change the update interval or change the compliments themselves. Here’s the one pulled from my config.js.

{
        module: 'compliments',
        position: 'bottom_center',
        config: {
                updateInterval: 30000,
                compliments: {
                        morning: [
                        "Good morning, sunshine!"
                                        ],
                        afternoon: [
                        "It's a pretty day outside. Go play in it!"
                                        ],
                        evening: [
                                "Wasn't the sunset beautiful?",
                                "Wasn't the day just spectacular?"
                                ]
                        }
                }
        },

Inside the config: {...} section there is a variable called compliments. The value of this variable must be an array, as specified by the morning: [...] structure. Please note that arrays require square brackets. Each compliment must be enclosed in double quotes " and each compliment is separated by a comma. You can have as many compliments as you like in each array. In the compliments:{...} variable you are allowed a morning array, an afternoon array and an evening array. No other array names will have any effect.

I experimented with this a bit yesterday. Thanks to @rvdgeer for the hint and @Jopyth for the initial code to start.

I ripped a YouTube video to disk and uploaded it to my Pi, putting it in the vendor folder. Adding this to my config.js was surprisingly effective (the rotate 90 is due to the video being designed to be projected on a window):

{     module: "helloworld",
      position: "fullscreen_below",  
      config: {
                text: "<video src='vendor/halloween.mp4' autoplay loop style='transform:rotate(90deg); position:absolute; top:50%;left:30%; height:50%'></video>"
               }
 },

@Mitchfarino I did something similar with my mirror. I ended up routing a channel in two pieces that spanned in the interior of the box. The monitor edges fit in the channel and a couple of corner brackets secured each piece to the interior of the box. If you weren’t too concerned with visible screws on the outside of your box, you could skip the corner brackets for driving screws into the monitor supports from the outside.

@BlackTalon Interesting. Thanks for figuring out the issue.

Question: I could load this on the Raspberry Pi 3 at the office and then take a video of the end result. Would that be interesting to the community? Or should we just call this a greater-than-raspberry module?

@valid8r - My suggestion is to install the latest version of node separately and then run the installation script. Try npm install npm@latest -g to install the latest version of the Node Package Manager (npm).

Once that completes, try the MagicMirror installations script again and let us know what happens.

cd ~
bash -c "$(curl -sL https://raw.githubusercontent.com/MichMich/MagicMirror/master/installers/raspberry.sh)"

@bibi I haven’t tried it with a USB cam, but it should work. In the config file, there is a switch to throw if you’re using a USB cam (and different switches to throw if you’re using a network cam - which raises interesting possibilities).

My camera is mounted above the monitor & behind the one-way acrylic. My monitor is smaller than my acrylic by about 2" on a side. This is good in that it’s a very clean installation and you don’t see a camera when you look at the mirror. It’s bad in that it cuts down on the light reaching the camera, preventing the facial recognition from working.

Virginia, USA