MMM-MyCommute

[Fonfon]

This post is deleted!

[j.e.f.f]

@leshark I decided to throw in this feature. I didn’t change the CSS, so if you use a long formatting template, you run the risk of the label overlapping the travel time. I’ll leave that up to you to manage shortening your label. That said, there should be ample space for a format like 3h 45m.

To get the update, navigate to your MMM-MyCommute and execute the following:

git pull

then:

npm install

After that you’ll be able to specify a travelTimeFormat configuration option. By default it will be m [min] (e.g. 87 min), but you can specify any format you wish. I’m using the moment-duration-format plugin for this (https://github.com/jsmreese/moment-duration-format).

Note that this I’m using this plugin’s trim feature, which will omit unnecessary tokens. For example, if you specify a format of h[h] m[m] (e.g.: 1h 27m), but your travel time is less than an hour, only the minute portion will be displayed (e.g.: 36m instead of 0h 36m).

Have fun!
-Jeff

[leshark]

@j.e.f.f Works like a charm! Thanks for the update :-)

[RYANO]

Hi
How do get this work in New zealand, Sorry I am new to this and you module look great and I want to use it.

[j.e.f.f]

@RYANO Hey glad you like the module! There should be nothing special you need to do in order to get this to work in New Zealand. If regular Google maps works for you in your browser or on your phone, then this module should work just fine. Follow the installation instructions as per the Readme, and make sure you get a Google API key. Put your API key in the apikey field in the config. Put your home address as it would normally appear in Google maps as the origin in the config, and the destination address, again as it would normally appear in Google maps as the destination for each entry in your destinations array. Configure everything else to your preference.

[kasperb]

@j-e-f-f Thanks for your module - it works great! I have one question: one of my trips involves using the light rail, however, the module list this as “(undefined)” opposed to the actual method of transportation. Do you have any suggestions how I could fix this?

[kasperb]

@j-e-f-f The issue was resolved after a git pull - thanks for the quick fix!

[lucallmon]

@j-e-f-f I haven’t come to this site for a while and wanted to know if you’ve worked out a way to have multiple stops and transportation modes in a single module. For instance, I’d like to see the total time it takes: Home to Metro station, Metro Station to Metro Station, Metro station to Work = total commute time. Is there a way to do this in a single module?

[j.e.f.f]

@lucallmon The Google directions API doesn’t directly work that way. One API call requires an origin, a destination, and a single mode of transportation. It’s possible to specify explicit waypoints, but those are assumed to be part of the same mode of transportation. In theory it should be possible to do what you are asking by making multiple calls, with the destination of the first call being the origin of the next call (and so forth). I worry, though, that such an approach would make it more likely to exceed the daily request limit. Let me think about it and see if there is an effective way to manage that.

[lucallmon]

@j.e.f.f Thanks Brother! Looking forward to hearing how it turns out.