@johnnyboy said in Fresh Install:

Hopefully, following @sdetweil’s instructions, I will get my MM back to life, and regain my interest?

I can’t speak to your interest but you will get up and running following his directions.

@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

Why?

Because I just used his install script for the um-teenth time. I’ve used it on Pi’s, laptops of all kinds, my dev machine, etc… and every time it has worked without a hitch.

So?

So thank you, Sam. :thumbsup:

@sdetweil

I thought I said that. :-)

Three years after the initial post. Here they are:

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!

@luke2102 said in friend of mine has tried to get half the modules working with out success:

my friend has tried to get this to work for keeps with out success their needs to be a easy way for people who do not understand how to edit files etc

There are more than a few people here willing to help you and your friend. You, and/or your friend simply need to ask for help but first you must make some attempt at doing it yourself. After that, you and your friend can create a topic, stating what you’ve already done and ask for help. User @sdetweil has written several installers and maintains them. Run one installer - Boom! MagicMirror is installed and works, making it incredibly easier than it used to be.

According to the MagicMirror creator, this is supposed to be a leaning experience. You are expected to read through the topics and learn how to do things. Make good use of the forum search feature. You can find many of your answers that way. If you get stuck, this is the place to ask for help, as mentioned above.

@brendan_c23 said in Problems With Weather:

So I emailed Openweathermap for help and he said I should use the “One Call Api” https://openweathermap.org/api/one-call-api but I am having trouble figuring out how to incorporate the API call code into the weather forecast module?

Uhhh, I’m pretty sure the default weatherforecast module DOES use the One Call API.

I would try getting another api key using a different email. However, I suspect there might be something else going on there. Would you object to sending me your current openweather api key so I can test it here? If you agree, send it in a private chat message. I’ve sent you a chat. You can send your api key there if you agree.

@Miafrance

I am glad you find it interesting. I look forward to seeing the hummingbirds in my yard every summer. :-)

@brendan_c23

weatherforecast: Your AppID does not support long term forecasts. Switching to fallback endpoint.

Totally not your fault, just so you know.

And I guess mine does not either, However, the module does load after a short delay but it only displays tomorrow’s weather. Same as when using my api key.

This is very odd as I tested your api key in another weather module that uses open weather and it is giving all the data and NO errors. SO, I’m guessing the weatheforecast module itself has some issues.

Are you dead set on using weatherforecast? There are many weather modules that provide you with forecasts and current weather. I’m fairly sure that some of them were built upon the openweather api and your current api key should work fine with them. Personally, I don’t use the default weather modules. I’ll be happy to give you a hand with them if you are willing to try them.

Edit:

I’ve just been informed that in the new MM release (April 1) both of those modules are being replaced by a newer version that does both current and forecast. Sheeesh