Read the statement by Michael Teeuw here.
MMM-MyCommute
-
@thoeng I ran into the same problem. there a few things you can do.
- Set the time that the module comes on and goes off. For example, I set my mine from 5:00 am to 8:00 am.
startTime and endTime - Hide the module on weekends. Mine does not come up on the weekends. hideDays
- Change how many times it goes to google with a request. pollFrequency
- add a cheap motion sensor to turn the display on and off (getting one now).
Hope that helps.
Dn
- Set the time that the module comes on and goes off. For example, I set my mine from 5:00 am to 8:00 am.
-
I swapped to a newer branch of “MMM-MyCommute”. After install, it booted up on the first try. Happy that it is now working. Thanks to all the authors of this module.
-
Will this module still be updating in the background during the hidden times? With the Google API, I wouldn’t want it updating when I am not needing it. Thanks!
-
Is anyone else having issues with the MyCommute module hiding itself but then not re-appearing.
I have EndTime setup for 8pm and also HideDays on certain days, however, once it hides, it stays hidden. Until I force it to show using the Remote module.
Otherwise, this Module works great, showing all the traffic times as it should. -
@JRB1988 From my experiences, I don’t believe it does.
-
Hi I have gotten this module setup and working with destinations (see below), but am trying to get it to show times based on locations of calendar events setup like at the end of the help page but it doesn’t seem to want to show. Am I missing something? My calendar shows my events and locations but not sure if MyCommute is pulling it. I even used the example code from the module Git page and it still didn’t pull anything. Does this not work anymore? Any insight would be much appreciated!
{ module: 'MMM-MyCommute', position: 'bottom_left', header: 'Traffic', config: { apikey: 'XXX', origin: 'XXX', startTime: '06:00', endTime: '20:00', destinations: [ { destination: 'XXX', label: 'XXX', hideDays: [0,6], mode: 'driving', alternatives: true, showSummary: true, color: '#82E5AA' }, { destination: 'XXX', label: 'XXX', mode: 'driving', alternatives: false, showSummary: false, color: 'lightblue' } ], maxCalendarEvents: 2, calendarOptions: [ { mode: 'driving' } ] } },
-
everything else is working time, personnel calendar and weather. my commute shows error in red on the side. does show that it is continuing to update. any suggestion?
{ module: "MMM-MyCommute", position: "bottom_bar", config: { apikey: 'google api key', origin: ' Rd, city, state zip', startTime: '00:00', endTime: '23:59', destinations: [ { destination: ' Ave, city, state zip', label: ' Work1', mode: 'driving', color: '#82E5AA' }, { destination: ' Ave, city, state zip', label: ' Work2', mode: 'driving', color: '#82E5AA' }, ] } },
-
@wagon40
I checked the apikey and Google is showing a count of apikey request. So that leads me to believe that it is a MM issue or module issue. Any help would be be great. -
@wagon40 said in MMM-MyCommute:
@wagon40
I checked the apikey and Google is showing a count of apikey request. So that leads me to believe that it is a MM issue or module issue. Any help would be be great.Hello to all,
I have the same problem as @wagon40 , can you help us?The log of the MM shows:
[13:48:15.263] [LOG] MMM-MyCommute: This API project is not authorized to use this API. [13:48:15.268] [LOG] MMM-MyCommute: This API project is not authorized to use this API.
I use the same Google API that uses “MMM-GoogleMapsTraffic” … could it be the cause of the problem?
Thanks a lot!
-
Is anybody there? 🤔