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