So we have our Magic Mirror set up in the bathroom.
At halloween it is going to show an extra surprise.

We control everything here with Home Assistant, so 15s after the light is turned on in the bathroom, the light will go out, some will start flickering, and the buttons for controlling the light will not work.

This is how it’s going to look like:

So it’s assembled, just need to protect the wood from moisture.

The ‘behind the mirror’ lights are working nicely, it’s based on WLED, the LED’s inside are SK6812, so it has very nice white, as well as RGB.
And then I off course need to polish the mirror
It’s going to be set up before halloween, and I already have videos of ghosts ready and tested

So far the frame is built, with the monitor mounted (19" LG). It has a 12V PSU, with a buckconverter for the RPi3, and a USB hub for the USB soundcard (and also gives the possibility of adding a USB keyboard to it without twisting fingers.
The reason for the 12V PSU is that I’m awaiting delivery of my 2x10W speakers, and a stereo 15" amplifier that will be added to the mirror as well.

I sent the oracal back (very expensive stuff) as I could get much cheaper and darker stuff from our local hardware store.
So I got the back covered with it, and then cut holes in it for the LED lights and monitor, it seems to work very well.

Ok, finally I found the right module. So the remote module in MagicMirror (MMM-Remote-Control), and then ‘rest_command:’ setup in HA.
That way the motionsensor can turn the screen on and off in the mirror. For now I’ve made it simple with just defining four commands, two for on / off and two for dim / undim. And then just use those services in HA automations.
Works perfectly.
Now I need to turn some modules on and off depending on the time of day.

The HA commands:

rest_command:
  turn_off_mm_screen:
    url: http://IP:8080/api/monitor/off
  turn_on_mm_screen:
    url: http://IP:8080/api/monitor/on
  dim_mm_screen:
    url: http://IP:8080/api/brightness/75
  undim_mm_screen:
    url: http://IP:8080/api/brightness/100

One of the automations (at night)

- id: '1557033756115'
  alias: Turn on bathroom light at night
  trigger:
  - entity_id: binary_sensor.bathroom_movement
    from: 'off'
    platform: state
    to: 'on'
  condition:
  - after: '23:00'
    before: '7:59'
    condition: time
  - condition: state
    entity_id: light.spejl
    state: 'off'
  action:
  - data:
      brightness_pct: 10
      entity_id: light.spejl
    service: light.turn_on
  - data: {}
    service: rest_command.turn_on_mm_screen
  - data: {}
    service: rest_command.undim_mm_screen

Next step would be to modify rest_command so that I don’t have one for each action, but send a payload that is modified to the command that I want.

So, things are shaping up, I’ve gotten the mirror rebuilt, I had to swap the monitor, it was getting too hot.
The new one is much cooler.
I also got the lights mounted, it’s a mixture of fun and serious, it will give light for usage, but it’s also RGB, so it can do effects if we want to
This image shows the lights turned to it’s lowest (apart from being off, of course. The foil is still on, until I get the mirror properly fixed to the frame, it has the foil on.

@bendonahue I’ve set it up here with MQTT.
I wrote a small guide on the HA forum:
https://community.home-assistant.io/t/magicmirror-integration-into-home-assistant-with-mqtt/177246/15

@JerryP said in I can't get mmm-screencast to work:

nam install

Is that a new command?

I got it through the ‘community order’ on this page.
The reflectance is very good, it’s a real mirror.
My only problem with it, is that the chroma of it is a bit brown, so it requires quite a lot of light in the room.

@klinge you are tying it to localhost only? If you do that, you can’t connect to it, it should be 0.0.0.0 or something like that?

I was on 2.18, and got a notification that there was a new version, and today I finally tried to update it, and now I see this message in the logfile
0|MagicMirror | sh: 1: ./node_modules/.bin/electron: not found

The software is installed with @sdetweil 's script originally.

What to do?

@sdetweil Ok, good to know, so at least it’s not them making problems for MMM-ScreenCast and MMM-RemoteControl.

So I did a new install completely from scratch on a Raspbian Buster, and did a ‘manual’ install this time, still same error:

[25.02.2022 16:00.46.615] [LOG] Launching application.
[1789:0225/160048.427469:ERROR:viz_main_impl.cc(161)] Exiting GPU process due to errors during initialization
[1828:0225/160048.917933:ERROR:sandbox_linux.cc(376)] InitializeSandbox() called with multiple threads in process gpu-process.

Monitor is in portrait mode, these settings are in boot/config.txt

display_rotate=1
enable_uart=1
avoid_warnings=1

Hi Guys

I’m having some problems with the installation.
I’ve done a brand new Raspbian Buster install.
Fully updated.
I then ran @sdetweil 's install script.

I’m now modifying the module config one by one, and installing the custom modules.

I’ve yet to install a custom module, so far I have changed the software to da-DK, I’ve made the compliments module fetch my gist compliments file, and I’ve changed the calendar module to use a danish provider.

I already see these two messages:

0|MagicMirror  | [3635:0225/103036.868905:ERROR:viz_main_impl.cc(161)] Exiting GPU process due to errors during initialization
0|MagicMirror  | [3680:0225/103037.331723:ERROR:sandbox_linux.cc(376)] InitializeSandbox() called with multiple threads in process gpu-process.

@fribse I just did another video for valentines

@lhops Try to log your temperature, the reboot sounds like a temp issue.
It would also suit the PiR that registers a rising temperature.

I live in CEST timezone, and I fear that is part of the problem.
I have a config like this for the module:

{
                        module: "MMM-MyCommute",
                        position: "bottom_right",
                        classes: "xsmall",
                        header: "Trafik",
                        config: {
                                apiKey: "xxx",
                                startTime: "05:00",
                                endTime: "12:00",
                                hideDays: [0,6],
                                origin: "Home",
                                destinations: [
                                        {
                                                destination: "Address1",
                                                label: "Company1",
                                                mode: "driving",
                                                color: "#82E5AA"
                                        },
                                        {
                                                destination: "Address2",
                                                label: "Company2",
                                                mode: "driving",
                                                color: "#82E5AA"
                                        }
                                ]
                        }
                },

My hope was that it would be active between 5 in the morning and midday, and not show up in weekends.
But this morning (tuesday) it diedn’t show up at around 8.

Has anybody else gotten this to work, and is there a trick to it?

@fribse Nope, just removed it and booted the mirror, still seeing those…

@sdetweil Glad to show you something new
I wonder if it’s the

gpu_mem=128

in boot/config.txt
?

Well, after doing a reinstall, module for module, it’s working with everything except that the Screencast module interferes with the remote module for the Home Assistant Integration (which uses the remote module).

So a success for now, and then I hope the integration to HA will get working.
Thans @sdetweil and @bugsounet !

@karsten13 I would normally agreee, but this is only to satisfy weird demands on SSL, not for any form of security and the mirror is not externally available.