Read the statement by Michael Teeuw here.
MMM-MyCommute not showing up.
-
@spoonek the same result means the problem is probably in the key. Google requires a credit card to back their accounts, altho they give generous credits against usage for a while
-
@sdetweil Yep, I added a card and activated the account last night. Was hoping it would sync up overnight but same issue this morning.
-
@spoonek use the menu to get the dev window open. or start with
npm start dev
if u normally use pm2, do pm2 stop 0
before the npm start -
@spoonek no sync time. it’s immediate.
-
@sdetweil said in MMM-MyCommute not showing up.:
@spoonek use the menu to get the dev window open. or start with
npm start dev
if u normally use pm2, do pm2 stop 0
before the npm startOK, that is awesome! Thanks for the tip! So maybe I need to generate a new api key and use that?
[2020-08-20 09:07:14.680] [LOG] MMM-MyCommute: You must use an API key to authenticate each request to Google Maps Platform APIs. For additional information, please refer to http://g.co/dev/maps-no-account
-
@spoonek u didn’t list the maps api I the list of services above
Google Maps Platform APIs
-
@sdetweil thanks. I don’t see it…
-
@spoonek from the link on the module doc
Maps JavaScript API
from the image u posted,
2nd row, second box from left -
@sdetweil said in MMM-MyCommute not showing up.:
@spoonek from the link on the moduledoc
Maps JavaScript API
from the image u posted,
2nd row, second box from leftYep, got that one already. :(
-
@spoonek so, then, passing the key is a problem,
so it might be the item name in config. u can specify both,
and u got the right string for the API key from Google.which GitHub module are u using?
from the module folder do,
git remote -v