Read the statement by Michael Teeuw here.
MMM-MyCommute
-
@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: [ ... ] } },
-
@j.e.f.f said in MMM-MyCommute:
nextTransitVehicleDepartureFormat: “[Next:] HH:mm”,
It works like a charme. Thanks a lot!!
-
@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.
-
@BanksyPaint can you check your electron logs by starting the mirror with
npm start dev
-
@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.
-
@strawberry-3.141 Thank you :D If not for this, then for future posts.
-
@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.
-
@BanksyPaint it concerns me that you needed to use
sudo
to runnpm install
… have you needed to do that with any other modules? -
@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).
-
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' } ] } }