MagicMirror² v2.16.0 is available! For more information about this release, check out this topic.
UNSOLVED 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?
