MMM-OpenWeatherMapForecast stuck on Loading....

[sdetweil]

@ally said in MMM-OpenWeatherMapForecast stuck on Loading....:

0|MagicMir | [26.08.2022 12:24.33.069] [LOG] [MMM-OpenWeatherMapForecast] 26-Aug-22 12:24 ** ERROR ** null

isn’t that helpful!..

[sdetweil]

@ally i used your config from

https://forum.magicmirror.builders/topic/17141/mmm-openweathermapforecast-stuck-on-loading/1?_=1661513140571

with my openweather apikey and it worked without issue.

[sdetweil]

@ally edit the node_helper.js of the module and change this

                    } else {
                        console.log("[MMM-OpenWeatherMapForecast] " + moment().format("D-MMM-YY HH:mm") + " ** ERROR ** " + error);
                    }

to this

                    } else {
                        if(response.statusCode != 200) 
                        console.log("[MMM-OpenWeatherMapForecast] " + moment().format("D-MMM-YY HH:mm") + " ** bad status ** " + response.statusCode);
                            else
                        console.log("[MMM-OpenWeatherMapForecast] " + moment().format("D-MMM-YY HH:mm") + " ** ERROR ** " + error);
                    }

[ally]

@sdetweil any thoughts on why this is occurring on a fresh install of MM and this module? I also just checked the MM change logs and i am definitely running the latest version (## [2.20.0] - 2022-07-02).

Ally

[sdetweil]

@ally no idea. but without the code change, we won’t know what the error is…

only thing I can think of is the apikey has a leading or trailing space, making it bad

[ally]

@sdetweil yeah, I was worried that might be the case as well, which is why I went to a fresh install and left the original weather module using the same key.

Same key, same quotes, no spaces, default settings and this is the result.

Config is setup for default weather module current, then forecast and then MMM-OpenWeatherMapForecast, which is stuck on Loading.

[sdetweil]

@ally again need the startup messages w the new code

I copy/pasted the config u supplied exactly and change to my API key and it worked as expected. so it’s not a config problem.

it’s an apikey problem

[ally]

@sdetweil I deleted the old api key and made a new one, same result. The default weather modules load and this one doesn’t.

[sdetweil]

@ally what is the message from the terminal window w the new code?

[stevengill]

@ally I removed the location name (e.g. New York) and just used the locationID number and it started to work