@Clubjack I had recently exactly the same issue with MMM-ioBroker, where I needed 2 instances of that module running. Finally, after some research I found the solution and documented in my private Wiki. Here is the documentation I wrote. After setting up that 2nd instance you can configure each instance separately and declare it in MMM-pages.
Here we go:
Problem
In some cases you may need to run 2 or more instances of the same module in MM, e.g. for public transportation. Some MMMs can then be put into config.js just on a different position and parameterized as needed. Unfortunatelly, not all MMMs support that.
The reason is that all those instances will share the same node_helper and therefore get the same socketnotifications.
Solution
To solve this problem you can try to duplicate the MMM with a different name and call it in the config.js. There is no guarantee that it works, but worth to try.
Following steps have to be done:
- Go to the modules folder and copy the whole module with a different name (in this example I’ll refer to MMM-ioBroker)
$ cd ~/MagicMirror/modules
$ cp -a MMM-ioBroker/ MMM-ioBroker2
- Go to ./MMM-ioBroker2 and change the .js of the module script accordingly
$ mv MMM-ioBroker.js MMM-ioBroker2.js
- Edit in MMM-ioBroker2.js the string to
Module.register('MMM-ioBroker2', {
…
- In some cases it might also be necessary to change the .css file name, too, incl. any reference to the instance name in the file.
$ mv MMM-ioBroker.css MMM-ioBroker2.css
And then edit or replace all occurences of ‘MMM-ioBroker’ with ‘MMM-ioBroker2’ in MMM-ioBroker2.css.