MMM-MyCommute

[j.e.f.f]

@rudibarani sure. You can add a rule in your custom css file like this:

.MMM-MyCommute .travel-time.status-good {  
  color: #FFFFFF;
}

[rudibarani]

@j.e.f.f Great! I keep learning about the way MM-modules work. Thanks a lot

[rudibarani]

Hi @j.e.f.f,
is there a way to localize the output of MMM-MyCommute? I noticed that MMM-MyWeather uses a translate folder that contains a file for each supported language. Maybe something similar would be possible here, too. I am happy to provide German translations if you like.
Related to that would be adhering to the timeformat set in a users config.js. Currently, the module seems to only support the 12 hour am/pm-format. Having a 24h format as in my other modules would be great.
Thanks for caring to think about this!

[j.e.f.f]

@rudibarani This module doesn’t print out many literal strings, except for error messages in the console, and the two words “Error” (easily localized) and “min.” (e.g. 33 min). Everyting else is either configured text or data from the API response. Are you looking to translate the route summary? eg: The grey text below the title in the image below:

If so, this is provided by Google in the response from the directions API. It is supposed to localize automatically based on where it determines your location to be, but I’m not sure if that’s just for returning otherwise ambiguous directions or if it’s supposed to give you the route in the localized language. That said, it request accepts an explicit region parameter. I could expose that and you could set it to see if that addresses this.

As for the time format, the module is not presenting any time in 12 hour AM/PM format. It is calculating the total number of minutes to get to the destination and presenting it in a built string – calculatedTimeInMinutes + " min". This will ALWAYS be a sum of minutes (e.g.: 90 min, not 1 hr 30 min – this is to save space). I could expose a string format parameter that has a placeholder for the number of minutes, so you could specify something like timePredictionFormat: "%MINUTES% m" (module would replace %MINUTES% with calculatedTimeInMinutes, and would render as 33 m, for example). Would this work for what you’re trying to do?

[rudibarani]

@j.e.f.f Thanks for the clarifications. Both of my questions seem to relate to grey text you referred to. In my case, it shows an english route summary including the departure times in the 12 hour format:

Having this string in German with 24h time format would be great. Maybe the region parameter could be a solution.

[j.e.f.f]

@rudibarani Ah I forgot about that part! Yeah that should be doable… The time in 12 hour format is provided by Google as-is, but I should be able to convert it. I can make this entire string a time format string. That way it can be translated in whatever context and order you need.

something like nextTransitVehicleSummaryFormat: "[next at] HH:mm".

That way you could translate it any way you like or change it any way you like.

[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.