MMM-MyCommute

[seanluse41]

Can this module support Japanese addresses?
The default config and values work for me, but putting in Japanese addresses returns loading… forever.

[thoeng]

This is great and very practical module! Everything is working on me but i would like to remain below USD200 (40K calls)/mo API call request. This means staying below 1.3K calls/day

However, after installed I can see 570+ request call in 2 hours on Google API dashboard. This is despite setting pollFrequency: 1200000 (20mins interval) on MM config.

Any help please?

[charp07]

MM is only loading the “loading…” text for this module. All my other modules are showing right. I am getting request on the Google API Console under the Directions API. So I believe that I must have the module installed correctly. Does anyone know why this would be happening?

[charp07]

	{
		module: 'MMM-MyCommute',
		position: 'bottom_right',
		config: {
			apikey: 'my api key from google',
			origin: '65 Front St W, Toronto, ON M5J 1E6',
			startTime: '00:00',
			endTime: '23:59',
			hideDays: [0,6],
			destinations: [
  {
				destination: '14 Duncan St Toronto, ON M5H 3G8',
				label: 'Air Canada Centre',
				mode: 'walking',
				color: '#82E5AA'
  },
  ]
  }

},

[sdetweil]

in the MagicMirror folder do

npm check:config

fix 1st error, repeat
I think it is the comma after the only destination

				color: '#82E5AA'
  },   //< ---

loading …

is the default message many modules put up while getting their data
but it failed to get the data

so, this means there was an internal error in the module code
open the developers window
(either npm start dev, or use ctrl-shift-i when mirror is running)
select the console tab, and scroll up to locate any errors, usually red text

[charp07]

This post is deleted!

[charp07]

@sdetweil okay, I’m new but the check:config command is not valid. So tried npm config and it brought up 10 errors.

Usage:
Npm config set
Npm config get …
Etc
Etc…

What does this mean?

[charp07]

@sdetweil also added comma to that location with no success. Then moved to behind bracket and nothing there either.

[sdetweil]

@charp07 sorry, I get that command backwards

npm config:check

[interman]

@thoeng I ran into the same problem. there a few things you can do.

1. 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
2. Hide the module on weekends. Mine does not come up on the weekends. hideDays
3. Change how many times it goes to google with a request. pollFrequency
4. add a cheap motion sensor to turn the display on and off (getting one now).

Hope that helps.

Dn