New Weather Module - Migration

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