@sdetweil said in MMM-ModuleScheduler update:

@Canguingo no, I was asking, did the command

git pull

work.

so, go there again and do the git pull and show the results

Thanks Sam.

It seems I had to delete some files from the ModuleScheduler before in order to get git pull to work.

Now it looks it’s working.

Many thanks!

@sdetweil said in MMM-ModuleScheduler update:

@Canguingo did the git pull succeed?

Not really,

I went to MagicMirror/modules/MMM-ModuleScheduler and there I did the git pull
and the npm install.

Then back to root and a sudo reboot.

But did not help the issue.

I might miss something, a step or something… dunno.

@DarrenHill said in New Weather Module - Migration:

@Canguingo said in New Weather Module - Migration:

apiKey: “abcde12345abcde12345abcde12345ab” //this is the old appi that i had

Is that really your actual key, or did you just put that as a redaction of your actual key?

Just to ask a basic question, as that doesn’t look like a valid key to me.

As the others have noted, all you should need to do is change the module name and swap the key label from appid: to apiKey: , The key value itself is valid for both.

Many thanks Darren,

That’s a dummy key not the real one. I managed to get it running.

The issue was (for the record):
Mistaken “apiKey” for “appi”
Missing ‘currentweather’ part which has also been replaced by the new module. So the code was wrong and missing a calling a module that does not exist anymore.

Again many thanks!!

@sdetweil said in New Weather Module - Migration:

@Canguingo well, there are more new parms…

provider
and type (as they collapsed current and forecast into the same module now)

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

my question is: Do I need a new apiKey or with the value of the old appi is enough?

if you don’t know the answer or don’t know how to explain it, I thank you a lot, but please leave space for someone who actually can help.

thank in advance.

@sdetweil said in MMM-ModuleScheduler update:

@Canguingo what doesn’t?

linux is case sensitive…

cd ~/MagicMirror/modules
cd modulename
git pull
npm install

great now i’m 28 commits behind instead of 19 …

@sdetweil said in New Weather Module - Migration:

@Canguingo well, there are more new parms…

provider
and type (as they collapsed current and forecast into the same module now)

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

so what do i have to do?

@sdetweil said in MMM-ModuleScheduler update:

@Canguingo well, modules are loaded into the

MagicMirror/modules folder

so your command will work from there

thanks this doesnt work

@sdetweil said in New Weather Module - Migration:

@Canguingo you are just changing the label of the apikey value in config.js

@sdetweil

this is how my config.js looks like

{
module: “weather”,
disabled: false, //false, true
position: “top_right”,
header: “Weervoorspelling”,
config: {
type: “forecast”,
location: “Amsterdam”, // my own location
locationID: “454545”, //id my location
apiKey: “abcde12345abcde12345abcde12345ab” //this is the old appi that i had
}
}

so i need a new apiKey or with the old one is ok?

@sdetweil said in MMM-ModuleScheduler update:

@Canguingo no updates for mm are automatic

to update a module. go to it’s folder and type

git pull

if that is successful, and there is a package.json file, then also do

npm install

then restart MagicMirror

Ok! So I type cd mmm-modulescheduler or something like that?
Sorry I usually follow the instructions very carefully without really knowing what I do.

Hi there,

I have updated to the last version of MagicMirror. besides some issues with the weather module (see my other threats) i get a warning to update the MMM-ModuleScheduler module. it is 19 commits behind.

What? Does this not update auto?

any suggestions?

many thanks in advance!