@mirror.master ah, so you got it to display two different instances of the module? Just Carousel doesn’t let you input those two instances because it requires a name?! Then I recommend using MMM-ProfileSwitcher + MMM-Remote-Control and/or MMM-ModuleScheduler. Instead of having to provide a list of modules which form one “page”, you can assign every module a list of “pages” it should be displayed on. This eliminates the problem of modules being named the same / being duplicates.
Just install ProfileSwitcher and RemoteControl, assign some “classes” (think of it as pages) to modules (e.g. “transport1” and “transport2” to the transport instances) and switch between them using URLs like here. I guess ModuleScheduler isn’t necessary since ProfileSwitcher already comes with timing functionalities. Just mentioned for completeness.

@mirror.master ah i see. I don’t think modules are meant to be used in form of multiple instances of the same module. For example, see the way node_helper is used (even when changing some names/parameters in config). Some modules may work with multiple instances of themselves, some don’t.

The module you are talking about is MMM-LocalTransport, correct? It’s not really clear by the term “localtransport module”. If I see correctly, you should be able to use multiple instances of this module just by adding it two times in the config file. If not, see below.

As far as I understand, you already tried to copy the whole module under different name? In other words, you created a “new” module which does exactly same / has the same code as the one you want to use, but has a different name (folder named “newModule” -> file named “newModule.js” -> within the line Module.register('newModule'))?! This is definitely possible and should work unless the module itself uses some sort of API which restricts multiple accesses.

Alternative way IF the module itself provides the option to set destinations via notifications (Note: MMM-LocalTransport doesn’t seem to offer that): use MMM-RemoteControl and/or MMM-ModuleScheduler to swap destinations by remote command and/or timing.
IF it doesn’t, implement it yourself (and use together with the modules mentioned above). In most cases, it is not difficult: basically the following structure should apply

notificationReceived: function(notification, payload) {
  if (notification==="SET_FROM_TO") {
    /* 1. set variable containing destination to new destination defined by payload;
     *     may be this.config.origin/this.config.destination or something
     * 2. make changes visible; probably by doing this.update() or this.updateDom();
     * So, for example for MMM_LocalTransport something like this should work:
     */
    this.config.origin = payload.origin;
    this.config.destination = payload.destination;
    this.update();
  }
}

@dhirajv12 Never seen this. Googled it. Found this.
If it works now, I wouldn’t worry too much.

@mirror.master You’re welcome! The information provided are rather general. Feel free to ask again, if you need more specific help.

@dhirajv12 Seems more like you are missing some dependency. Try reinstalling from scratch…

@mirror.master Have a look here. I don’t know how you want to trigger the swapping, but in general the possibilities described in the thread are the ways to go.

@Mykle1 Why bother with individual modules? If you do it for every module, isn’t it the same as simply styling header in general?

I don’t know if we agree on the term “header”. For me, the following changes the color of the text of every module-headline to green:

#custom.css
header {
    color: green;
}

(Note: .header does not!)

@beck0r I guess you changed something ;) just restarting doesn’t brake anything.

1. So, what do you see? Standard compliments? Nothing? Error message?
2. Does it work with compliments embedded into config file?
3. Could you post config and remote compliments file?

@beck0r I’ve got at least one “ö” in my compliments and it works; not sure why, though. You can try using an external .json file for your compliments, since thats what I did.

@RE_Magic_Mirror Well…it depends.

• If switching to develop branch fixed your problem, then you want to stay at develop until the changes are merged into the master branch. Until then, you can either update (see https://github.com/MichMich/MagicMirror#updating-your-magicmirror) or decide to ignore updates. If you don’t want to see the notification, you have to disable the update notification module.
• If it did not help with your problem, then you are usually better off using the master branch, so I would suggest to switch back to master.