Hi Pilster59,

I’m sorry but I’m curious. you say that you want a “simple” solution but you ask to redevelop the whole UI of the underlying OS to manage wireless connections. why don’t you want to do alt-tab and use the wireless GUI ? at least, it is less bug-prone and will likely manage more type of wireless connexion parameters (WPA2, PSK, etc.)

I just rewrote the module, with a new standard UI and the module should now perfectly work as multi-instance (@Ob018 )

Just got my credentials (took two weeks)

 I simply “sandwiched” it between the monitor and the frame. 2 “L” brackets hold everything in place. Here is my explanation of how I built the box and frame:

Same thing here. the only way to be able to unbuilt it if needed (and it was needed several times in my case)

same than mine :) coded exactly like you while I was on the plane I just pushed but not tested (sadly I pushed it on my master :-/)
https://github.com/lgmorand/MMM-Ratp

socketNotificationReceived: function(notification, payload) {
        Log.info("Notif:" + notification);
        if (notification === "TRANSPORTS") {
            if (this.config.debugging) {
                Log.info("Transports received");
                Log.info(payload.lineInfo);
                Log.info(payload.transports);
            }

            if(this.config.uniqueID == payload.uniqueID) // just in case of multi instances
            {
                this.transports = payload.transports;
                this.lineInfo = payload.lineInfo;
                this.loaded = true;
                this.updateDom(this.config.animationSpeed);
            }
}

At least, thanks to you, I know it can work :)

my idea to improve it was to auto-generate a ID for the module, not in the config, but generated by the Magic Mirror on loading. it should be easy to implement. Once this ID generated, it is accessible from the node_helper and the module.js. this way, no need to declare a uniqueID in the config

@BenRoe nope. And I tried several months ago without success. But I’m trying it now (thought I’ll not be able to test before the next week). If it works, it could be easily implemented everywhere and furthermore, I have an idea to simplify it a little bit by improving Magic Mirror itself.

I’ll come back here after my tests

most of modules don’t support multi-instance because the way magicmirror is done, they share node_helper and thus, both instances received all notifications so the last notification will overwrite both modules.

either you duplicate the module (and edit the source code a little bit) or the module itself but be rewrittent to manage multi-instances.

you’ll need an API or something to read the info from. You should provide a technical source for all this information (the HTML page is not ;-)) and maybe someone will do the module for you (but honestly it’s kind a really personal need for you :))

the video is great :) should definitely put it on the readme. People will love your module ;-)

Hi @muharremtac

could you fullfill the description of the readme? the config talk of images, but I don’t see how it works ? I was expecting a gesture commands or something. is it just a caroussel of images automated by gestures ? if so, you should say what we must expect with this module because it is not very clear (at least for me :))