New Weather Module - Migration

[Canguingo]

@DarrenHill said in New Weather Module - Migration:

@Canguingo You need to put in your key (which used to be in the appid entry in your old config) into the apiKey entry there. What is listed is just a default dummy one in the example you quote.

I’m actually just doing the update myself at the moment, and now tweaking the newer module to emulate the appearance of the old two.

Can you post your old config.js entries for the modules (removing key strings and anything else you want to keep private) and then we can try to get your new version transposed across. Just finished mine, now minor tweaks ongoing.

Hey Darren,

Many thanks. I did the update of the MagicMirror, and changed the code in the config file. Do I need to update in anyway the Weather Module as well, or with the code in config file is enough?

I have added the api etc indeed, and I only see “data uploading” but nothing else.

Any suggestions?

Many thanks!

[Canguingo]

@JerryP said in New Weather Module - Migration:

@Canguingo said in New Weather Module - Migration:

Hi there,

I have made the latest update of MM and got an error because the Weather Module is Deprecated (wonder whether this could be updated in the last update of MM as it is an standard module, anyway).

I am trying to add the config file the following code:

{
module: “weather”,
position: “top_right”,
config: {
type: “forecast”,
location: “Amsterdam,Netherlands”,
locationID: “”,
apiKey: “abcde12345abcde12345abcde12345ab”
}
}

as suggested in https://docs.magicmirror.builders/modules/weatherforecast.html#migration.

but this doesn’t solve the issue.

Is there any way to migrate from the old version of Weather Module to the new one?

Many thanks in advance!

		{
			module: "weather",
			disabled: false, //false, true
			position: "top_right",
			config: {
					type: 'forecast',
					location: "Heemskerk",
					locationID: "2754696",
					apiKey: "https://openweathermap.org/api",
					fade: false,
					colored: true,
		}},

Hi Jerry,

I indeed added the IDs and apikey. But nothing is loading. Do I need to update the Weather Module as well? I thought this was done automatically.

The rest of the code is same as yours but with my location and apikey.

Many thanks!

@JerryP said in New Weather Module - Migration:

@Canguingo said in New Weather Module - Migration:

Hi there,

I have made the latest update of MM and got an error because the Weather Module is Deprecated (wonder whether this could be updated in the last update of MM as it is an standard module, anyway).

I am trying to add the config file the following code:

{
module: “weather”,
position: “top_right”,
config: {
type: “forecast”,
location: “Amsterdam,Netherlands”,
locationID: “”,
apiKey: “abcde12345abcde12345abcde12345ab”
}
}

as suggested in https://docs.magicmirror.builders/modules/weatherforecast.html#migration.

but this doesn’t solve the issue.

Is there any way to migrate from the old version of Weather Module to the new one?

Many thanks in advance!

		{
			module: "weather",
			disabled: false, //false, true
			position: "top_right",
			config: {
					type: 'forecast',
					location: "Heemskerk",
					locationID: "2754696",
					apiKey: "https://openweathermap.org/api",
					fade: false,
					colored: true,
		}},

[DarrenHill]

@Canguingo Nothing needs to be done in the module, it should already have been there in parallel to the old ones for the last few versions of MM.

All you need to do is make the changes in config.js as detailed on the migration/depreciation part of the documentation. That will switch you over from the old modules to the new one.

What has happened with the 2.19 update is the old modules have basically been removed and just replaced with the notification that you see on the mirror screen now (and that will also presumably be removed going forward).

The config.js entry should look something like the template version you posted originally, except of course you will need to use your own specific API key rather than the abcde12345 placeholder and your specific location (unless you happen to be in Amsterdam).

[JerryP]

@DarrenHill
The config is “apiKey” and in the old config i’ts “appi”

So please check the typing.

[Canguingo]

@DarrenHill said in New Weather Module - Migration:

@Canguingo Nothing needs to be done in the module, it should already have been there in parallel to the old ones for the last few versions of MM.

All you need to do is make the changes in config.js as detailed on the migration/depreciation part of the documentation. That will switch you over from the old modules to the new one.

What has happened with the 2.19 update is the old modules have basically been removed and just replaced with the notification that you see on the mirror screen now (and that will also presumably be removed going forward).

The config.js entry should look something like the template version you posted originally, except of course you will need to use your own specific API key rather than the abcde12345 placeholder and your specific location (unless you happen to be in Amsterdam).

thanks.
So i did what you suggested. just added/changed the config.js and it looks exactly like yours.
still not working. do i need to ask for a new api key? i already had one for the previous version.

[Canguingo]

@JerryP said in New Weather Module - Migration:

@DarrenHill
The config is “apiKey” and in the old config i’ts “appi”

So please check the typing.

yes i just mixed up the terms in this threat. do you mean i need a new apikey different than the old appi i already had?

[sdetweil]

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

[Canguingo]

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

@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

[Canguingo]

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

@Canguingo i dpn’t know exactly… read the doc and check to see if you have all the required parms…

[Canguingo]

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

[JerryP]

@Canguingo
I’dint use a new key. The old one was working fine.
After I update the Mirror to 2.19 and change the config.

[DarrenHill]

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

[DarrenHill]

For reference, this is one of the entries in my config.js (I use the module twice, once for now and once for forecast):

        {
            module: "weather",
            position: "top_left",
            config: {
                type: "current",
                location: "Manchester",
                locationID: "", //ID from http://bulk.openweathermap.org/sample/city.list.json.gz; unzip the gz file and find your city
                apiKey: "#####f59935f34cea0bf3c1aa82#####",
                units: "metric",
                degreeLabel: true,
                showHumidity: true,
                tableClass: "medium"
                }
        },

Where the #'s in the apiKey are actually other letters and numbers (full key redacted).

[Canguingo]

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