MMM-ProfileSwitcher, A Profile/User/Layout Switching Module

tosti007

@Snille about the facial recognition: @paviro would do some testing first and make sure everything works fine and then it’s still up to him to merge the pull request. About the conflict: yes I am aware that he changed his codebut forgot to update my pull request and I will update the line numbers aswell, thank you! I will let you know when I changed it.

About the German xD that’s really odd, do you have your global language settings on German? If you don’t it shouldn’t be German.
~~To disable the title set the title value of the module’s config to false. Like so:~~ alright :D

		{
			module: "MMM-ProfileSwitcher",
			header: "Profile",
			config: {
                                title: false,
				enterMessages: {
					"Snille Louise Martin": "Hej %profile%!",
					"Snille": ["Hoppas dagen varit bra!", "Ser man på, välkommen!"], 
					"Louise": ["Kul i skolan idag?", "Kul att ses!"], 
					"Martin": ["Kul att ses!", "Allt bra?"] 
				},
				leaveMessages: {
					"everyone": "Ses snart %person%!", 
					"Snille": ["Hej då, jag kommer sakna dig...", true] 
				}
			}
		},

And I am really happy to hear that you are enjoying the module :)

Snille

@tosti007 Hehe, I just edited my post when you replied. Found the title thing… Sorry for not reading… :)
I have my language like so:

	ipWhitelist: [
		"127.0.0.1",
		"::ffff:127.0.0.1",
		"::1",
		"::ffff:10.0.0.1/120" 
	],
	language: "sv",
	modules: [

Seems to work with the clock at least (get the swedish names of the days. :)…
I just saw a “leave message” in german… I have to try to grab a screenshot…

tosti007

@Snille ah yea I don’t have Swedish translations (I only speak English, German and Dutch and that’s more than enough imo xD) and apparently it chooses German then instead.
Try setting includeEveryoneMessages to false in the config. It shouldn’t show up then but if it doesn’t let me know.

Snille

@tosti007 Here you go:
sv.json

{
  "leave": "Ses snart %profile%!",
  "enter": "Hej %profile%, trevligt att ses igen!",
  "title": "Användarprofil"
}

:)

tosti007

@Snille Thank you very much :) was about to ask :D

tosti007

@tosti007 said in MMM-ProfileSwitcher, A Profile/User/Layout Switching Module:

I will update the line numbers aswell, thank you! I will let you know when I changed it.

@Snille Updated :) You have to remove only a few lines more and then it should work like before! Also added your translations :) thank you once more

tosti007

@All Hello everybody! Version 2 is out now :D You can set a timer to switch from one profile to another after a certain amount of time! For an explanation on how to configure them check the README. After a feature request of @shashank.

Mar

So i’ve added the MMM-ProfileSwitcher to the config file along with “classes: ‘default xyz’” etc to each module under the config file. With one module having only a class of “PAGE2”.

Using MMM-Buttons i have it successfully pushing a notification saying PAGE2 but nothing is happening on my MM, also all the modules are showing up? When the notification is pushed in the pm2 logs i see all the modules receiving the notification but i dont ever see profileswitcher in that list.

I honestly dont know what im doing wrong, the profileswitcher is loading according to the pm2 logs (with an error) but for instance one of my modules I have a unique class set so it should only be visible for that profile but it still shows up when the mirror loads on the default page.

edit:
Noticed this error on pm2 logs x

0|mm       | ** Message: console message: http://localhost:8080/modules/MMM-ProfileSwitcher//MMM-ProfileSwitcher.js @87: SyntaxError: Unexpected token '>'

Line reads:

self.config.ignoreModules.some((m) => classes.includes(m)) || // Should this module be ignored?

Also same at line 204/108 wondering if it should be an =, >=, or perhaps a < =? It also doesnt seem to like line 205 return statement (but im not sure what this one means).

shashank

@tosti007 Hi, Thanks a Lot, Profile switch timer is working fine, tested the same.

tosti007

@Mar After a helpfull pull request by @Jopyth this line got removed. Try pulling the new changes and let me know if still gives problems! Thank you for letting me know that bug.

@All The module uses lockstrings now! This due to some problems in combination with other modules. Give the README configurables a look if you want to disable this.

Edit: Ugh I just noticed I made a terrible mistake in that line. the => should have been >==. Thanks again!
Edit 2: Double ugh, read it again and it was right.