Version 2.30.0 weather module, stuck loading, worked fine before upgrade

[sdetweil]

@Richard238 yes they told us the old free api was being terminated. only the new api exists, so we changed the defaults

but other users have reported the 2.5 apikey still works
see the 1st post on this topic

[Rberry91]

@sdetweil hi Sam,

I have added a credit card and added the extra codes from the article and it doesn’t load.

[sdetweil]

@Rberry91 if you have the 3.0 apikey you dont add any extra parms

just type, apikey, lat and lon

[Rberry91]

@sdetweil
It still says invalid date

Sorry so many questions

[sdetweil]

@Rberry91 open the developers window, ctrl-shift-i,
select the console tab,
and enter weath in the filter field

do you see errors? like 401, 403

[Rberry91]

@sdetweil
Hi yes error 401

[sdetweil]

@Rberry91 401 means the apikey is invalid

[Rberry91]

@sdetweil
Hi Sam,

So I got it to work however the header is Australia/Brisbane, which is not correct. But the weather details are correct, how do I change the name of the header. I have added location and locationID

[sdetweil]

@Rberry91 v3 does not return the right location,
location/id are not used in v3, only lat/lon

use the module header property

module:…
header:“…”

the set the weather config option

appendLocationToHeader:false,

[Rberry91]

@sdetweil
Hi Sam,

Now I have an message to update the MMM-GooglePhotos module. How do I do that without causing problems like before. I did try your code and it didn’t seem to work but I am most likely doing something incorrect

[sdetweil]

@Rberry91 didnt try my code? i do not supply anything that will update modules.

my upgrade script is only for base MagicMirror

every module upgrade is the same

cd ~/MagicMirror/modules/modulename
git pull
xxx see the module doc on what to do after
sometimes you need an npm install, sometimes not

[Rberry91]

@sdetweil

Hi again,
The MMM- GoohlePhotos was not updating so I re installed and am know getting a error of missing creditionals please help

[sdetweil]

@Rberry91 now you have to follow the module instructions to get authorization again

[Rberry91]

@sdetweil
I reverted to the older version and I have tried updating using your command and other ones and still doesn’t update tell me that “pulling without specifying how to reconcile divergent branches is etc”

The other problem I am having is the weather, the forecast works but the current Weather doesn’t and they are the same code.

[sdetweil]

@Rberry91 divergent branches sounds like you have both modules trying to merge to the same folder

delete then git clone again
the nan says the apikey is wrong

and you have a typo, MagicMirror is case sensitive

[butchkemper]

The configuration parameters I use are:

module "MMM-OpenWeatherForecase"
latitude and NOT lat
longitude and NOT lon
apikey and NOT apiKey   <----  Notice the "K"

Some MM configuration keywords have abbreviations but not all. The module README file gives the values for the keywords.

Also, since your apikey has been revealed to the world, you should cancel the posted key and generate a new key. Always keep the apikey secret.

Butch

[butchkemper]

@sdetweil I noticed this discretion between the Weather module documentation:

• The “Weather” documentation has “apiKey” - large case “K”,
• The “MMM-OpenWeatherForecast” documentation has “apikey” - small case “k”.

Butch

[sdetweil]

@butchkemper modules can go anything they want
what is used internally can be anything required

I looked at the doc for the default weather module before posting above. as there are two instances, one works the other doesn’t. apikey is the issue

[Assassins]

Work on 2.29.0 with api2.5

But now on 2.33.0
It say “NaN”
I get the error 401, it say the apiKey i wrong, but is write from my api key from the website.
How can i get a apiKey to api3.0 without to paid for it. ???
The api2.5 still work, but not on this modul.

    {
      module: 'weather',
      position: 'bottom_left',
      header: 'Ballerup',
      config: {
         lat: "55.7317",
         lon: "12.3633",
         apiKey: "xxxxx765xxxx98xxxjhx888"
       }
    },

[sdetweil]

@Assassins you cannot get V3 apikey from open weather without providing a credit card.
they don’t charge unless you go over 1000/request per day.

now, you CAN make 2.5 work (if they still accept api requests they keep telling us they are going to do (have done!!)) just be warned that they can/will end this function sometime…

in the module config section
apiKey: 2.5_key
apiVersion: 2.5

and

weatherEndpoint: “current” OR “forecast”

edited