MMM-DarkSkyForecast - Yet ANOTHER weather module

[nobita]

@j-e-f-f Thanks for your hint ,I think I will new install MagicMirror and Darkskyforecast again

[lavolp3]

@nobita @j-e-f-f did not advise that. With the current information, I don’t think that helps.
You need to check the error logs as jeff hinted at by one of the ways described here in the forum several times.
One quick way is running the mirror with the command

npm start dev

and looking if there is an error message showing up on your console or in the browser if you access the mirror from another computer.

[motdog]

dumb question I’m sure but when placing this in the config.js I should get rid of the default weather program, right?

[sdetweil]

@motdog you could leave them both in for a little while to check that they both say the same thing!

[motdog]

@sdetweil I tried that & could not get dark sky to show up at all. That’s why I am confused

[sdetweil]

@motdog me too… can u open the developers console, and see if there are any errors?

either ctrl-shift-i (letter i) while MM is running,
or

npm start dev

to start with the dev console…

then select the console tab in the right handle white pane. scroll up to find any errors… in red text usually

[j.e.f.f]

@motdog said in MMM-DarkSkyForecast - Yet ANOTHER weather module:

dumb question I’m sure but when placing this in the config.js I should get rid of the default weather program, right?

You don’t have to. It will just mean you’ll have weather information from two sources. But one wouldn’t (shouldn’t ?) conflict with the other.

[motdog]

@j-e-f-f thats what I thought. Im just having all sorts of weird issues with both weather modules. I may just need to redo them

[motdog]

Ive got it up but when I change “table” to “tiled” I get a config error when I restart.

When I add units: us I get an error. Ugh.

This works```
//your cod {
module: “MMM-DarkSkyForecast”,
header: “Weather”,
position: “top_right”,
classes: “default everyone”,
disabled: false,
config: {
apikey: “*********”,
latitude: “38.751389”,
longitude: “-90.565948”,
iconset: “4c”,
concise: true,
forecastLayout: “table”
}
},e here

this doesnt 

{
module: “MMM-DarkSkyForecast”,
header: “Weather”,
position: “top_right”,
classes: “default everyone”,
disabled: false,
config: {
apikey: “*******”,
latitude: “38.751389”,
longitude: “-90.565948”,
iconset: “4c”,
concise: true,
units: us,
forecastLayout: “table”
}
},

[sdetweil]

@motdog always hide your apikey values. with ***

[motdog]

@sdetweil thanks. I finally got this module the way I wanted. On to the next one!

[j.e.f.f]

@motdog You have specified units without quotes. need to write it like this:

units: "us",

[Cr4z33]

@j-e-f-f I don’t know why, but when I use your module after a while MM becomes all dark although modules keep working (ie. MMM-AssistantMk2).

There’s no specific timing for the issue to appear (it can be after 1 hour or after 15 mins, etc.).

Modules won’t appear again until I restart MM.

This is my current module config:

		{
			module: "MMM-DarkSkyForecast",
			header: "Meteo",
			position: "top_right",
			classes: "default everyone",
			disabled: false,
			config: {
					apikey: "***",
					latitude: "***",
					longitude: "***",
					language: "it",
					forecastHeaderText: "***",
					label_timeFormat: "hh:mm",
					iconset: "4c",
					concise: false,
					showSummary: false,
					forecastLayout: "table"
				}
		}

[motdog]

@j-e-f-f yep. Thanks. Just lots of trial and error but it was set up how I wanted.

[Cr4z33]

@Cr4z33 said in MMM-DarkSkyForecast - Yet ANOTHER weather module:

@j-e-f-f I don’t know why, but when I use your module after a while MM becomes all dark although modules keep working (ie. MMM-AssistantMk2).

There’s no specific timing for the issue to appear (it can be after 1 hour or after 15 mins, etc.).

Modules won’t appear again until I restart MM.

This is my current module config:

		{
			module: "MMM-DarkSkyForecast",
			header: "Meteo",
			position: "top_right",
			classes: "default everyone",
			disabled: false,
			config: {
					apikey: "***",
					latitude: "***",
					longitude: "***",
					language: "it",
					forecastHeaderText: "***",
					label_timeFormat: "hh:mm",
					iconset: "4c",
					concise: false,
					showSummary: false,
					forecastLayout: "table"
				}
		}

@j-e-f-f you there? :smiling_face_with_open_mouth_cold_sweat:

[j.e.f.f]

@Cr4z33 I have not seen this behaviour… the module does not do anything to hide any modules including itself… you can examine the code for yourself to see. My guess is there is some unintended consequence of my module interacting with one of the other ones your are also using… Can you try disabling the other modules one at a time to see if the behaviour goes away? If it does, whichever was the last one to be disabled is likely the other party. We can start investigating what’s going on after that.

[sdetweil]

@Cr4z33 said in MMM-DarkSkyForecast - Yet ANOTHER weather module:

Modules won’t appear again until I restart MM.

that usually means MM has crashed… many times this is memory related… we know that the default updater module also causes a similar behavior

[Cr4z33]

@j-e-f-f OK, I’ve started disabling all other 3rd-party modules and enabling them one by one.

Apart from that what shall I look to then once there’s an issue between your module and the one of someone else? :)

@sdetweil so what do you suggest me to do? :thinking_face:
At first I thought that using MMM-WatchDog could sort the problem, but I feel like I misunderstood? :smiling_face_with_open_mouth_cold_sweat:

[sdetweil]

@Cr4z33 watchdog will just allow you to restart when it crashes… not capture why…

I still don’t have a good method for capturing these kinds of failures…

[Cr4z33]

@sdetweil oh I see, but then even if my MM doesn’t look like it restarted.

By now I am trying to see the overall behaviour with the Update module being disabled to see if the issue is still happening.