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

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

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