MMM-MyCommute

[BanksyPaint]

@j.e.f.f Thanks so much for responding so quickly. I wish I’d posted again last night, though after I got it working, I threw my hands up in confusion and went straight to bed. I nuked the directory, re-cloned from GitHub, and when I did my ‘npm install’, I did so using ‘sudo’ and upon starting MagicMirror, I saw the module load the way others have, and how I would expect to. I don’t know why in my case I needed elevated priv’s for the npm install to work, though I’m not complaining :P

Thanks for being helpful! Also - really excellent module. You’ve really done a great job.

[j.e.f.f]

@BanksyPaint it concerns me that you needed to use sudo to run npm install… have you needed to do that with any other modules?

[BanksyPaint]

@j.e.f.f No sir. Though to be fair, with other modules I didn’t run npm install? Happy to start from a clean slate on my next opportunity to see if it’s necessary again (I’m away for the weekend, sadly).

[jhermes34]

I’ve just started with my magicmirror project and have most of the modules working, for some reason mmm-mycommute gets stuck on “loading…”. This happens even with the default configuration from the wiki. Any suggestions? Thanks! This is my current configuration(with keys and addresses redacted):

{
  module: 'MMM-MyCommute',
  position: 'top_left',
  config: {
    showHeader: false,
    apikey: '',
    origin: '',
    startTime: '00:00',
    endTime: '23:59',
    hideDays: [4],
    destinations: [
      {
        destination: '',
        label: ''
      },
      {
        destination: '',
        label: '',
        avoid: 'tolls'
      }
    ]
  }
}

[j.e.f.f]

@jhermes34 Did you remember to run npm install in the MMM-MyCommute directory? Do you see any errors in the pm2 log (Assuming you’re managing MM with pm2).

[jhermes34]

@j.e.f.f I did run the npm installer, the pm2 log gives an error about starting mm.sh

[BanksyPaint]

@jhermes34 There’s an npm install that you need to run in the MMM-MyCommute directory, ~/MagicMirror/modules/MMM-MyCommute. This shouldn’t (?) affect pm2 at all.

[j.e.f.f]

@jhermes34 What’s the error you’re seeing?

[Fonfon]

hi all,

I have install MMM-MyCommute executed npm install in folder
i think my config is good,
but when i starting my magic mirror the module don’t start
all my module works great but this one can’t start
can you help me please.

[j.e.f.f]

@Fonfon Do you see any errors in the pm2 logs? Can you send me your config? I’ll give it a try. (Hide your API key)

[Fonfon]

@j.e.f.f thanks jeff
when mm starting there is no error
sorry but i d’ont knows how get logs
this my config:

{
module: ‘MMM-Mycommute’,
position: ‘top_left’,
config: {
showHeader: true,
headerText: ‘Traffic’,
api_key: ‘API’,
origin: ‘my home’,
startTime: ‘00:00’,
endTime: ‘23:59’,
hideDays: [0,6],
destinations: [
{
destination: ‘myworkplace’,
label: ‘Bureau’,
mode: ‘driving’,
color: ‘#82E5AA’
}
]
}
},

[j.e.f.f]

@Fonfon OK there are two problems with your config:

module: 'MMM-Mycommute' needs a capital C, like follows:

module: 'MMM-MyCommute'

Next, the property name for the API key is apikey not api_key

Give those a try and see if it fixes your issue.

Also, the showHeader config isn’t needed any more. If you want a header, add it to your config in the normal way, like so:

    { 
      module: 'MMM-MyCommute',
      position: 'top_left',
      header: "Commute",  // ---- here ----
      config: {
        headerText: 'Traffic',
        apikey: '...',
        origin: '...',
        startTime: '00:00',
        endTime: '23:59',
        hideDays: [0,6],
        destinations: [
          {
            destination: '...',
            label: 'Bureau',
            mode: 'driving',
            color: '#82E5AA'
          }
        ]
      }
    }, 

If you don’t want one, don’t specify that property.

[Fonfon]

@j.e.f.f thanks jeff
its ok now Thanks very much for your help
this module is absolutely fantastic !!!
thanks again !!

[j.e.f.f]

@Fonfon Glad it’s working for you now!

[leshark]

I love this module, it works really well! Is there any way that the journey time could be displayed in HH:MM format rather than just minutes? I’ve looked through the config and I can’t see a way to change this.

Many thanks!

[j.e.f.f]

@leshark I made it explicitly just in minute to save space. Even a long commute of 1hr 30min can be expressed shorter as 90 min. If I enabled the change in format as you ask then I’ll need to dedicate more space to the time, which takes away from the label. I felt the label was more important.

[leshark]

@j.e.f.f Hi, thanks for the reply, I can see that makes sense now and can live with it in minutes! Some of my journeys are 400+ minutes and at 0600 in the morning it takes a moment to do the math :-).

Cheers

Craig

[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 :-)