About 3 days ago, my darksky sensor or weather more than doubled it’s number of requests and now is exceeding the allowed amount. I had the sensor set to 30 minutes, and it wasn’t going over about 550 a day previously with both the weather and sensor enabled. Now it runs out quite quickly. Was this broken in 0.84.6 when they added the additional days to the forecast? As soon as I fixed that, it started having this problem. Here’s my settings for the weather and sensor:
So I disabled the darksky sensor completely, and it appears that the darksky weather component by itself is consuming pretty close to 1000 API calls per day, despite saying in the docs that it should only consume 480… Looks like someone changed that without thinking about those of us that like to use both the sensor and weather component. I’m changing the subject of this thread to reflect that it’s the weather component rather than the sensor which is the problem. Is anyone using both of them successfully in 0.84.6?
You are talking about only the darksky sensor then, as the weather component doesn’t have the setting for polling interval. I have isolated the problem as being in the weather component now.
No problem, it took me quite a while to figure out that there were 2 separate components as well… Once I did I wanted both of them, hence the problem I have now, where the weather component isn’t leaving enough API calls for the sensor to function.
I’ve migrated to the Darksky weather componente since yahoo weather is deprecated. I now have both a sensor and weather components from Darksky running on my machine and I see double the usage of calls since then.
It seems to be 0.84.6 specific then. It also used to work correctly for me in 0.83.2, and I was successfully running both the sensor and weather component. Now unfortunately the weather component alone hogs up all the API calls, I can only run the sensor with a 2 hour refresh interval which isn’t really enough for my purposes.