MMM-MyCommute

rudibarani

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

j.e.f.f

@rudibarani Ok give it a shot now. I add a config option called nextTransitVehicleDepartureFormat.

Here’s an example:

    {
      module: 'MMM-MyCommute',
      position: 'top_left',
      classes: 'default everyone', 
      header: 'Commute',
      config: {
        apikey: 'SECRET',
        origin: 'SECRET',
        ...
        nextTransitVehicleDepartureFormat: "[Next:] HH:mm",
        destinations: [
          ...
        ]
      }
    },

rudibarani

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

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

It works like a charme. Thanks a lot!!

BanksyPaint

@j.e.f.f Hi there! I know the original post you replied to is a little dated, though I’m experiencing this as well. I’ve taken the config you have posted here:
https://github.com/jclarke0000/MMM-MyCommute
With the changes you also suggested for the header and text, and inserted my API key, and I’m seeing nothing appear. I’ve taken the OP’s suggestion, rm’ing the folder, re-cloning and re-installing, though it isn’t working for me. Any ideas on what it could be?

Here’s the output from MM, and it looks normal? I tried another user’s suggestion of rebooting the pi, and sadly that didn’t work for me :(

Initializing new module helper ...
Module helper loaded: MMM-MyCommute
All module helpers loaded.
Starting server on port 8080 ... 
Server started ...
Connecting socket for: updatenotification
Connecting socket for: MMM-MyCommute
====================== Starting node_helper for module [MMM-MyCommute]
Sockets connected & modules started ...
Launching application.

strawberry 3.141

@BanksyPaint can you check your electron logs by starting the mirror with npm start dev

j.e.f.f

@BanksyPaint hey are you seeing nothing appear or is it stuck on “Loading”? The module is designed to hide itself if it is outside the time frame window you set in the config, in which case you’ll see nothing at all. If there’s a problem during initialization, then it will be stuck on “Loading”.

Otherwise, can you send me your config? I’ll give it try on my side.

BanksyPaint

@strawberry-3.141 Thank you :D If not for this, then for future posts.

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 !!