@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.

@sdetweil

If I access the MagicMirror directly via Putty do I have to enter npm start dev or how?

If i enter npm start dev he following will come out:

npm ERR! path /home/pi/package.json
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall open
npm ERR! enoent ENOENT: no such file or directory, open '/home/pi/package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/pi/.npm/_logs/2019-09-06T07_07_27_973Z-debug.log

Good Morning

So I activated the 2FA and replaced the generated key with my password. I also took your config and added my username and password from 2FA. Unfortunately, as before, there is still “load” and it does not show any emails.

I do not see it either. I see the same as sdetweil. I’ve also approved third-party apps with account access on this page below.

Can I do something that would help you? Post a log or something. You just have to tell me the command;)

no ideas? Or can I do something that can help you to find the mistake?

Hello

Sorry if I ask again, but unfortunately I can not find it. So I go like this -> Account -> Security and then I do not find what you mean.

@mumblebaj said in Problem with the Module "email":

@CyruS1337 With gmail you have to create an application key on gmail itself. Your email account password would not work.

And how do I create an application key myself? :-/

@cirdan Unfortunately, the module still does not work for me. Have it disabled mitlerweile again.

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'		 
		  },
		 
		 
    ]
  }
},