MMM-DarkSkyForecast - Yet ANOTHER weather module

Johans

@j-e-f-f
No, It doesn’t come back.
I made a new installation on fresh SD card.
All works fine without installing your module, after that it’s not working anymore.

Johans

When I run directly in the browser, it’s OK, but thats not the main goal, should run via the MagicMirror.

hco125

I posted an issue on your module link in GitHub, but no response yet. Please see this link for details. Both the config in the link as well as the one below do the same thing…loading infinitely.

		{
			module: 'MMM-DarkSkyForecast',
			header: "Weather",
			position: 'top_center',
			disabled: false,
			config: {
				updateInterval: 10,
				units: 'us',
				forecastHeaderText: "O'Neill, NE",
				iconset: '5c',
				apiKey: 'blocked for privacy',
				latitude: '42.457649',
				longitude: '-98.647789',
				forecastLayout: 'tiled',```
			},
		},

lavolp3

@hco125
Time to go do some debugging. Ican imagine noone will be able to help you with the information given.

Please do the following:
Start the mirror in dev mode

npm start dev

OR

Open the mirror webpage on another browser (MIRRORIP:8080), press F12 for dev mode

In both cases, try to find error messages referring to this module and post them here.

hco125

I stripped down my MagicMirror configuration as well, so that we know that another module is not interfering. The modules that ARE on this config include: alert, updatenotification, MMM-ModuleScheduler, clock, MMM-AlarmClock, MMM-DarkSkyForecast, and MMM-Screencast. Here are the errors in the console running MagicMirror and accessing on Chrome with those modules running.

7
moment-timezone-with-data.js:472 Moment Timezone has no data for none. See http://momentjs.com/timezone/docs/#/data-loading/.
logError	@	moment-timezone-with-data.js:472
57
moment-timezone-with-data.js:472 Moment Timezone has no data for none. See http://momentjs.com/timezone/docs/#/data-loading/.
logError	@	moment-timezone-with-data.js:472
fn.tz	@	moment-timezone-with-data.js:554
getDom	@	clock.js:79
(anonymous)	@	main.js:110
updateDom	@	main.js:109
updateDom	@	main.js:514
updateDom	@	module.js:358
(anonymous)	@	clock.js:45

However, I then stripped ALL modules EXCEPT MMM-DarkSkyForecast and rechecked the console. I get NO errors, and the log is as follows, but the modules still loads infinitely, with no display of weather (see screenshot, below):

Initializing MagicMirror.
translator.js:201 Loading core translation file: translations/en.json
translator.js:224 Loading core translation fallback file: translations/en.json
loader.js:182 Load script: modules/MMM-DarkSkyForecast//MMM-DarkSkyForecast.js
module.js:469 Check MagicMirror version for module 'MMM-DarkSkyForecast' - Minimum version:  2.2.0 - Current version: 2.6.0
module.js:471 Version is ok!
module.js:477 Module registered: MMM-DarkSkyForecast
loader.js:152 Bootstrapping module: MMM-DarkSkyForecast
loader.js:182 Load script: vendor/node_modules/moment/min/moment-with-locales.js
loader.js:182 Load script: modules/MMM-DarkSkyForecast/skycons.js
loader.js:157 Scripts loaded for: MMM-DarkSkyForecast
loader.js:197 Load stylesheet: modules/MMM-DarkSkyForecast/MMM-DarkSkyForecast.css
loader.js:159 Styles loaded for: MMM-DarkSkyForecast
loader.js:161 Translations loaded for: MMM-DarkSkyForecast
loader.js:197 Load stylesheet: css/custom.css
MMM-DarkSkyForecast.js:138 Starting module: MMM-DarkSkyForecast
main.js:468 All modules started!
module.js:156 MMM-DarkSkyForecast received a system notification: ALL_MODULES_STARTED
module.js:156 MMM-DarkSkyForecast received a system notification: MODULE_DOM_CREATED
module.js:156 MMM-DarkSkyForecast received a system notification: DOM_OBJECTS_CREATED

So after adding in one module at a time to determine which one was throwing the errors I posted above, it is the default MagicMirror “clock” module, and I do not believe it is the cause of the MMM-DarkSkyForecast problems.

j.e.f.f

@johans @hco125 i believe your issues are related. If the module runs in the web browser, but not on the mirror, then we’re seeing an issue with the difference in JavaScript syntax supported by Chrome versus Electron. I’ll need to debug your configs in Electron running on the Pi, as the errors will only be seen in the browser console.

Sorry I’ve been slow to respond. I just got back from visiting family for the holidays so I haven’t been checking this forum at all nor the issue list in my git repo. Will take a look and let you know if I find any problems.

djsunrise19

Looks very nice. Is there a way to get the “feels like” temperature, too? I can’t find anything about it.

hco125

@j-e-f-f & @lavolp3

I figured out the issue…idiot error (me). I typed the config option as “apiKey” instead of “apikey” and it wouldn’t read it as registered. So sorry for taking your time. Works now.

j.e.f.f

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

Looks very nice. Is there a way to get the “feels like” temperature, too? I can’t find anything about it.

I’m planning to add it. This is something I’d like as well.

j.e.f.f

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

@j-e-f-f
No, It doesn’t come back.
I made a new installation on fresh SD card.
All works fine without installing your module, after that it’s not working anymore.

Can you try something? Completely remove MMM-DarkSkyForecast (i.e.delete the directory with rmdir -rf MMM-DarkSkyForecast), and comment out the entry in the config. Restart MM. Does your player come back now? If so, try this:

Reinstall my module using git clone ... but DON’T run npm install in the MMM-DarkSkyForecast directory. All of the dependencies are currently included with Magic Mirror, so it should work as-is.

Put the DarkSky entry back in your config and restart MM. If everything works then the issue is that my module is installing a different version of one of the dependencies than what is included in MM, and likely is causing the incompatibility with the MMM-Widget module.