MMM-WeatherOrNot

[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!