Read the statement by Michael Teeuw here.
MMM-MyCommute
-
@leem2000 if it has a package.json file, yes, and if the instructions say so, yes
gotta follow the instructions
-
Hi,
I have been installing this module on 2 MagicMirrors.
It’s running 24/7 and I check travelling time to 4 destinations (so, 8 with both mirrors).Today I got an email, that after about only 2 weeks or so, there are just 25€ remaining of my testing period and 300€.
I do not have any other projects and I’ve checked the Dashboard, there have been more than 45000 queries to the directions API so far.
First thing I did: Limited the module on both mirrors to run only at daytime. But as I have different work locations and shifts, this is not so good. And, of course, I dont want to generate queries for a real amount of cash…
What should I do? Is this normal?
-
@requiemmg yes, I got a warning too from google, 4 mirrors, asking every 5 minutes, the api query counts add up fast… 8,000 calls a week…
-
Okay, so no way to limit API calls? Would it be possible to call every 10 minutes or so and only every 60 minutes in the “non-active” time?
-
@requiemmg if someone changes the code, sure. can do almost anything. I support another mirror app which does provide for a interested time period. (rush hour), and doesn’t call API outside that time period if set
-
Okay, played around a bit. Set the module to show times only from 5am to 5pm. And I added a “pollFrequency: 15 * 60 * 1000,” to my config.
While the first one works (the module disappears at night), the second one does not seem to work:
This is the Traffic from the last 2 days. You can see the requests are paused last night. I made changes to the poll frequency yesterday in the afternoon, no change.
The module used up nearly all of my €300 starting balance. I wonder if this will go on like this.
API calls in the last 48 hours:
API calls in the last ONE hour:
Which I do not understand: No errors. Poll Frequency of every 15 Minutes. 2 Mirrors with 4 destinations each. So 4*8=24 API calls/hour would be what I expect to see…
-
@requiemmg 352/hour is 5.87 per minute, about once every 12 seconds… once every 24 seconds both of 2 machines.
1 looked at the code, 1 api request per destination.
-
Raised an issue. Seems like the problem comes with the use of MMM-Pages, so on every reload of the page, the module is loaded and the requests are sent again, even if the data is still up to date. @qistoph was so nice to make a fork to address this issue.
-
@requiemmg yep, separate instance on every page.
-
This makes it clear why I had about 50.000 requests, which made my $400 starting balance void…well, with the new fork and some config modifications, this is much better.
