Read the statement by Michael Teeuw here.
New Weather Module - Migration
-
@DarrenHill
The config is “apiKey” and in the old config i’ts “appi”So please check the typing.
-
@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. -
@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?
-
@Canguingo you are just changing the label of the apikey value in config.js
-
@sdetweil said in New Weather Module - Migration:
@Canguingo you are just changing the label of the apikey value in config.js
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?
-
@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
-
@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?
-
@Canguingo i dpn’t know exactly… read the doc and check to see if you have all the required parms…
-
@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.
-
@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.
