MMM-OpenWeatherForecast - Replacement for MMM-DarkSkyForecast

[bassin12]

@sdetweil
When I try the code in the config.js I get this in the logs

[29.08.2022 10:22.03.630] [LOG] [MMM-OpenWeatherMapForecast] 29-Aug-22 10:22 ** ERROR ** null
[29.08.2022 10:22.03.639] [LOG] [MMM-OpenWeatherForecast] 29-Aug-22 10:22 ** ERROR ** Error: Request failed with status code 401

[sdetweil]

@bassin12 said in MMM-OpenWeatherForecast - Replacement for MMM-DarkSkyForecast:

[29.08.2022 10:22.03.630] [LOG] [MMM-OpenWeatherMapForecast] 29-Aug-22 10:22 ** ERROR ** null

yes, bug in his code…

use the code I posted on page one to extend the error reporting

but it returns 401 as well…

[DDE12]

Is there a solution for this error? Is it something I’ve done or something in the module code?

[MMM-OpenWeatherForecast] 12-Nov-22 23:49 ** ERROR ** Error: Request failed with status code 401

[sdetweil]

@DDE12 401 eror is unauthorized

so the apikey you are using has expired

[DDE12]

@sdetweil
I setup the default weather module with OpenWeather and it is working with the key I have. I obtained the key a few days ago. Is it the same key for MMM-OpenWeatherForecast?

[sdetweil]

@DDE12 no idea

the module says go here
https://home.openweathermap.org/users/sign_up
the default weather openWeathermap provide says
https://home.openweathermap.org/users/sign_in

so it would seem the same key

the module uses this path

https://api.openweathermap.org/data/2.5/onecall?"

the default module uses this

		apiVersion: "2.5",
		apiBase: "https://api.openweathermap.org/data/"
                        +apiVersion+"onecall?"

so, they appear the same

[DDE12]

@sdetweil
I put in a new key just to see but still have the same 401 error. When I installed the module I got

npm WARN old lockfile
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile

added 4 packages, and audited 391 packages in 50s

1 package is looking for funding
  run `npm fund` for details

39 vulnerabilities (2 low, 15 moderate, 19 high, 3 critical)

To address all issues, run:
  npm audit fix

Run `npm audit` for details.

I did not run audit fix. Is there something that I need to do with the install?

[sdetweil]

@DDE12 NEVER run audit fix…

i don’t know why the MMM-OpenWeatherForecast is failing ,
other than it says unauthorized. i would open an issue for the author.

[j.e.f.f]

@DDE12 Could you share your config? Also be sure put your API key in quotes in the configuration. If you aren’t using quotes, this could be a reason why the module is giving you the 401 error

[DDE12]

@j-e-f-f
I can, but I think I figured it out last night without changing anything in MM or the module. I initially signed up for the free account on OpenWeatherMap. Last night I signed up for the One Call by Call https://openweathermap.org/api and MMM-OpenWeatherForecast starting working. Before signing up, I tested my API in a browser at https://api.openweathermap.org/data/2.5/onecall?lat=someLatitude&lon=someLongitude&appid=secretAPI
and at https://api.openweathermap.org/data/3.0/onecall?lat=someLatitude&lon=someLongitude&appid=secretAPI
and both reported 401 error. After signing up, the module began working in MM. This does require a credit card and subscribers get 1000 free calls per day. Subscribers can set the maximum number of calls in their dashboard to prevent going over and getting charged. This doesn’t seem like it would be too much of a problem if users set the module’s config appropriately.

I’m guessing that the module is trying to get data that is no longer free and some API’s are grandfathered ?? Or I misunderstood what type of account I needed from the start.

Where is the API address in the module’s code?

Let me know if I can provide further information.