Read the statement by Michael Teeuw here.
MMM-MyCommute
-
@smotx The module is designed to be as frugal as possible when making requests. Outside of your start and end times, no requests are being made to Google. Between those times, requests are made every ten minutes, one for each destination configured.
-
@bob so how often do you refresh the data to stay under the limit of the “free” tier?
-
This post is deleted! -
Hi, yesterday this module stopped working for me, I reinstalled it using the default config and still not working, I don’t even get the “loading” message
Anybody else?
Thanks
-
Hi, mine was working fine for me this morning.
-
@j-e-f-f - Thanks for creating this module.
I have a question - is it possible to use the Origin property inside the destination objects? The use case is that i’ll like to display the commute to work in the morning and in the evening display the traffic back from work. I believe this will be possible if origin can be defined at each destination level. -
@yupwho no, the module doesn’t work that way. However you can define a second instance if the module and use your work as the origin and route your way home. However it wouldn’t be an accurate representation of commute time because the module reflects current traffic patterns. So it might say your trip home right now is 20 minutes but it might actually be an hour at the time you actually commute home.
-
Does this module still work? I’ve just installed it and get nothing other than “Loading…” no matter what I try. I’ve used the example config (with my own API key) and tried a number from scratch and nothing works.
The MMM-Traffic module this is based on is installed and works so I know my API is working. Anything dumb I should check for to make sure I’ve not screwed up?
Edit: Solved it. When running in Docker I needed to restart the Container for the API key to get picked up and work.
-
@looking Hi looking, I’m having the same an error display how did you solved it ? thanks in advance, FS
-
Is this modul working also in germany?
