MMM-OpenWeatherForecast

Ray

@wishmaster270
I totally agree with everything you said I do have two keys but I only use one
the only thing I can think of is maybe the 20 calls are a carryover from the previous day that’s the only thing I can think of
I shut down my mirror around 7 o’clock at night

and when I started up in the morning around 8 o’clock in the morning I would think there would only be one call
but when I looked it said there were 20
so like I said maybe it’s a carryover from the previous day

so tomorrow morning I’m going to conduct a test
I will check the website first to see if there any calls there before I start my mirror

if you want I will let you know

Ray

@wishmaster270
so I found out what was going on with the calls being counted when my magic mirror wasn’t even up and running

so here’s what I found out
I have MMM-OpenWeatherForecast checking the temperature in two time zones
and one of the time zone I have set requestDelay: 250
this was done before the upgrade to 3.0 call abb
since then I have deleted one of the time zones
but forgot to delete requestDelay: 250 an error in my part

it turns out that the One Call API 3.0 was counting all the calls in that 250
in version 2.5 we didn’t have to worry about that

sdetweil

@Ray yes, a call is a call. 250 is WAY TOO OFTEN for weather that doesn’t changed but every 10-15 minutes

Ray

@sdetweil
I just thought I’d throw it out there in case someone else runs into the same problem

JohnGalt

@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.

sdetweil

@JohnGalt the default weather broadcasts it’s data just like calendar does

So the othermodules could use it

wishmaster270

Just to make clear.
The requestDelay is only used for the time between the start of the mirror and the first fetch of the data.
For all following the updateInterval 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

butchkemper

@JohnGalt

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

hrjmsh

@OldGuyBerlin Worked for me, thanks.

chris1971

I had the same problem with my weather forecast. I made a subscription for an API 3.0 key and modified the config in this way:

{
		module: "MMM-OpenWeatherForecast",
		position: "top_right",
		header: "Wetter in Mülheim",
		config: {
        apiBaseURL: "https://api.openweathermap.org/data/3.0/onecall?",
        apikey: "xxxxxxxxxxxxxxxxxxxxxxxx", //only string here
      latitude: 51.xxxxxxxx,            //number works here
      longitude: 6.9xxxxxxxx,          //so does a string
      updateInterval: 45,
	iconset: "3c",
	maxDailiesToShow: 4,
	maxHourliesToShow: 4,
	label_hourlyTimeFormat: "k[ Uhr]",
	label_sunriseTimeFormat: "k:mm",  // change the format for this one 
	label_days: ["So", "Mo", "Di", "Mi", "Do", "Fr", "Sa"]

In addition I added “https://api.openweathermap.org/data/3.0/onecall?” as mentioned by @Ray in the node_helper.js in the weather module. The update intervall is 45 minutes - which means below 1000 calls per month
The module is running again!!!

Thx to this community and forum,
Chris