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)
Did you put in an issue at github?
Same problem here. Also got the mail two days ago.
Did anyone contact them and explain what happened? I am actually not really happy to pay $90 for that. 