here: https://github.com/home-assistant/home-assistant/issues/2190
Unless one of you is on Windows, there wasn’t any reports of this on Windows in the thread. In fact, I was on Win10 and didn’t have the issue. And when I moved everything over to Pi, I’m still not having any problems.
Just to clarify.
cool!!!
that was fast! … I was still trying to figure it out how to create it!.
maybe you can add your setup as well so it becomes clearer
Weird. How about I send you my API key via PM? Just to test - not as a replacement fix! 
At least then you would be able to rule out the account as the issue. But please test it quickly - I don’t want to use up my requests!
I don’t think it’s the account. It’s at least several accounts.
Or it could be a similar issue with all the affected accounts. I just PM’d @davedan my API key to test so we can see for sure.
The same with me. A huge bill!!!
Same here. Response I got was
"According to our records, that’s not the case: you’ve used $20 or so worth of traffic in the last month. I assume you’re uninterested in paying for the traffic, so I’ve capped your account at the free limit of 1000 req/day: if you ever want that lifted, please contact me."
So also since updating
Fix from https://github.com/home-assistant/home-assistant/pull/2191 seems to resolve it. I manually updated the source until there is a release and not seeing all the API requests anymore.
1 Like
Good catch. Reminds us to check issue requests in github. I just solved a similar problem with Google Travel Time not having a default mode specified (which is also being fixed in the next release). I should have checked for this as well but I wasn’t having the issue myself and thought someone would have looked.
Another method in the interim would be use the scan_interval parameter. I have mine set at 180 (seconds) and haven’t run into any issues.
That was exactly what I suggested to the users in the other thread I referenced.
I have scan_interval = 900, but even then I have the same problem!
Same issue here unfortunately. I disabled the forecast.io sensor right away after I got the e-mail. However my outstanding amount is $53.66 
After upgrading to 0.20.3 it seems to be fine again… (so far)
wow i am not the only one… i got the email from them i am went over or something … something not right…
Folks this is fixed in the new release - please update and then post here if you still have the issue!
the docker image is not updated (yet)