MMM-MyCommute

[beck0r]

@j.e.f.f

Of course… here it comes

	{
  				module: 'MMM-MyCommute',
  				position: 'top_left',
  				config: {
    					showHeader: true,
    					headerText: 'Verkehr',
   					apikey: '...',
    					origin: '...',
    					startTime: '05:00',
    					endTime: '17:00',
    					destinations: [
      							{
        						destination: '...',
       	 						label: 'Auto zur Arbeit',
        						mode: 'driving',
        						color: '#82E5AA'
      							},      						
      							{
        						destination: '...',
        						label: 'Fahrrad zur Arbeit',
        						mode: 'bicycling',
							color: '#FFB444'
      							},
							{
        						destination: '...',
        						label: 'RMV zur Arbeit',
        						mode: 'transit'
      							}
    							]
  					}
		},

[j.e.f.f]

@beck0r Can you try doing a git pull in your MMM-MyCommute directory and restarting your mirror? I think I found your issue – I didn’t have an icon definition for High-speed rail.

EDIT Maybe not… I need to add definitions for all sorts of possible transit vehicle types. Stay tuned…

EDIT OK fixed for real this time. I added definitions for all of the transit modes listed here: https://developers.google.com/maps/documentation/directions/intro#VehicleType

Note: You’ll see the tram icon while the route is loading, as that is the default icon used when no transitMode is specified. But you’ll see it change to the train icon after your travel times are retrieved.

[BlackTalon]

@j.e.f.f This is perfect! Thank you so much!

[beck0r]

Hi,

once again for everybody with the same issue. It’s working now! Thumbs up for j.e.f.f, thank you!

[joela85]

One more question. I want to make a route going via different roads, can that be done in this config file?
For example:
Destination: X
Via: A1

Destination: X
Via: A2

[j.e.f.f]

@joela85 so the google API doesn’t allow that specifically, but there are a couple of ways we could accomplish something similar:

1. I can have Google return alternative routes, and they can be listed out. No garantee you’re going to get any of the routes you’re interested, but they will be the fastest.

2. you can provide a list of waypoints and Google will return your route passing through those specific places. So if you put specific landmark addresses that are on the highways you’re interested in then you would more or less get the result you’re looking for.

Both of these options seem fairly straightforward to add so I might just do both :)

[j.e.f.f]

@joela85 I added the first of the above two options. You can specify alternatives:true for any of your destinations to get alternative routes. showSummary must be set to true for this to work.

Will be working on the second option soon.

[j.e.f.f]

@joela85 I’ve added the second option too. You can now specify a waypoints parameter for any of the destinations to influence the route Google will find.

[tidus5]

@j.e.f.f Hey Jeff
can you add the time for the next metro/tram/bus ?
is it possible to catch the adress in the agenda ? and if its blank just used the definited adress in destination ? :-)

[j.e.f.f]

@tidus5 I’ll have to see what the API gives me. Not sure that info is available.

I wrote a transit-specific module that does that but it is for TTC (Toronto transit). However it is based in the NextBus API which supports many systems. It could easily be modified to work with a number of transit systems. Which is yours?