I will look at v4 and contribute what I can. I appreciate your efforts and good work.

With respect to the MagicMirror installation location, I am resolving this on my end by creating a symbolic link in the user’s home directory if no MagicMirror directory exists there. The symbolic link points to the detected MagicMirror location. This will make my code compatible with modules that assume /home/pi/MagicMirror/modules is where they are installed. I don’t think non-standard MagicMirror install location is very common but I prefer placing it in a location all users can access. Anyway, this change is not high priority and I agree it can wait till we have something agreeable in v4.

The installer/rebuild.sh and installer/update.sh scripts attempt to:

cd ~/MagicMirror/modules/MMM-GoogleAssistant

The assumption that MagicMirror was installed in the user’s home directory is almost always correct but, in my case, not so. I have installed MagicMirror in /usr/local/MagicMirror. This same assumption is also made by the MMM-Detector scripts and maybe other modules as well.

I am able to work around the issue by editing the installer scripts prior to running an update or rebuild. I do not know if you wish to support alternate MagicMirror installation locations in your installer scripts but if you do, here is what I do in my scripts:

MM=${HOME}/MagicMirror

[ -d ${MM}/config ] || {
      MM=
      for homedir in /usr/local /home/*
      do
          [ "${homedir}" == "/home/*" ] && continue
          [ -d ${homedir}/MagicMirror/config ] && {
              MM="${homedir}/MagicMirror"
              break
          }
      done
}

Alternately, the update and rebuild npm commands are being run in the module’s installation directory so is there really a need to change directory using an absolute pathname? Maybe it is preferable to simply cd .. or not at all? I leave it up to you, just letting you know that the scripts break on some MagicMirror installations.

I’ve submitted a pull request at https://github.com/2hdlockness/MMM-IronManGIF/pull/2

This pull request adds two config settings, rotate and updateInterval. The rotate config parameter is a boolean that controls whether the module should rotate through the gif images. The updateInterval config parameter is an integer that specifies the duration of display of the current image in milliseconds. Defaults for these new config parameters are false and 300000 (5 minutes) respectively.

This is accomplished by adding a scheduling function that sets the update interval using setInterval()

Let me know if you would like further clarification on the implementation or if I need to modify the pull request in any way.

That works nicely, thanks. However, it only works in some positions and others will require different css settings. But, for now, I am pretty happy with this overlay of modules. It’s cool.

Possibly at some point in the future I might try integrating the clock into the IronManGIF module with an option to display it. That way it the clock and the gif would be occupying the same geometry. Or, maybe that’s too much work just to be able to easily switch positions. Anyway, thanks!

Pretty cool! What is your CSS to get the clock overlay?

I was debugging another issue and noticed errors in the dev console with MMM-GoogleAssistant when it was setting the album cover background image. The album it was using to access a cached album id was undefined. So accessing the id property of this undefined object threw an exception.

Is this something wrong with my cache?

I modified components/extented.js at line 714 to check if the album was undefined:

if (typeof album != 'undefined') {
    albumCover.style.backgroundImage = `url(modules/MMM-GoogleAssistant/tmp/cache/${album.id})`
}

This got rid of the dev console errors but why is it trying to access an undefined album object?

@doctorfree