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
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?
@wswenson Wow, that is very cool, it would be perfect for the disney hotels :-) We live 14 hours away from the nearest disney park (Disneyland Paris), so I guess for us, the wait times would have changed too much :-D
Now if only Tivoli in Copenhagen would offer an api, that would be great for us :-)
@fribse Ok, that is weird, after doing the force, and waiting for quite a while, it works again???
So I’m changing it to solved, running the update once more, with “force”, made it work
It’s running on a RPi3B+
I upgraded from 2.22 using the sdetweil script, and it went through it without errors.
If I ask pm2 MagicMirror is online.
The log file looks like this:
pi@bathmirror:~/MagicMirror $ 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 | > magicmirror@2.23.0 start
0|MagicMir | > DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js
0|MagicMir |
0|MagicMir |
...
/home/pi/.pm2/logs/MagicMirror-error.log last 15 lines:
0|MagicMir | [30079:0526/061428.523308:ERROR:node_bindings.cc(552)] Failed to initialize node environment in process: browser , with error: Uncaught SyntaxError: Unexpected token ':'
0|MagicMir | /home/pi/MagicMirror/node_modules/electron/dist/electron exited with signal SIGSEGV
...
I don’t think it’s the ‘request’ thing, I did the search for request, and commented out all the modules that used that.
The config looks like this:
let config = {
address: "xxx",
port: 8080,
basePath: "/",
ipWhitelist: ["127.0.0.1", "::ffff:127.0.0.1", "::1","xxx/24"],
useHttps: false, // Support HTTPS or not, default "false" will use HTTP
httpsPrivateKey: "", // HTTPS private key path, only require when useHttps is true
httpsCertificate: "", // HTTPS Certificate path, only require when useHttps is true
language: "da",
locale: "da-DK",
logLevel: ["INFO", "LOG", "WARN", "ERROR"], // Add "DEBUG" for even more logging
timeFormat: 24,
units: "metric",
modules: [
// {
// module: "MMM-ModuleScheduler",
// config: {
// global_schedule: [
// {from: "0 5 * * *", to: "0 10 * * *", groupClass: "morning_schedule"},
// {from: "0 18 * * *", to: "0 23 * * *", groupClass: "evening_schedule"},
// {from: "0 5 * * 1-5", to: "0 10 * * 1-5", groupClass: "weekday_morning_schedule"},
// {from: "0 6 * * *", to: "0 20 * * *", groupClass: "day_schedule"},
// {from: "0 0 * * 1-5", to: "59 23 * * 1-5", groupClass: "weekdays_schedule"},
// {from: "30 5 * * *", to: "59 23 * * *", groupClass: "complimenttime"}
// ]
// }
// },
{
module: "alert",
},
{
module: "updatenotification",
position: "top_bar"
},
{
module: "clock",
position: "top_left"
},
{
module: "calendar",
header: "Kalenderdage",
position: "top_left",
classes: "day_schedule small",
config: {
maximumEntries: 6,
fetchInterval: 12000000 ,
calendars: [
{
symbol: "calendar-check",
url: "https://calendar.google.com/xxx"
// url: "https://www.google.com/xxx"
// url: "webcal://p01-calendarws.icloud.com/ca/subscribe/1/IsLh6fUURb4n_nA6vhWYUmlEe98rz2BN8BhioUPzrC2HVohwJIUCbGuGeTwczZWvXjTqU7vicBATXHojb1p5fn8ub3RCBUwKfHm3jXJDzFE"
}
]
}
},
{
module: "compliments",
position: "lower_third",
classes: "complimenttime bold xlarge bright",
config: {
remoteFile: "xxx",
updateInterval: 120000,
morningStartTime: 05,
morningEndTime: 10,
afternoonStartTime: 15,
afternoonEndTime: 18,
}
},
{
module: "weather",
position: "top_right",
classes: "day_schedule",
config: {
weatherProvider: "openweathermap",
type: "current",
units: "metric",
timeFormat: 24,
decimalSymbol: ",",
initialLoadDelay: 0,
onlyTemp: false,
locationID: xxx,
apiKey: "xxx"
}
},
{
module: "weather",
position: "top_right",
classes: "day_schedule",
config: {
weatherProvider: "openweathermap",
type: "forecast",
units: "metric",
timeFormat: 24,
decimalSymbol: ",",
initialLoadDelay: 0,
onlyTemp: true,
maxNumberOfDays: 7,
colored: true,
appendLocationNameToHeader: false,
locationID: xxx,
apiKey: "xxx"
}
},
{
module: "newsfeed",
position: "bottom_bar",
classes: "day_schedule",
config: {
feeds: [
{
title: "Ekstra Bladet",
url: "https://ekstrabladet.dk/rssfeed/all/"
},
{
title: "DR nyheder",
url: "https://www.dr.dk/nyheder/service/feeds/allenyheder"
},
{
title: "BT",
url: "https://www.bt.dk/bt/seneste/rss"
},
{
title: "Berlingske.dk",
url: "https://www.berlingske.dk/content/3/rss"
},
{
title: "TV2 Øst",
url: "https://www.tv2east.dk/rss"
}
],
updateInterval: 30000,
showSourceTitle: true,
showPublishDate: true,
broadcastNewsFeeds: true,
broadcastNewsUpdates: true
}
},
{
module: "MMM-News-QR",
position: "bottom_bar",
classes: "day_schedule",
config: {
updateType : "push",
animationSpeed: 2500,
colorDark: "#fff",
colorLight: "#000",
imageSize: 100
}
},
{
module: "MMM-Remote-Control",
config: {
apiKey: 'xxx',
showModuleApiMenu: true,
pm2ProcessName: 'MagicMirror',
},
},
// {
// module: "MMM-Screencast",
// position: "'bottom_right", // This position is for a hidden <div /> and not the screencast window
// config: {
// position: "bottomRight",
// castName: "Spejl",
// height: 300,
// width: 500,
// }
// },
// {
// module: "MMM-MyCommute",
// position: "bottom_right",
// classes: "xsmall",
// header: "Trafik",
// config: {
// apiKey: "xxx",
// startTime: "05:00",
// endTime: "12:00",
//// hideDays: [0,6],
// origin: "xxx",
// destinations: [
// {
// destination: "xxx",
// label: "xxx",
// mode: "driving",
// color: "#82E5AA"
// },
// {
// destination: "xxx",
// label: "xxx",
// mode: "driving",
// color: "#82E5AA"
// }
// ]
// }
// },
]
};
/*************** DO NOT EDIT THE LINE BELOW ***************/
if (typeof module !== "undefined") {module.exports = config;}
I tried running the upgrade again, with force, it didn’t help, and this is the output
pi@bathmirror:~/MagicMirror $ bash -c "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)" force
doing test run = false
update log will be in /home/pi/MagicMirror/installers/upgrade.log
Check current Node installation ...
Node currently installed. Checking version number.
Minimum Node version: v16.13.1
Installed Node version: v16.15.1
No Node.js upgrade necessary.
Check current NPM installation ...
NPM currently installed. Checking version number.
Minimum npm version: V7.11.2
Installed npm version: V8.11.0
No npm upgrade necessary.
saving custom.css
upgrading from version 2.23.0 to 2.23.0
fetching latest revisions
updating MagicMirror runtime, please wait
> magicmirror@2.23.0 postinstall
> npm run install-vendor && npm run install-fonts && echo "MagicMirror² installation finished successfully!
> "
> magicmirror@2.23.0 install-vendor
> echo "Installing vendor files ...
> " && cd vendor && npm install --loglevel=error --no-audit --no-fund --no-update-notifier
Installing vendor files ...
up to date in 17s
> magicmirror@2.23.0 install-fonts
> echo "Installing fonts ...
> " && cd fonts && npm install --loglevel=error --no-audit --no-fund --no-update-notifier
Installing fonts ...
up to date in 3s
MagicMirror² installation finished successfully!
> magicmirror@2.23.0 prepare
> [ -f node_modules/.bin/husky ] && husky install || echo no husky installed.
no husky installed.
added 325 packages, changed 1 package, and audited 327 packages in 3m
80 packages are looking for funding
run `npm fund` for details
2 vulnerabilities (1 moderate, 1 high)
To address all issues, run:
npm audit fix
Run `npm audit` for details.
Checking for modules with removed libraries
processing dependency changes for active modules with package.json files
processing for module MMM-Remote-Control please wait
----------------------------------
npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
added 40 packages, and audited 41 packages in 15s
8 packages are looking for funding
run `npm fund` for details
found 0 vulnerabilities
processing complete for module MMM-Remote-Control
restoring custom.css
@doctore Ok, I’ll try to see if that works, thankyou!
@kayakbabe Yes, I’m referring to /boot/config.txt, not Magicmirror/config/config.yaml :-)
@N6NG Ok, and what are you writing in the config for it to work? That would be a big help for me :-)
@fribse Ok, so now I’ve gotten a second RPi3b+. Apparently the monitor doesn’t like the way that Bullseye rotate the screen (by using the ‘Screen orientation’ in the GUI).
So how do I rotate the screen in ‘the old way’ which works fine on the monitor.
My guess is that it’s modifying the refresh rate beyond the capabilities of the monitor.
It’s usually running on 60Hz, and I tried changing it to 50Hz, but that didn’t change anything.
So what do I do now? I would really like to use the bullseye, as I can’t get Home Assistant to control the mirror if I have screencast installed on the mirror under Buster.
@fribse Hmm, can’t make this work. I can get it to work on a RPi4, but not on a RPi3 with the ‘Screenconfiguration’ app.
It’s really annoying, I would like to have screencast and remote-control modules enabled, so that Home Assistant can integrate to it, through the remote-control module, but that doesn’t work on Buster (the integration fails to set up), it fails because of some weird problem in the integration combined with the screencast, which the author can’t reproduce, which is very odd, as I can show it every time.
I can get the integration to work on Bullseye together with the remote-control module and the screencast, but not on a RPi3, only on a RPi4, and even rotate the screen, but I don’t want to place a very hot and overly powerfull RPi4 behind the magicmirror.
Damned if I do, and damned if I don’t.
@BKeyport That is worth a try, didn’t think of that!
@sdetweil That would be odd, as it works with previous versions of Raspberry Pi OS?