Offline
@lparco I have the same problem.
I installed the module and entered the following in the config
{
module: 'MMM-IQAir',
position: 'bottom_right',
config: {
key: 'kGdYrWay***********',
}
},
Unfortunately, no luck. It doesn’t even show it to me. What could be wrong?
Great, it worked. I have one more question.
Do I have to use the “calendar” module from MagicMirror, or would the MMM-MyCalendar module also work?
{
module: "MMM-MyCalendar",
position: "bottom_right", // This can be any of the regions. Best results in left or right regions.
header: 'Kalender Andreas',
config: {
colored: true,
maxTitleLength: 30,
maximumEntries: 4,
displayRepeatingCountTitle: true,
timeFormat: "HH:mm",
dateFormat: "DD:MM:YYYY",
joiningWord: "um",
calendars: [
{
url: 'https://calendar.google.com/calendar/ical/................./basic.ics',
color: "#5b53d4",
symbol: 'calendar',
auth: {
user: 'username',
pass: 'superstrongpassword',
method: 'basic'
}
},
],
}
},
{
module: "MMM-MyCalendar",
position: "bottom_right", // This can be any of the regions. Best results in left or right regions.
header: 'Kalender Daniela & Andreas',
config: {
colored: true,
maxTitleLength: 30,
maximumEntries: 4,
displayRepeatingCountTitle: true,
timeFormat: "HH:mm",
dateFormat: "DD:MM:YYYY",
joiningWord: "um",
calendars: [
{
url: 'https://calendar.google.com/calendar/ical/................./basic.ics',
color: "#f05db0",
symbol: 'calendar',
auth: {
user: 'username',
pass: 'superstrongpassword',
method: 'basic'
}
},
],
}
},
Hello everyone
I hope you can help me. I’m trying to get the calendar to display in Calendar Ext3.
This is what my configuration looks like
{
module: "calendar",
position: "top_left",
config: {
broadcastPastEvents: true, // <= IMPORTANT to see past events
calendars: [
{
url: "https://calendar.google.com/calendar/ical/....................ics",
name: "Andreas", // <= RECOMMENDED to assign name
color: "red" // <= RECOMMENDED to assign color
}
]
}
},
{
module: "MMM-CalendarExt3",
position: "bottom_bar",
title: "",
config: {
mode: "month",
instanceId: "basicCalendar",
locale: 'de-CH',
maxEventLines: 5,
firstDayOfWeek: 1,
calendarSet: ['Andreas'],
}
},
good day
I would like to have my 8 surveillance cameras (Unifi) displayed on a monitor. Therefore I heard myself that I have the MagicMirror or the mmm-rtspstream module for my project.
Enclosed my config:
{
module: "MMM-RTSPStream",
position: "top_left",
config: {
autoStart: true,
rotateStreams: true,
rotateStreamTimeout: 10,
moduleWidth: 354,
moduleHeight: 240,
localPlayer: 'omxplayer',
remotePlayer: 'none',
showSnapWhenPaused: true,
remoteSnaps: true,
stream1: {
name: 'Wald',
url: 'rtsp://IPCAM/42z4585742524dud1h',
frameRate: 'undefined',
snapshotType: 'url',
snapshotRefresh: 10,
width: undefined,
height: undefined,
},
}
},
{
module: "MMM-RTSPStream",
position: "top_right",
config: {
autoStart: true,
rotateStreams: true,
rotateStreamTimeout: 10,
moduleWidth: 354,
moduleHeight: 240,
localPlayer: 'omxplayer',
remotePlayer: 'none',
showSnapWhenPaused: true,
remoteSnaps: true,
stream1: {
name: 'Einfahrt',
url: 'rtsp://IPCAM/F5478u56hngdyzEYHt',
frameRate: 'undefined',
snapshotType: 'url',
snapshotRefresh: 10,
width: undefined,
height: undefined,
},
}
},
I see the picture linked, but the picture is outside the frame and I see nothing on the right.
Was I wrong?
Has worked so far, thanks.
Now the positions of the modules which are in the corners are no longer in the corners but are slightly offset against inside.
How can I, for example, bring my QR code module (MMM-EasyPix) to the outside, towards the edge of the screen?
@Stoffbeuteluwe Ok, thanks for the tip. I will try it tonight.
Oo cool, thank you :) coole Sache, weiter so ;)
What do I have to set that every 5 seconds the page change. I would like to always display the module MMM-BackgroundSlideshow and two modules are displayed on the page: MMM-NowPlayingOnSpotify, MMM-EasyPix, MMM-SystemStats, compliments.
That would be my configuration to the module and to the MMM Page Indicator
{
module: 'MMM-pages',
config: {
modules:
[[ "MMM-NowPlayingOnSpotify", "MMM-EasyPix"],
[ "MMM-SystemStats", "compliments" ]],
fixed: ["MMM-BackgroundSlideshow", "MMM-page-indicator"],
animationTime: 5000,
}
},
{
module: 'MMM-page-indicator',
position: 'bottom_bar',
config: {
pages: 2,
}
},
At the moment, only the first page is displayed
Yes, that’s really interesting. But since I let the pictures play with max 1-2 MB, the mirror was never black anymore. Although I did the elevation of SWAP.
Hi @sdetweil
Mhmmm sorry if I ask so stupid. How do I do that then I download the module from you …
So you suggest that I delete the module and download the specified links as “git”?
And sorry for the late reply. Lately there was a lot going on (baby, house building, etc.)
I seem to have found the mistake. I have selected one to quality of photos for playing the photos (4mb per photo). The fact that I have chosen a lower quality of the photos, the problem is gone.
This morning, the mirror was dark again.
This is the memory output
pi@raspberrypi_1:~ $ free -m
total used free shared buff/cache available
Mem: 925 220 391 1 313 653
Swap: 1023 118 905
Edit: The mirror was stopped and started and after 15min he was dark again …
@sdetweil said in MMM-BackgroundSlideshow:
free -m
Command will show memory usage
pi@raspberrypi_1:~ $ free -m
total used free shared buff/cache available
Mem: 925 218 404 1 302 657
Swap: 1023 111 912
@sdetweil said in MMM-BackgroundSlideshow:
and rebooted after changing swap file
I have now reboot the mirror …
Now I thought it was solved, but after about 1 hour the screen was black again. I had to stop the MagicMirror with pm2 stop 0 and then restart it with pm2 start 0.
I also changed the size from 100 to 1024.
What else can it be?
sudo dphys-swapfile swapoff
sudo nano /etc/dphys-swapfile / (changed size 1024)
sudo dphys-swapfile swapon
Here are the logs from /home/pi/.pm2/logs/mm-out.log
> magicmirror@2.8.0 start /home/pi/MagicMirror
> sh run-start.sh
Starting MagicMirror: v2.8.0
Loading config ...
Loading module helpers ...
No helper found for module: alert.
Initializing new module helper ...
Module helper loaded: updatenotification
Initializing new module helper ...
Module helper loaded: MMM-WatchDog
Initializing new module helper ...
Module helper loaded: MMM-Remote-Control
Initializing new module helper ...
Module helper loaded: MMM-SystemStats
Initializing new module helper ...
Module helper loaded: newsfeed
Initializing new module helper ...
Module helper loaded: MMM-MyCommute
Initializing new module helper ...
Module helper loaded: MMM-GoogleMapsTraffic
Initializing new module helper ...
Module helper loaded: MMM-DarkSkyForecast
Initializing new module helper ...
Module helper loaded: MMM-MyCalendar
All module helpers loaded.
Starting server on port 8080 ...
Server started ...
Connecting socket for: updatenotification
Connecting socket for: MMM-WatchDog
Starting module helper: MMM-WatchDog
Connecting socket for: MMM-Remote-Control
Starting node helper for: MMM-Remote-Control
Connecting socket for: MMM-SystemStats
Connecting socket for: newsfeed
Starting module: newsfeed
Connecting socket for: MMM-MyCommute
====================== Starting node_helper for module [MMM-MyCommute]
Connecting socket for: MMM-GoogleMapsTraffic
Starting node_helper for module: MMM-GoogleMapsTraffic
Connecting socket for: MMM-DarkSkyForecast
====================== Starting node_helper for module [MMM-DarkSkyForecast]
Connecting socket for: MMM-MyCalendar
Starting node helper for: MMM-MyCalendar
Sockets connected & modules started ...
Launching application.
Create new news fetcher for url: https://api.20min.ch/rss/view/1 - Interval: 300000
WatchDog started. Maximum timeout: 10s.
Create new news fetcher for url: https://api.20min.ch/rss/view/67 - Interval: 300000
Working notification system. Notification: MMM-GOOGLE_MAPS_TRAFFIC-GET payload: { style: 'standard' }
Create new calendar fetcher for url: https://calendar.google.com/calendar/ical/XXXXXX%40gmail.com/private-b6dbd8fd617ffcffc29ab3478af2b6f1/basic.ics - Interval: 300000
And here are the logs from /home/pi/.pm2/logs/mm-error.log
libGL error: MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
libGL error: MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
ATTENTION: default value of option force_s3tc_enable overridden by environment.
pi@raspberrypi3:~ $ pm2 reloadLogs
Reloading all logs...
All logs reloaded
pi@raspberrypi3:~ $ pm2 logs
[TAILING] Tailing last 15 lines for [all] processes (change the value with --lines option)
/home/pi/.pm2/pm2.log last 15 lines:
PM2 | [2019-09-07T14:54:18.048Z] PM2 log: pid=17526 msg=failed to kill - retrying in 100ms
PM2 | [2019-09-07T14:54:18.145Z] PM2 log: pid=17526 msg=failed to kill - retrying in 100ms
PM2 | [2019-09-07T14:54:18.224Z] PM2 log: App [mm] with id [0] and pid [17526], exited with code [0] via signal [SIGINT]
PM2 | [2019-09-07T14:54:18.245Z] PM2 log: pid=17526 msg=process killed
PM2 | [2019-09-07T14:54:27.372Z] PM2 log: Starting execution sequence in -fork mode- for app name:mm id:0
PM2 | [2019-09-07T14:54:27.383Z] PM2 log: App name:mm id:0 online
PM2 | [2019-09-07T15:18:47.949Z] PM2 log: Process 0 in a stopped status, starting it
PM2 | [2019-09-07T15:18:47.954Z] PM2 log: Stopping app:mm id:0
PM2 | [2019-09-07T15:18:48.369Z] PM2 log: pid=597 msg=failed to kill - retrying in 100ms
PM2 | [2019-09-07T15:18:48.372Z] PM2 log: App [mm] with id [0] and pid [597], exited with code [0] via signal [SIGINT]
PM2 | [2019-09-07T15:18:48.469Z] PM2 log: pid=597 msg=process killed
PM2 | [2019-09-07T15:18:48.473Z] PM2 log: Starting execution sequence in -fork mode- for app name:mm id:0
PM2 | [2019-09-07T15:18:48.493Z] PM2 log: App name:mm id:0 online
PM2 | [2019-09-07T16:10:56.689Z] PM2 log: Reloading logs...
PM2 | [2019-09-07T16:10:56.693Z] PM2 log: Reloading logs for process id 0
/home/pi/.pm2/logs/mm-error.log last 15 lines:
0|mm | MESA-LOADER: failed to retrieve device information
0|mm | MESA-LOADER: failed to retrieve device information
0|mm | ATTENTION: default value of option force_s3tc_enable overridden by environment.
0|mm | libGL error: MESA-LOADER: failed to retrieve device information
0|mm | MESA-LOADER: failed to retrieve device information
0|mm | MESA-LOADER: failed to retrieve device information
0|mm | ATTENTION: default value of option force_s3tc_enable overridden by environment.
0|mm | libGL error: MESA-LOADER: failed to retrieve device information
0|mm | MESA-LOADER: failed to retrieve device information
0|mm | MESA-LOADER: failed to retrieve device information
0|mm | ATTENTION: default value of option force_s3tc_enable overridden by environment.
0|mm | libGL error: MESA-LOADER: failed to retrieve device information
0|mm | MESA-LOADER: failed to retrieve device information
0|mm | MESA-LOADER: failed to retrieve device information
0|mm | ATTENTION: default value of option force_s3tc_enable overridden by environment.
/home/pi/.pm2/logs/mm-out.log last 15 lines:
0|mm | Connecting socket for: MMM-MyCommute
0|mm | ====================== Starting node_helper for module [MMM-MyCommute]
0|mm | Connecting socket for: MMM-GoogleMapsTraffic
0|mm | Starting node_helper for module: MMM-GoogleMapsTraffic
0|mm | Connecting socket for: MMM-DarkSkyForecast
0|mm | ====================== Starting node_helper for module [MMM-DarkSkyForecast]
0|mm | Connecting socket for: MMM-MyCalendar
0|mm | Starting node helper for: MMM-MyCalendar
0|mm | Sockets connected & modules started ...
0|mm | Launching application.
0|mm | Create new news fetcher for url: https://api.20min.ch/rss/view/1 - Interval: 300000
0|mm | WatchDog started. Maximum timeout: 10s.
0|mm | Create new news fetcher for url: https://api.20min.ch/rss/view/67 - Interval: 300000
0|mm | Working notification system. Notification: MMM-GOOGLE_MAPS_TRAFFIC-GET payload: { style: 'standard' }
0|mm | Create new calendar fetcher for url: https://calendar.google.com/calendar/ical/XXXXXXXXX%40gmail.com/private-b6dbd8fd617ffcffc29ab3478af2b6f1/basic.ics - Interval: 300000