Not all modules can run two instances by just adding a second config entry with different values. Some modules, NOT ALL, can be “tricked” into running two instances with different values. Here’s how:

1. Make a copy of the module folder that you want to run twice. (Ex - MMM-Module)

2. Rename the folder of the copy to MMM-Module2.

3. Open the MMM-Module2 folder that you just renamed.

4. Rename the MMM-Module.js file to MMM-Module2.js

5. Open the MMM-Module2.js file.

6. Change the Module.register line to Module.register("MMM-Module2", {.

7. Change the getStyles: function to

getStyles: function() {
        return ["MMM-Module2.css"]
    },

8. Save the MMM-Module2.js file you just edited and close.

9. Open the MMM-Module2 folder.

10. Rename the MMM-Module.css file to MMM-Module2.css.

11. Open the MMM-Module2.css file.

12. Rename the module names to reflect the new module name. Your class names will be different. Just change the module names:

.MMM-Module2 .header {
  color: #50F8F4;
  text-align: center;
  /*  display: none;
}
 
.MMM-Module2 .age {
  color: #white;
  text-align: center;
  /*  display: none;
}

.MMM-Module2 .females {
  color: #ff69b4;
  text-align: center;
/*  display: none;
}

13. Save the MMM-Module2.css file and close.

14. Now make another entry into the config.js file using MMM-Module2 as the module name and change your values.

Remember

This doesn’t always work but many users have had success this way, including myself.

About API calls

If the module you are duplicating uses an API key, you are effectively doubling the calls to that API. This might lead to hitting your call limit. In this case, you should consider raising the updateInterval for both modules to avoid being throttled by the API.

Peace!

@sdetweil

I thought I said that. :-)

@bkeyport

@bkeyport said in Cached pictures in iFrame:

Is there any way to turn off the caching, or do whatever I need to do to get a fresh image every time?

Sounds like a similar issue I had a while back. Perhaps this is the same issue. The DOM has to change in order for it to refresh. Sean and Strawberry taught me this. The solution is simple.

Set up a time stamp var and add it to the end of your img source.

var getTimeStamp = new Date().getTime();
img.src = "http://api.usno.navy.mil/imagery/earth.png?view=rise&seed=" + getTimeStamp; 

If yours is the same issue then this will work.

Hope it helps.

Peace!

@sdetweil

Sorry about reviving an old thread but I thought you and others might want to know

Bro, I went ahead and installed npm install electron@latest (11.3.0) as an experiment. Both my MMM-ISS-Live and EARTH-Live modules were affected by electron. It appears the latest version of electron has fixed the problem, at least with these two modules

@cowboysdude

Uhhhh . . .

@brendan_c23

I’m done for the night, mate. I would suggest you double check your appid at openweather. copy and paste it into your config entry for weatherforecast and make sure it is in quotes.

Perhaps someone else will continue to help you tonight.

Good luck

@brendan_c23

MagicMirror should have launched when you issued the pm2 start MagicMirror command

@brendan_c23

Were there any errors when MM launched?

@brendan_c23

ok,. so try pm2 stop MagicMirror

then pm2 start MagicMirror

@brendan_c23

output should look like this

pi@Pi3:~ $ pm2 status
┌──────┬──────┬────────┬───┬─────┬──────────┐
│ Name │ mode │ status │ ↺ │ cpu │ memory   │
├──────┼──────┼────────┼───┼─────┼──────────┤
│ mm   │ fork │ online │ 0 │ 0%  │ 1.3 MB   │
└──────┴──────┴────────┴───┴─────┴──────────┘
 Use `pm2 show <id|name>` to get more details about an app
pi@Pi3:~ $