MMM-WeatherOrNot

[Jarhead96097]

@Mykle1 Interesting idea… but being the relative noob that I am, would I simply copy and rename the folders and make appropriate config changes, or are there more steps? Do I need to do an npm install --productive in each renamed folder?

Thanks for your help!

[Jarhead96097]

@Mykle1

I found another post that describes using multiple instances of a module. I’ve copied and renamed the second and third instance, and updated the *.js, *.css and config.js files. Everything seems to be updating and working correctly now. I’ll check again in another hour to make sure.

Thanks for the idea!

[Jarhead96097]

@Mykle1

Well, I spoke too quickly. It seems that renaming the three instances helped but didn’t eliminate the problem. The data still grows stale after some period of time.

Any other ideas? Other than copying/pasting/renaming, editing the .js and .css files and doing the npm install, is there anything else I should be doing to ensure the three modules work independently and continue to retrieve weather data?

Thanks,

[Mykle1]

@Jarhead96097

Well, there are no guarantees.

You’re using a separate location and locationCode for each instance? (by following the readme instructions)

You could try staggering the updateInterval on each instance as well (so they’re not updating at the same time)

I’ve never used more than one instance

[Jarhead96097]

@Mykle1 Sure… my mileage may vary… completely understood.

Yes, I’ve configured them with three different sets of location and locationCode information.

I wondered about staggering the updateInterval, so I’ll try that next.

Thanks!

[Mykle1]

@Jarhead96097

I’m testing. I’ll let it run for a while.

[Jarhead96097]

@Mykle1 Thanks for all the help! I love the module… just wish I could figure out why the information goes stale.

[sdetweil]

@Mykle1 does the module rebuild the display or does it locate the dom elements and update those?
document.getElementbyId() … if so, you probably have duplicate IDs w 2 versions running

in my modules I use the module identifier as part of the item id to avoid this

this.identifer in the modulename.js

[Mykle1]

@sdetweil

It’s an iframe that is being updated via the url

[Mykle1]

@Mykle1 is out for a smoke.

[sdetweil]

@Mykle1 iframe. gotcha

[sdetweil]

@Mykle1 hey hey. you didn’t tell me!

[Mykle1]

@sdetweil

The hell I didn’t! My last post was a broadcast notification. :-)

[Mykle1]

@Jarhead96097

I am experiencing the same issue.

[Jarhead96097]

@Mykle1 Well, glad to hear it isn’t related to my individual setup. If there’s anything I can help test, please let me know.

[Jarhead96097]

@Mykle1

Would I need to edit the MMM-WeatherOrNot2.js and MMM-WeatherOrNot3.js code to somehow reference different iframes? Is there a different way to reference multiple iframes running on MM?

[Mykle1]

@Jarhead96097

I tried that. No luck. If you wanted to try for yourself, do:

Make copy of module folder
Rename copy folder to MMM-WeatherOrNot2
Open the MMM-WeatherOrNot2 folder
Rename the css file to MMM-WeatherOrNot2,css
Rename the MMM_WeatherOrNot.js file to MMM-WeatherOrNot2,js
Open the MMM-WeatherOrNot2,js file
Change line 8 to Module.register("MMM-WeatherOrNot2",{
Change line 49 return ["MMM-WeatherOrNot2.css"];
Make new entry in config for MMM-WeatherOrNot2

[Jarhead96097]

@Mykle1 said in MMM-WeatherOrNot:

@Jarhead96097

I tried that. No luck. If you wanted to try for yourself, do:

Make copy of module folder
Rename copy folder to MMM-WeatherOrNot2
Open the MMM-WeatherOrNot2 folder
Rename the css file to MMM-WeatherOrNot2,css
Rename the MMM_WeatherOrNot.js file to MMM-WeatherOrNot2,js
Open the MMM-WeatherOrNot2,js file
Change line 8 to Module.register("MMM-WeatherOrNot2",{
Change line 49 return ["MMM-WeatherOrNot2.css"];
Make new entry in config for MMM-WeatherOrNot2

Yes, unfortunately, I had the same result. Is there a way to create an array and display all of the configured locations?

[Mykle1]

@Jarhead96097

You could always give it a try. :-)