Hi @matelot20,

I know that MMM-MyCommute was having some issues on my mirror yesterday as well, but fixed itself later in the day without me having to do anything (still not sure why exactly that was happening, but it’s better now). I know that for it to recognize your destinations you have to have the address as it shows in Google Maps, for example: Disneyland Anaheim would be “1313 Disneyland Dr, Anaheim, CA 92802” instead of “Disneyland” as you have it in your config. As for the API message, it could be something different.

Please let me know if that helps!

Edit - I just realized that if you are running the latest update of MMM-MyCommute, there was an update that changed the config text “apikey” to “apiKey”, so

apikey:  [my api key],

would now be

apiKey:  [my api key],

That could be where your API issue stems from