@sdetweil said in Upgrade Strecht to Debian 10 doesn't work:

@Canguingo buster is also outdated, bullseye is the current release.

I don’t think there is an upgrade path.

so I think you have to start w a new SD flash

I have some scripts that can help

backup the current mm config and modules list
install mm on the new os
restore the config and modules list

see https://github.com/sdetweil/MagicMirror-backup-restore

and to install mm
https://github.com/sdetweil/MagicMirror_scripts

ok, ok… just recovering from the shock.

When you say start with a new SD, you mean reinstall everything again? So delete mij SD card and reinstall everything? Pi and MM?
OMG! I don;t think I can survive this…

So what would be the process? First backup, your link.
Then …?

Thanks for your assistance… o my…

@sdetweil So I have to start all over again, and re install everything new?
What was the purpose to change to buster?

I have followed all the steps in https://raspberrypi.tilburgs.com/upgrade-stretch-to-buster/

But at the end when i check everything is all right I get
release 9,6
codename stretch

it seems i haven’t upgraded anything.

any ideas for normal people without indeph knowledge of coding, linux and pi?

many thanks for your assistance! very much appreciated!

Hi there,

I know this might be out of topic, but how do you connect your VCN to your MM? In Pi the VCN is outdated, but seems I cannot updated. At least I do not know what to do.

Any good samaritan that would like to help me?

Many thanks in advance!

Sorry guys, I am trying to upgrade my mirror to the new system, but it seems we have to make a backup. I wenst to the link https://raspberrypi.tilburgs.com/back-up-rpi/ but I need to create a folder in Synology NAS… what?! I have no clue what and how…

Could anyone help me please?

Many thanks in advance!

@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 …