Read the statement by Michael Teeuw here.
Default weather module stuck loading after latest MM update
-
@butchkemper Is this the default weather module or an additional one?
-
@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
-
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? -
@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 -
@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. -
@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)
-
@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 -
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" } },
-
@Peter ok, two things…
you ALSO have to add
weatherEndpoint: "/onecall",
to each config, as this is required for the 3.0 api
this makes it work with my 3.0 apikey
second,
in the forum, when you post config, or log info, please use the code block wrapper… else the quotes get changed to workd processing type which JS doesn’t understandto do
paste the text into the editor, blank line above and below
select the text just pasted
hit the </> button above the editor -
@sdetweil Thanks, You solve a 2 weeks headache problem wit this line:
weatherEndpoint: “/onecall”,