A New Chapter for MagicMirror: The Community Takes the Lead
Read the statement by Michael Teeuw here.
Read the statement by Michael Teeuw here.
MMM-MyCommute
-
Good Morning
I have the module MMM-MyCommute installed on my 3 PIs. It also works on two out of three PIs. I do not know that the module works better on the second PI. I have already made the settings for a PI that runs MMM-MyCommute properly. Unfortunately, it does not work on the PI. Can someone help me please, that would be my configuration:
{ module: 'MMM-MyCommute', position: 'top_left', config: { apikey: 'API_KEY', origin: 'start', startTime: '04:00', endTime: '08:00', travelTimeFormat: 'h[h]:m[min]', colorCodeTravelTime: true, showSummary: true, hideDays: [0,6], destinations: [ { destination: 'destination', label: 'Lisa Arbeit über Autobahn', alternatives: true, startTime: '05:00', endTime: '08:00', }, { destination: 'destination', label: 'Lisa Arbeit über Oensingen', color: "#82BAE5", waypoints: 'via:Oltenstrasse, 4702 Oensingen | via:Oltenstrasse, 4538 Oberbipp' }, { destination: 'destination', label: 'Lisa Arbeit über Kestenholz', startTime: '05:00', waypoints: 'via:Oensingerstrasse, 4703 Kestenholz' }, { destination: 'destination', label: 'Lisa Arbeit über Kestenholz', color: "#DB7093", waypoints: 'via:Wangenstrasse, 4913 Bannwil' }, ] } }, -
no ideas? Or can I do something that can help you to find the mistake?
-
@CyruS1337 what does ‘does not run’ mean?
did u open the developers console and look for any errors reported?
-
If I access the MagicMirror directly via Putty do I have to enter
npm start devor how? -
@CyruS1337 yes, do
cd ~/MagicMirror export DISPLAY=:0 npm start dev -
@sdetweil said in MMM-MyCommute:
export DISPLAY=:0
That comes out when I enter
npm start dev> magicmirror@2.8.0 start /home/pi/MagicMirror > sh run-start.sh "dev" 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 ... Whoops! There was an uncaught exception... { Error: listen EADDRINUSE 0.0.0.0:8080 at Server.setupListenHandle [as _listen2] (net.js:1330:14) at listenInCluster (net.js:1378:12) at doListen (net.js:1492:7) at process._tickCallback (internal/process/next_tick.js:63:19) at Function.Module.runMain (internal/modules/cjs/loader.js:755:11) at startup (internal/bootstrap/node.js:241:19) at bootstrapNodeJSCore (internal/bootstrap/node.js:579:3) errno: 'EADDRINUSE', code: 'EADDRINUSE', syscall: 'listen', address: '0.0.0.0', port: 8080 } MagicMirror will not quit, but it might be a good idea to check why this happened. Maybe no internet connection? If you think this really is an issue, please open an issue on GitHub: https://github.com/MichMich/MagicMirror/issues Launching application. -
@CyruS1337 said in MMM-MyCommute:
EADDRINUSE 0.0.0.0:8080
already an instance running with pm2…
pm2 list
pm2 stop 0
pm2 start 0
-
@sdetweil said in MMM-MyCommute:
@CyruS1337 said in MMM-MyCommute:
EADDRINUSE 0.0.0.0:8080
already an instance running with pm2…
pm2 list
pm2 stop 0
pm2 start 0
I did, unfortunately it still does not show me the module
pi@raspberrypi3:~/MagicMirror/modules/MMM-MyCommute $ pm2 list ┌──────┬────┬──────┬────────┬───┬─────┬──────────┐ │ Name │ id │ mode │ status │ ↺ │ cpu │ memory │ ├──────┼────┼──────┼────────┼───┼─────┼──────────┤ │ mm │ 0 │ fork │ online │ 5 │ 0% │ 2.6 MB │ └──────┴────┴──────┴────────┴───┴─────┴──────────┘ Use `pm2 show <id|name>` to get more details about an app pi@raspberrypi3:~/MagicMirror/modules/MMM-MyCommute $ pm2 stop 0 [PM2] Applying action stopProcessId on app [0](ids: 0) [PM2] [mm](0) ✓ ┌──────┬────┬──────┬─────────┬───┬─────┬────────┐ │ Name │ id │ mode │ status │ ↺ │ cpu │ memory │ ├──────┼────┼──────┼─────────┼───┼─────┼────────┤ │ mm │ 0 │ fork │ stopped │ 5 │ 0% │ 0 B │ └──────┴────┴──────┴─────────┴───┴─────┴────────┘ Use `pm2 show <id|name>` to get more details about an app pi@raspberrypi3:~/MagicMirror/modules/MMM-MyCommute $ pm2 start 0 [PM2] Applying action restartProcessId on app [0](ids: 0) [PM2] [mm](0) ✓ [PM2] Process successfully started ┌──────┬────┬──────┬────────┬───┬─────┬──────────┐ │ Name │ id │ mode │ status │ ↺ │ cpu │ memory │ ├──────┼────┼──────┼────────┼───┼─────┼──────────┤ │ mm │ 0 │ fork │ online │ 5 │ 0% │ 2.6 MB │ └──────┴────┴──────┴────────┴───┴─────┴──────────┘ Use `pm2 show <id|name>` to get more details about an app -
ok, and pm2 logs to show the logging output
-
The module once worked on the PI. Do I have to do something now @sdetweil?
-
@CyruS1337 i don’t know anything about the module… so just looking for debugging info…
pm2 logs should show something
-
That would be my logs
pi@raspberrypi3:~ $ pm2 logs [TAILING] Tailing last 15 lines for [all] processes (change the value with --lin es option) /home/pi/.pm2/pm2.log last 15 lines: PM2 | [2019-09-07T14:54:17.446Z] PM2 log: Stopping app:mm id:0 PM2 | [2019-09-07T14:54:17.944Z] PM2 log: pid=17526 msg=failed to kill - retrying in 100ms 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 [1 7526], 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 - re trying in 100ms PM2 | [2019-09-07T15:18:48.372Z] PM2 log: App [mm] with id [0] and pid [5 97], 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 /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-MyCommu te] 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-DarkSky Forecast] 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/ca lendar/ical/XXXXX%40gmail.com/private-b6dbd8fd617ffcffc29ab3478af2b6f1/b asic.ics - Interval: 300000 -
@CyruS1337 refresh the logs output… (watch out, your email private url is shown)
-
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 -
@CyruS1337 got to be more than that
-
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: 300000And here are the logs from
/home/pi/.pm2/logs/mm-error.loglibGL 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. -
Hello,
I had a similar problem. Just tried out some module configurations and forks.
I now use MMM-GoogleMapsTraffic from here https://github.com/sdetweil/MMM-GoogleMapsTraffic.git (see this thread MMM-GoogleMapsTraffic freezes Magic Mirror)
and MMM-MyCommute from here https://github.com/qistoph/MMM-MyCommute.git
This seems to work for me.
There is also a small error in your configuration. The first destination has a comma after the last configuration endTime. This needs to be removed for a propor JSON file.
Regards Dirk -
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.)
-
@CyruS1337 there is a bug in the googlemapstraffic module, I have a fixed version… you can rename the current module folder out of the way, and then git clone the fixed one from my repo.
-
Hi @sdetweil
Mhmmm sorry if I ask so stupid. How do I do that then I download the module from you …
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login