@j.e.f.f said in MMM-MyCommute:

nextTransitVehicleDepartureFormat: “[Next:] HH:mm”,

It works like a charme. Thanks a lot!!

@j.e.f.f Great idea!!! Thanks for trying :)

Thanks @Yurick for finding the solution to the problem. Would be great to see this implemented so everyone could benefit from @kapsolas module.

@j.e.f.f Thanks for the clarifications. Both of my questions seem to relate to grey text you referred to. In my case, it shows an english route summary including the departure times in the 12 hour format:

Having this string in German with 24h time format would be great. Maybe the region parameter could be a solution.

Hi @j.e.f.f,
is there a way to localize the output of MMM-MyCommute? I noticed that MMM-MyWeather uses a translate folder that contains a file for each supported language. Maybe something similar would be possible here, too. I am happy to provide German translations if you like.
Related to that would be adhering to the timeformat set in a users config.js. Currently, the module seems to only support the 12 hour am/pm-format. Having a 24h format as in my other modules would be great.
Thanks for caring to think about this!

@kapsolas Thanks for the quick reply. Another question on the side: It seems that only images are are loaded that where on Instagram before I restarted my MM. Is that intended behaviour or am I doing something wrong?

		{
			module: 'MMM-Instagram',
			position: 'middle_center',
			disabled: false,
			config: {
				access_token: '####.####',
				count: 200,  
				min_timestamp: 0,
				animationSpeed: 2500,
				updateInterval: 30000
			}
		},

I waited an hour but non of my new images showed up. Only old ones. Even create a new account with only three images before booting my MM - and it keeps cycling those three and ignores later uploads…
Any idea?

Hi @kapsolas,
I think I need some help with the settings for

min_timestamp: 0,

Is there a way to set show only images from today and show nothing if there is no image uploaded today?

Thanks for your help

@olexs
The delay calculation and sorting issue seems to be even stranger. Now I have three upcoming ICE connections to Berlin. This is how they are shown:

• 22:01 +20 //actual: 21:59 + 2 min
• 23:01 +20 //actual: 22:59 + 2 min
• 20:15 +40 //actual: 19:59 + 15 min

The hafas output is:

Parsing: ICE 276 nach Berlin Hbf (tief) um Mon Jun 26 2017 20:14:00 GMT+0200 (CEST)
{"name":"ICE 276","class":1,"productCode":0,"productName":"ICE"}
{ when: 2017-06-26T18:14:00.000Z,
  delay: 900000,
  line: 'ICE 276',
  nr: undefined,
  type: 'ICE',
  color: '#006F35',
  direction: 'Berlin Hbf (tief)' }
Parsing: ICE 274 nach Berlin Hbf (tief) um Mon Jun 26 2017 22:01:00 GMT+0200 (CEST)
{"name":"ICE 274","class":1,"productCode":0,"productName":"ICE"}
{ when: 2017-06-26T20:01:00.000Z,
  delay: 120000,
  line: 'ICE 274',
  nr: undefined,
  type: 'ICE',
  color: '#006F35',
  direction: 'Berlin Hbf (tief)' }
Parsing: ICE 592 nach Berlin Hbf (tief) um Mon Jun 26 2017 23:01:00 GMT+0200 (CEST)
{"name":"ICE 592","class":1,"productCode":0,"productName":"ICE"}
{ when: 2017-06-26T21:01:00.000Z,
  delay: 120000,
  line: 'ICE 592',
  nr: undefined,
  type: 'ICE',
  color: '#006F35',
  direction: 'Berlin Hbf (tief)' }

Any idea how to fix this?

Hi @olexs,
I think I found a bug that we could fix quite easily. There seems to be a problem with the calculation of the delay. Looking at this output that comes from hafas:

Parsing: ICE 276 nach Berlin Hbf (tief) um Mon Jun 26 2017 20:14:00 GMT+0200 (CEST)
{"name":"ICE 276","class":1,"productCode":0,"productName":"ICE"}
{ when: 2017-06-26T18:14:00.000Z,
  delay: 900000,
  line: 'ICE 276',
  nr: undefined,
  type: 'ICE',
  color: '#006F35',
  direction: 'Berlin Hbf (tief)' }
Parsing: ICE 274 nach Berlin Hbf (tief) um Mon Jun 26 2017 22:01:00 GMT+0200 (CEST)
{"name":"ICE 274","class":1,"productCode":0,"productName":"ICE"}
{ when: 2017-06-26T20:01:00.000Z,
  delay: 120000,
  line: 'ICE 274',
  nr: undefined,
  type: 'ICE',
  color: '#006F35',
  direction: 'Berlin Hbf (tief)' }

The screen will show no delay for the ICE 274 and 20 Minutes delay for ICE 276. 15 minutes and 2 minutes, respectively, would have been correct according to the DB website.
I guess, the calculation is currently delay/60/100 instead of delay/60/1000. Would you mind checking on that? It also seems there is no space for a three-digit delay (eg. 120 mins), which sometimes happens with DB.

The time finally shown e.g. as 20:14h in the first example would be the actual delayed departure. I would prefer to see the original departure (time - delay) plus the current delay separately. Maybe you could add an option to switch between actual departure and original departure + delay separately?

Is there a way to sort the output by departure? Currently the next train is at the bottom of the list and later ones are added at the top. Having them sorted the other way round would seem more intuitive to me.

@j.e.f.f Thanks a lot for your quick help! Much appreciated :)