@sdetweil Good to note that it don’t always work, FWIW… like it don’t help my situation, but, I only have to restart once in a great while now, so, I don’t see it nearly as much… now if I could get OMX to stop freezing so I don’t have to restart it every half hour (😭😭😭 not a magic mirror problem, Running it on top of MM to avoid RTSPStream bugs)
I’ve added the following line to /etc/xdg/lxsession/LXDE-pi
@xrandr --output HDMI-1 --rotate right
YMMV, you might have to fiddle with it to suit your rotation and output.
@BKeyport I just pushed some changes for the next release to autodetect the custom regions in index.html and use those for validating and using in config.js
(and npm run check:config)
There’s a REALLY simple way to do this using a script and a cron job.
From the pi user, execute:
sudo nano /bin/mmreload.sh
Paste the following contents into that file:
#!/bin/sh
if [ /home/pi/MagicMirror/config/config.js -nt /home/pi/.pm2/pids/mm-0.pid ]; then
/usr/bin/pm2 restart mm
fi
Save it (CTRL-X) and then give it execute permissions like this:
sudo chmod +x /bin/mmreload.sh
From the pi user, execute the following:
crontab -e
In the crontab file, add the following line:
0,30 * * * * /bin/mmreload.sh > /dev/null 2>&1
Save the file (CTRL-X if you’re using nano).
This will check the MM ‘pid’ file against the config.js file to see if the configuration file has been edited since the mirror was last started (it will check at the top and bottom of every hour). If the config file has been edited, it will restart MM and use the new configuration file.
@chassain-0 it says you must have done the git pull before doing the upgrade-script…
(already at 2.10.0 when script started)
test doesn’t change any files, but apply runs were aborted as the installed version was already at 2.10.0, so no npm install was done by script
@Clubjack and others,
I noticed this problem too.
For instance my birthday lasted 2 days ( only got presents once though) and my wedding-day is one day forward (which will upset my wife).
The entries were made using Google Calendar (so not a calendar app that synchronizes with Google).
I notice this since 2020, but that does not mean it did not happen before, could have overlooked it.
When I ran a test with a dummy entry, it worked fine.
When I toggle a „faulty“ entry from repeating to not repeating and then back to repeating, the entry is shown correct.
I collected some data and will post it when I sorted it out a bit.
@BKeyport
Like this?
[image: 1558339634709-transform.png]
You can do it with MMM-CalendarExt2 (MMM-CalendarExt could also do that but with different mechanism)
With MMM-CalendarExt2,
you can transform data of event before display it.
transform: (event)=>{
event.icon = "fa-solid:user-secret"
event.title = "My Secret"
return event
}
See https://github.com/eouia/MMM-CalendarExt2/wiki/Filtering-and-Sorting#transforming
The Mirropane available in the US (the one you linked to) with a light transmission of 11% and one reflective side of 68% is theoretical (and in my oppinion) a perfect fit for a magicmirror in normal lighting conditions (not daylight/sunny locations).
I’m aware there’s too many commas by ‘traditional thinking’ - but I kept getting config errors without it.
This was the default config, modified for testing.
So, it does the same thing now with my other magic mirror install.
The other unit is on a 7" touchscreen, I have it alternating between the Weather module and the Weather Forcast module.
Offline
