MMM-OpenWeatherForecast

butchkemper

Howdy,

I am having trouble getting MMM-OpenWeatherForecast to run and have been working my way through the problems.

First problem was a typo of “apiKey” which caused this message to flood the .pm2/logs/MagicMirror-out.log. Problem solved by correctly spelling the variable name “apikey” - notice the subtle difference between the “K” and “k”.

[2024-10-03 10:22:54.732] [LOG]   [MMM-OpenWeatherForecast] 3-Oct-24 10:22 ** ERROR ** No API key configured. Get an API key at https://darksky.net

Once the “apikey” spelling problem was solved, the next error arrived and the log file was flooded with thousands of this message:

code_[2024-10-03 12:09:29.002] [LOG]   [MMM-OpenWeatherForecast] 3-Oct-24 12:09 ** ERROR ** Latitude and/or longitude not provided.

This error was caused by confusing documentation that made it appear the variables were “lat” and “lon” instead of “latitude” and “longitude”. Correcting the spelling eliminated the error messages.

The current problem is this message which is again flooding the pm2 error.log:

[2024-10-03 14:10:02.077] ^[[31m[ERROR]^[[39m ^[[31m[MMM-OpenWeatherForecast] 3-Oct-24 14:10 ** ERROR ** TypeError: fetch failed^[[39m

I need a hint of where to look or what to do. I sure it is not hard but just me overlooking something.

However,the three problems reveal that the Module contains an error that flood the log files with thousands of messages.

Here is the portion configuration file relative to the OpenWeatherForecast module:

                        module: "MMM-OpenWeatherForecast",
                        position: "top_right",
                        header: "Current Weather",
                        config: {
                                weatherProvider: "openweathermap",
                                type: "hourly",
                                units: "imperial",
                                tempUnits: "imperial",
                                roundTemp: true,
                                timeFormat: 24,
                                onlyTemp: false,
                                appendLocationNameToHeader: true,
                                showSun: true,
                                fade: false,
                                fadePoint: 1,
                                colored: true,
                                updateInterval: 900000,      // 15 minutes, 900 seconds
                                maxEntries: 10,
                                degreeLabel: true,
                                lang: "en",
                                location: "Sachse,Texas",
                                locationID: "4724564", //ID from http://bulk.openweathermap.org/sample/city.list.json.gz;
                                latitude: 32.98579,
                                longitude: -96.60234,
                                apiVersion: "3.0",
                                weatherEndpoint: "/onecall",
                                apikey: "This is a 3.0 key"
                        }

I am also confused about the updateInterval value. Previously in this module and in other modules, time intervals are given in milliseconds so 15 minutes is written as 900000.

Thank you for reading.

Butch

MarcLandis

@butchkemper it seems that you are mixing configuration for the standard weather module and configuration for MMM-OpenWeatherForecast

butchkemper

@MarcLandis Thank you for the push in the right direction. I took the time to remove all the unused options and corrected the updateInterval. Now everything is back to working.

Now I will need to study the new options to see if I need to change anything.

Thanks again.

Butch

Ray

So after getting everything set up with the new version 3.0 at openweathermap.org
I turned on my mirror for the first time this morning and it displayed the weather
and so I went to openweathermap.org just to check how many calls I made it already had me down for 20 calls
am I missing something here

sdetweil

@Ray how often is the module fetching the weather ?

wishmaster270

@sdetweil In default the module calls the Api every 10 minutes.

sdetweil

@wishmaster270 thanks. i knew i could go look, asking poster to do the same.

Ray

@wishmaster270 yes I have mine set for 15
but that doesn’t explain why when I turn it on for the first time in the morning they already have 20 calls I don’t get that

Ray

@sdetweil I have it set for 15 minutes

MarcLandis

@Ray said in MMM-OpenWeatherForecast:

@wishmaster270 yes I have mine set for 15
but that doesn’t explain why when I turn it on for the first time in the morning they already have 20 calls I don’t get that

What means “turn it on”? Boot up the Pi or turn on the screen?

Ray

@MarcLandis sorry for the misunderstanding there
when I activate my mirror and it checks the weather

MarcLandis

@Ray updates are still done even the screen is off.

Ray

@MarcLandis yes I get that and I totally understand that

but that’s not my question maybe it can’t be answered
my magic mirror is on a computer when I boot the computer up in the morning it will automatically start magic mirror usually the first thing it checks is the weather
if I turn the computer off there should be no more calls to the weather app

so my original question would be if I turn my computer on first thing in the morning and I go to the weather app why does it say I already have 20 calls that’s my real question

wishmaster270

@Ray
Hi, I do not know your set up nor do I know when the “in one day” changes to the next day at OpenWeaterMap.
I use the API Key exactly in this module and only have one instance of the mirror running…
I just checked my statistics at OpenWeaterMap and I do have at about 112 calls a day. Which is correct as my mirror is shutdown between 11:30pm and 5am.

Maybe it is a matter of your timezone and calls of the last day are counted in the current one.

What does your statistic look like

https://home.openweathermap.org/statistics/onecall_30

Edit:
And one small side note. Even if you use different keys the calls a summarized per account

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