Trouble Integrating MMM-OpenWeatherMapForecast with OpenWeather API v3.0

[sdetweil]

@Socrates do a git pull in the module folder to update the code

[Socrates]

@sdetweil
Thanks for your replies. I forgot to mention that, before posting this here, i did update the module. Infact to be on the safe side i renamed the folder MMM-OpenWeatherMapForecast to preserve it as a backup, and then used git clone to download the new module and ran npm install from within the MMM-OpenWeatherMapForecast folder.

[Socrates]

@sdetweil

Did a git pull no, luck.

[sdetweil]

@Socrates ok, edit the node_helper.js

and change the end of line 63 from

 HH:mm") + " ** ERROR ** " + error);

to

 HH:mm") + " ** ERROR ** " + response .statusCode);

then restart MagicMirror and look at the output of npm start

im guessing its 401, access denied

is your new apikey with a credit card?

[Socrates]

@sdetweil
Also wanted to let you know I am using one openweather api for a different module in mm and thats working fine, only this module its not working, the module wont even show up on mm screen.

[sdetweil]

@Socrates I took your config, used my v3 apikey and it works…

[Socrates]

@sdetweil
hello and good evening again. No i do not have a credit card on file with Openweathermap. Its a free tier.
Also, may i request you to guide me where to find the output file? I have mm on auto start while rebooting

[Socrates]

@sdetweil
So do i need to sign up for a paid API using a credit card? Or do u think there is an inconsistency with my MMM-OWMF module? I have made the changes to the node_helper.js file just as you suggested and restarted MM, still no avail.

[sdetweil]

@Socrates i believe the 3.0 free tier also requires a credit card on file…
they give you 1000 calls no charge per day, but if you go over they charge you
see the link ‘Pay as you call’

(vs prevent the api from working)
this is new for 3.0
the linked pages says

'One Call API 3.0 is included to the “One call by call” subscription plan only, users pay for the actual use of the product. '

if you are using pm2 to autolaunch then the output will be here

pm2 logs --lines=xxxx

where xxxx is the number of the most recent lines of the log to display,
default 15

you may need more

I always recommend using manual start mode while debugging, this makes the output easier to access

pm2 status 

will show the running apps

pm2 stop all 

will stop them all

manual start

cd ~/MagicMirror
npm start 

ctrl-c at the terminal or
ctrl-q on the mm screen to stop mm

once things are resolved

pm2 status
pm2 start x

where x is the number of the line for the app to start or the name on that line
0 or MagicMirror as shown below on one of my systems

┌────┬────────────────────┬──────────┬──────┬───────────┬──────────┬──────────┐
│ id │ name               │ mode     │ ↺    │ status    │ cpu      │ memory   │
├────┼────────────────────┼──────────┼──────┼───────────┼──────────┼──────────┤
│ 0  │ MagicMirror        │ fork     │ 5    │ online    │ 0%       │ 2.5mb    │
└────┴────────────────────┴──────────┴──────┴───────────┴──────────┴──────────┘

[sdetweil]

@Socrates said in Trouble Integrating MMM-OpenWeatherMapForecast with OpenWeather API v3.0:

restarted MM, still no avail.

all that change did was output the status code to the log , instead of the empty error

so, the log output will tell you
Im sure its 401

I hacked my apikey , and this is what the line should look like in the log

[2024-09-09 21:49:07.454] [LOG]   [MMM-OpenWeatherMapForecast] 9-Sep-24 21:49 ** ERROR ** 401