MMM-GoogleTasks not compatible with MMM-pages, MMM-Carousel, or MMM-ModuleScheduler



  • 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:
      0_1546654556693_50533322-fd50c780-0aec-11e9-9ffb-6af110232030.png

    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.


  • Project Sponsor Module Developer

    Well sounds like a conflict of some kind. See for the fun of it if in the GoogleTasks is using the same selector from css or even in the main js file itself…OR ask the developer of GoogleTasks 🙂



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