Default weather module stuck loading after latest MM update

JMac

I’ve just updated the MM to the latest version, everything seems to have gone fine except the default weather module, which is now stuck in a “loading” phase.

I found an older post saying the newer version of this module needed an APIkey over an APIid but the MM setup is newer than this post so already has this change.

Has anyone had this same issue since this latest update, or have any ideas how to sort this?

Seems I can’t even update the MM without causing an issue.

for completeness I got this at the bottom of the update using
git pull && npm run install-mm,

npm ERR! code EBADENGINE
npm ERR! engine Unsupported engine
npm ERR! engine Not compatible with your version of node/npm: magicmirror@2.29.
npm ERR! notsup Not compatible with your version of node/npm: magicmirror@2.29.
npm ERR! notsup Required: {“node”:“>=20.9.0 <21 || 22”}
npm ERR! notsup Actual: {“npm”:“10.1.0”,“node”:“v20.8.0”}

npm ERR! A complete log of this run can be found in: /home/MagicMirror/.npm/_los/2024-10-06T07_38_42_762Z-debug-0.log

would these errors cause the issue I’m seeing?
cheers.

MaXi-XCeL

@Peter Found it in the documentation!

Note: Latitude and longitude are REQUIRED if weatherEndpoint is set to ‘/onecall’. The locationID and location options are ignored when the OpenWeatherMap One Call API is used.

https://docs.magicmirror.builders/modules/weather.html#configuration-options

karsten13

@JMac

npm ERR! notsup Required: {“node”:“>=20.9.0 <21 || 22”}
npm ERR! notsup Actual: {“npm”:“10.1.0”,“node”:“v20.8.0”}

mm needs a node version v20 or v22 and minimum version is v20.9.0, you are running v20.8.0

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)