MMM-MyCommute

[sdetweil]

@banbutcher I don’t know what API parameters are available or used by that module

[banbutcher]

its just a pic of the list of enabled Apis and directions is on there… no still hasnt solved problem.

is their a different key for directions api and another different key for the javascript map api?

[sdetweil]

@banbutcher no. Just have to use the same project and key to enable the apis

[banbutcher]

@sdetweil

thats what i thought, i have the right ones enabled and using the same key! :/

[banbutcher]

turns out i didnt have the address formatted correctly! took them directly from google maps and it worked great!

thanks,
Richie

[banbutcher]

is there any way of knowing if calendar events are being passed? Ive added this code to mine and nothing gets added to my commute:

      maxCalendarEvents: 2,
      maxCalendarTime: 24 * 60 * 60 * 1000,
      calendarOptions: [
              {
              mode: 'driving'
              }
      ],  

am i missing something?

[testdruif]

Created issue for calendar events regarding arrival time & transit option.
Also worth noting that calendar events are only first added when the module refreshes traffic (after 10 minutes from startup)

https://github.com/qistoph/MMM-MyCommute/issues/12

[sdetweil]

@testdruif is this module getting cal events as broadcast by the calendar module? How often does the cal module refresh/broadcast?

[testdruif]

@testdruif said in MMM-MyCommute:

Created issue for calendar events regarding arrival time & transit option.
Also worth noting that calendar events are only first added when the module refreshes traffic (after 10 minutes from startup)

https://github.com/qistoph/MMM-MyCommute/issues/12

When the calendar events are added the code crashes further down the line.
Code doesn’t add the calendar collor variable.

[testdruif]

@sdetweil Yes, the module gets events from calendar module broadcast.

Another issue: when you have multiple calendar modules configured the array gets wiped at unexpected times.
So you can only use it correctly with 1 calendar module.

because the commute module loads before all calendar entries are processed they are processed on the next “commute update” which is 10m by default config.