New Weather App (good bye DarkSky) creates config error

[Kastore]

Since DarkSky API is discontinued i looked for a new module.

So i wanted to go for the standard weather module which however creates a config error.

Would someone be so kind and help me out if it is a code error or if i have to download/install the weather module?

 {
			module: "weather",
    			position: "top_right",
    				config: {
      // See 'Configuration options' for more information.
				type: "forecast",
				units: "metric",
				roundTemp: "true",
				degreeLabel: "true",
				showPrecipitationProbability: "true",
				colored: "true",
				apiVersion: "3.0"
				lat: "12.123123"
				lon: "12.123123"
				apiKey: "abcdefgh"
    					}
  },

[Kastore]

@sdetweil
Hey there,

so as of today the module is now working . I had to remove the API Version as you mentioned and that helped. However it took another day for the module to work… no clue why it didnt work right away (despite “reboot” and “pm2 restart”)…

I am currently now trying to figure out how to get one Module working as “current” or “day forecast” so i know what the day brings and another with the “forecast”.

I am assuming i need to do multiple modules to get that done?

[sdetweil]

@Kastore trailing commas missing

[BKeyport]

To expand on what Sam said:

Please run npm run config:check in your MagicMirror directory after manually editing your config. You’ll find anything that breaks the entire mirror in one shot. If the module fails after the mirror starts, then come here.

[Kastore]

@BKeyport That one comes up with “no config file found”

[Kastore]

@sdetweil

{
   		module: "weather",
   			position: "top_right",
   				config: {
   			type: "forecast",
   			units: "metric",
   			roundTemp: "true",
   			degreeLabel: "true",
   			showPrecipitationProbability: "true",
   			colored: "true",
   			apiVersion: "3.0",
   			lat: "123.123123",
   			lon: "321.321312",
   			apiKey: "abcdefg",
   					},
 },

That still results in no display of the weather module :/

[sdetweil]

@Kastore the thing to the right of the :

if true , false, or numbers should not be in quotes.

if it contains a letter or symbol, then it should be in quotes

[Kastore]

@sdetweil

Can you please write me the code? I am seriously going mental over “not having anything loading” to “no config file” to just partially loading things…

This is really frustrating when you got 0 clue about coding to not figure out where the heck the issue is… ._.

This code doesnt create a missing config file but doesnt load the module. If i just enter the weather module (without config) it loads but only shows the current weather, but i would like to get the forecast for my region with the current API Version which is apparently 3.0

{
   		module: "weather",
   			position: "top_right",
   				config: {
     // See 'Configuration options' for more information.
   			type: "forecast",
   			units: "metric",
   			roundTemp: true,
   			degreeLabel: true,
   			showPrecipitationProbability: true,
   			colored: true,
   			apiVersion: 3.0,
   			lat: 123123,
   			lon: 312321,
   			apiKey: "asdasdasd123123asedasd123",
   					},
 },

[sdetweil]

@Kastore I used your exact config except my api key(i tried multiple keys) and lat/lon
I commented out the apiVersion:3.0,
and it works as expected

[Kastore]

@sdetweil
Hey there,

so as of today the module is now working . I had to remove the API Version as you mentioned and that helped. However it took another day for the module to work… no clue why it didnt work right away (despite “reboot” and “pm2 restart”)…

I am currently now trying to figure out how to get one Module working as “current” or “day forecast” so i know what the day brings and another with the “forecast”.

I am assuming i need to do multiple modules to get that done?

[sdetweil]

@Kastore said in New Weather App (good bye DarkSky) creates config error:

am assuming i need to do multiple modules to get that done?

yes, you just configure one instance as current and one as forecast

also, try this for the slow loading on the forecast instance
add

initialLoadDelay: 10, 

to the config parms