Default weather module stuck loading after latest MM update

butchkemper

The Api has changed and the old apikey no longer works. The old api, V2.5, provided data for free and the new api, V3.0, will charge for daily data access requests that exceed 1,000. The new api requires a credit card to bill for all requests exceeding 1,000 per day.

In addition to establishing a credit card on my account and generating a V3.0 key, I installed the MMM-OpenWeatherForecast module using these instructions:

Navigate into the MagicMirror modules directory.
Execute git clone https://github.com/Tom-Hirschberger/MMM-OpenWeatherForecast
Enter the new MMM-OpenWeatherForecast directory and execute npm install

The configuration instructions and other information is located in:

Read the instructions in the README.md file.

Butch

JMac

@karsten13 how do I update this specifically.

Everything was working fine prior to the latest MM update.

JMac

@butchkemper Is this the default weather module or an additional one?

sdetweil

@JMac if you had used my upgrade script, it would have upgraded node as well

see https://github.com/sdetweil/MagicMirror_scripts

you can use the upgrade again with the parameter of

force

instead of

apply

JMac

So I’ve run your update, and the weather still doesn’t load.

Seems odd that the API issue would only arise following the update.
Is this likely?

sdetweil

@JMac the provider announced that the old 2.5 API would be sunset in June of this year… we didn’t get that update into the last version…

v3.0 is the ONLY one we provide default for…

starting with MM version 2.29

you MUST get a new v3 api key , which requires a credit card.
the 1st 1000 calls to the new api are currently not charged

JMac

@sdetweil So I’ve upgraded to my account on OpenWeather (and added payment details.
Generated a new APIkey and added this to the config of the weather module but it is still stuck on loading.

sdetweil

@JMac can you look at the messages from npm start

the ‘loading…’ message is just to have something on the screen until data arrives

and as such it didn’t arrive.

can u post the module config (xxx out your apiKey)

Peter

@sdetweil same problem here.
Upgraded my Openweather account, added paymentdetails (seemed to worked well), generated a new API key (how can I see it is a 3.0 key?)
Used your upgrade script, Sam.
Entered the new key in my config.
Everything works fine except the default weathermodule.
Peter

Peter

This is my config, maybe somebody can tell me what is wrong?

{
module: "weather",
position: "top_right",
config: {
weatherProvider: "openweathermap",
type: "current",
location: "Apeldoorn",
locationID: "2759705", //ID from http://bulk.openweathermap.org/sample/city.list.json.gz; unzip the gz file and find your city
apiKey: "xxxxxxxxxxxxxxxxxxxxxx"
}
},
{
module: "weather",
position: "top_right",
header: "Weersverwachting",
config: {
colored: true,
weatherProvider: "openweathermap",
type: "forecast",
location: "Apeldoorn",
locationID: "2759705", //ID from http://bulk.openweathermap.org/sample/city.list.json.gz; unzip the gz file and find your city
apiKey: "xxxxxxxxxxxxxxxxxx"
}
},