Nebraska

@robiv8

There is never enough time in a day!!!

I wish I had the skill to do it myself. I am struggling to figure out enough coding just to set up my config.js file.

If anyone would be willing to take a gander at the issue I posted on the developer’s GitHub page:

GitHub Issue

I haven’t had a response from Jopyth in over 9 days, perhaps a guru here is willing to provide feedback and/or a suggestion if this is even possible.

@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.

@cowboysdude I reached out to the developer on the GitHub repo by creating an issue there, with no response for quite some time.

Unfortunately, I do not know how to identify the css selector(s) you mentioned, nor how to verify if the modules are using the same ones or not. I am teaching myself programming bit by bit and it is a very slow and painful process.

Link to issue posted on MMM-GoogleTasks GitHub Repo, with further explanation below.

Bug Description:

• Both MMM-pages and MMM-Carousel modules and have this same issue. All modules are showing on one page only and no advance to another page is occurring, neither is it changing on a browser pointed to the MagicMirror URL, nor on the MagicMirror itself. Also, MMM-ModuleScheduler is not hiding the modules I specify.

System Info:

• PCB: Raspberry Pi 3B
• OS: Raspbian GNU/Linux 9 (stretch)
• Node version: 10.15.0
• MagicMirror Version: 2.5.0
• Running MagicMirror with pm2 on start

Screenshot

• Here is the jumbled mess, and my MMM-CalendarExt module never shows at all:
  

Module Configuration:

• MMM-Pages config:

{
	module: 'MMM-pages',
	config: {
		modules: 
			[['MMM-GoogleTasks', 'MMM-Gas', 'MMM-AlarmClock', 'MMM-NOAA3'],
			['MMM-SimpleLogo', 'MMM-CalendarExt']],
		excludes: ['alert', 'updatenotification', 'clock', 'MMM-Remote-Control'],
		animationTime: 0,
		rotationTime: 5000,
		delayTime: 0,
	},
},

• MMM-ModuleScheduler config:

{
	module: 'MMM-ModuleScheduler',
	config: {
		notification_schedule: [
			//TURN SCREEN ON AT 05:00 AM EVERY DAY
			{notification: 'REMOTE_ACTION', schedule: '30 5 * * *', payload: {action: 'MONITORON'}},
			//TURN SCREEN OFF AT 01:00 AM EVERY DAY
			{notification: 'REMOTE_ACTION', schedule: '00 1 * * *', payload: {action: 'MONITOROFF'}},
			//RESTART THE RASPBERRY PI DAILY AT 02:00 AM
			{notification: 'REMOTE_ACTION', schedule: '00 2 * * *', payload: {action: 'REBOOT'}},
		],
		schedulerClass: 'scheduler',
		animationSpeed: 0,
		global_schedule: {
			from: '00 0 * * *',
			to: '01 0 * * *',
			groupClass: 'hide_module',
		},
	},
},

• And this module does not hide:

{
	module: 'MMM-AlarmClock',
	position: 'top_center',
	classes: 'hide_module',
	config: {
		alarms: [
			{
				time: '09:27', //must be 24 hr format
				days: [1,2,3,4,5], //Sunday=0, Saturday=7
				title: 'KBRX - Party Line',
				message: 'Party Line',
				sound: 'http://162.244.81.209:8032/stream?autoplay=1',
				volume: 1.0,
				touch: false,
				format: 'ddd, h:mm A',
				timer: 1.15 * 60 * 60000, //change first operand to specify hours
				fade: false,
				fadeTimer: 60 * 1000, //change 1st operand to specify seconds, how long fade into alarm before volume is set
				fadeStep: 0.005, //0.5%, inc volume this percent amount each second until fadeTimer is reached
				popup: false,
			},
		],
	},
},

Console Errors:
The following are the ONLY errors that showed in the console, and I discovered by process of elimination that the moment-timezone errors are caused by the MagicMirror default “clock” module.

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
TypeError: Cannot convert undefined or null to object
at Function.keys ()
at Class.getDom (MMM-GoogleTasks.js:87)
at main.js:110
at new Promise ()
at updateDom (main.js:109)
at main.js:53
at Array.forEach ()
at createDomObjects (main.js:24)
at Object.modulesStarted (main.js:471)
at startModules (loader.js:59)

Helpful Hints:
Then, by another module elimination process, I discovered that disabling/deleting MMM-GoogleTasks from the config.js file makes MMM-pages, MMM-Carousel, and MMM-ModuleScheduler run as expected.

This is bugging me, since really look forward to using MMM-GoogleTasks on my Mirror, and I must be able to switch out pages of modules since I am using it for an advanced personal assistant and family organization center.

Please help.

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.

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',```
			},
		},