MMM-MyCommute

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.

Binog

Hey j.e.f.f.

Thanks for this amazing module !
I do have the problem that I use two modules of your commute. once in a while it worked fine, but then it stopped working. Thought something withe the googleAPIkeys was wrong,. now trying, if I cutout one commute, the other shows itself.

Do I have to name MMM-MyCommute to MMM-MyCommute2 for the second one? And then, do I have to rename the js-file as well?

Thx for helping !

j.e.f.f

@Binog This module is supposed to support multiple instances. Send me a message with your config and I’ll help you troubleshoot.

schlachtkreuzer6

This post is deleted!

pjkoeleman

@j-e-f-f
I have this module installed and having a question.
I have formated the time as hh:mm, when the commute time is more than 59 minutes than there are two digits for the hours. When it is less than 60 minutes it only shows the minutes. See image.

My question is how can I force that the time format is using the leading “00:” when the time is lass than 60 minutes?

In moment-duration-format there is an option, but I don not now how to implement this in my mirror, now its looking wierd !
Tried to add the code in line 298 and 312 with {forceLength: true}, but that didn’t do the trick.

Thanks in advance for your repley.

schlachtkreuzer6

Great Module thanks for developing! :)

I got a question or more a request?

Is there any way to enable start/endtime and hide days at the same time? So general the module is not shown weekends [0,6] and than starting Mondays with the destination A1 from 0715 to 0900 and B1 16:00 to 18:00 [2,3,4,5] . And tuesday A1 same (0717-0900) and B2 13:00 to 14:00 [1,3,4,5] Wed-Fri A1 continues.

Many thanks for your help!

strawberry 3.141

@schlachtkreuzer6 did you try to use module scheduler for it?

schlachtkreuzer6

@strawberry-3.141 nope. I didn’t though about it because the module itself got that options but they don’t work at the same time.

j.e.f.f

@schlachtkreuzer6 so if I understand your request, you would like to have different start and end times based on a particular days? If so you can do this. each destination has its own start and end time, as well as its own hideDays list. Configure two destinations with the same destination address, mode, label, etc, but in each one configure the desired start times and hideDays. So for your example above, the config would look something like this:

    {
      module: "MMM-MyCommute",
      position: "top_left",
      classes: "default everyone", 
      header: "Commute",
      config: {
        apikey: "...",
        origin: "...",
        startTime: "00:00",
        endTime: "23:59",
        hideDays: [0,6], //module always completely hidden on weekends
        destinations: [
          {
            destination: "A1 Destination Address",
            label: "A1",
            startTime: "07:15",
            endTime: "09:00",
          },
          {
            destination: "B1 Destination Address",
            label: "B1",
            startTime: "16:00",
            endTime: "18:00",
            hideDays: [2,4] //hidden on tues, thurs
          },
          {
            destination: "B1 Destination Address",
            label: "B1",
            startTime: "13:00",
            endTime: "14:00",
            hideDays: [1,3,5] //hidden on mon, wed, fri
          }
        ]
      }
    }

j.e.f.f

@pjkoeleman I just added a config parameter to control this. Add travelTimeFormatTrim: false to turn off the duration trimming. It also accepts "left" to trim larger zero-value tokens (e.g.: 0h 37min renders as 37min), and "right" to trim the smaller tokens first (e.g.: 2h 0min renders as 2h). It defaults to "left".

Note that setting this parameter to true has the same affect as setting it to false. To get the default behaviour, set this to "left" or just omit the parameter altogether.

Do a git pull and you should be able to use the new config.

pjkoeleman

@j.e.f.f
Thanks very much, now I will study you code, because I want to learn javascript my self.

j.e.f.f

@pjkoeleman the key here is that I’m using a plugin for Moment.js that allows formatting of time durations. By default, Moment.js doesn’t allow this. See here:

https://github.com/jsmreese/moment-duration-format

schlachtkreuzer6

@j.e.f.f ok! Thanks I will try this as fast as possible, after my holiday ;)

FYI: I work at two destinations, Mon -Fri at W1 and Mon evening and Tuesday evening at W2 with about 1,5-2h at home ^^ only traveling with the car, so for me it’s necessary to know if my usual route is busy or not to calculate when I should left for work but I not really need to know the other route ;) traffic on route W2 varies +/- 1h… (terrible!)

But if this mini schedule thing inside this module works: WOW! What an absolutely overkill of an module for me!