Read the statement by Michael Teeuw here.
MMM-OpenWeatherForecast
-
@Ray yes, a call is a call. 250 is WAY TOO OFTEN for weather that doesn’t changed but every 10-15 minutes
-
@sdetweil
I just thought I’d throw it out there in case someone else runs into the same problem -
@Ray – Just for the sake of completeness for you or others I will mention here that the provider will count ALL calls, from ALL modules.
As an example I can have this module running for a comprehensive look at my local weather, plus an instance of the default weather module telling me what’s happening with a friend or relatives, plus I’m running MMM-DynamicWeather.
The API will count all the calls from all sources. It would be great if the MM system could pull the data and broadcast it to modules as needed, but that’s not how it works.
-
@JohnGalt the default weather broadcasts it’s data just like calendar does
So the othermodules could use it
-
Just to make clear.
TherequestDelay
is only used for the time between the start of the mirror and the first fetch of the data.
For all following theupdateInterval
in seconds is used.The module sends is weather info, too. But I think both modules are not capable of use the info provided by notification at the moment
-
The api call daily threshold for billing is 1,000. The default setting is to update every 10 minutes and that equals to 144 daily calls.
Butch
-
-
@OldGuyBerlin Worked for me, thanks.