Wouldn’t it be better to have some kind of speadshwet online somewhere or maybe a database table from the site? :) That would make it easier to edit than copy-paste that table all the time

@yours.mukul did you install node? (apt-get install nodejs) and is it the latest version?

@PatrickGlatz
I just gave it a look and I know what’s wrong. The problem is that the code only looks at those times when switching to a different profile than the default profile. So it’s not a fault on your side but on mine.
Solution: I already solved it on my local pc and will upload the fix later today uploaded. All you will have to do is pull the new changes and the config you showed should work without a problem :)

Sorry for the inconvenience, a mistake on my part. Thank you for letting me know!

Greetings
Brian

@PatrickGlatz the config file looks fine to me and you don’t have to add the profiles anywhere else than in the module itself.

About the ModuleScheduler, I wrote a how to here about how to use it with this module. Sure you have that correctly set up?

I will copy paste your config into mine tomorrow morning and see if I can reproduce it.

@looolz I think what you are looking for is the MMM-ModuleScheduler which you can use in combination with my module as described here

Are you certain you installed it properly by going into the folder and using the npm install command?

Another side note I just realised, if you do use that setTimeout and you swap between profiles in rapid succession I am not sure and cannot quarantee that some of the modules will be shown properly

@mortenbirkelund By altering the code git won’t allow you to pull the new updates, in case of an update you will have to clone it manually again. And thank you for sharing the timeout :)

@mortenbirkelund Yes there is, however that would mean that the code has to loop over the modules twice, which isn’t a great thing to do performance wise. I will write a bit of code that does it for you and post it here soon.

Edit: here is the code, all you need to do it replace the whole set_profile function inside the MMM-ProfileSwitcher.js file.

The code:

// Change the current layout into the new layout given the current profile
set_profile: function (useEveryone) {
    var self = this;

    var options = {};
    if (self.config.useLockStrings) {
        options.lockString = self.identifier;
    }

    MM.getModules().exceptWithClass(self.config.ignoreModules).enumerate(function (module) {
        if (!self.isVisible(self, useEveryone, module.data.classes)) {
            module.hide(self.config.animationDuration, function () {
                Log.log(module.name + " is hidden.");
            }, options);
        }
    });

    MM.getModules().exceptWithClass(self.config.ignoreModules).enumerate(function (module) {
        if (self.isVisible(self, useEveryone, module.data.classes)) {
            module.show(self.config.animationDuration, function () {
                Log.log(module.name + " is shown.");
            }, options);
        }
    });
},

Note: Once again this is not so great performance wise, but I dont think you will notice much of it

@Snille yes that’s a a great way to use the modules :) you’re welcome for my version but thank you for yours :D

Nice to see people making different versions of my code :)
This indeed was one thing that my module can’t do! Now people can choose to use this module if they want buttons for single modules :D

The reason why it’s a bad practice to change the maker’s code is because you cannot do an easy git pull anymore due to the changes. That means that every time there is a new version of the module you will have to redownload it and then modify the code again.

That being said there is no way to get what you want without modifying the code, unless the maker adds this as a feature in the future.

To get what you want you only have to change code inside MMM-NetworkScanner.js.
Inside the getDom function you can find the lines:

// Icon
icon =  document.createElement("i");
icon.classList.add("fa-li", "fa", "fa-" + device.icon);
deviceItem.appendChild(icon);

// Name 
deviceItem.innerHTML += device.name;

All you have to do is change that part into:

// Name 
deviceItem.innerHTML += device.name;

// Icon
icon =  document.createElement("i");
icon.classList.add("fa-li", "fa", "fa-" + device.icon);
deviceItem.appendChild(icon);

So this is basically swapping the order in which the icon and the text are added to deviceItem.

Hope this helps :D

Note: I am currently on mobile so have no way of testing it. If it doesn’t work then let me know and i will search another solution (and I will be confused since I am pretty sure this works)

@kichilron alright :)

Does your console show any errors when you run your code?

Since the callback isn’t called at all it might also be a problem with the request("omitted" part. Try doing something simple (only log something) inside the callback. If it doesn’t show up then I think the problem lays in the request function that might be called wrong.

@dfuerst Yes it does, FacialRecognition also uses classes (which are saved in this.data)

If you look around in the Show your Mirror category you will be able to find multiple people using foil and glass and see it for yourself. One thing to note is that a real glass mirror will also feel different. I am sure if the plastic mirror works and can’t recall if i have seen someone make one.

You can most often buy the mirrors online, just go to any search engine and start searching :) then you can also maybe find a local retailer.

I am really not familiair with requests and such, but I did notice this line:

var a = $(this).next();

Are you sure you want to use this here and not self?

@all Thanks to @roramirez we now have Spanish translations! :D

Alright so I found the problem and it turned out to be a mistake in the Localtransport module. I have send him a pull request and updated my README with a fix. Have fun with the modules :)

I will copy paste it the README text here as well:

---

The MagicMirror-LocalTransport-Module module does not work (without a fix) with the [MMM-ProfileSwitcher].
This due to his code overwriting a variable that it a default variable used by the MagicMirror Framework and my code need this. Luckily this problem can be solved fairly easily with any text editor.

Go to the module’s main file localtransport.js and replace the occurences of this.data with this.info.

Note: There should be three occurences on lines 170, 204 and 209.

You will most often get bleedthrough, but how much really depends on your screen. You could look through the posts in the show your mirror section. Here you will be able to find some pictures where you can see the bleedthrough and decide for yourself if you can live with that :)

@dfuerst I fixed that backwards compatibility, but this does unfortunatly not solve the problem (tested it). I did found the reason why it doesn’t work, however I do not have a quickfix for this. I will look at it in the following days after doing some research.