@BenRoe the classes config item is the exact same name used by the MMM-ProfileSwitcher plugin unfortunately.
Read the statement by Michael Teeuw here.
Posts made by Mar
-
RE: MMM-SystemStats (cpu temp/load, fre ram ...)
-
RE: [MMM-Buttons] Connect multiple buttons to send configurable notifications
@Jopyth Moved my post here out from another thread.
I am having one more issue though. Using a python test program i can see every single instance of my button press is registered instantly. But in the mirror it seems MMM-Buttons doesnt register pushes unless sometimes I double or triple click…then sometimes the button registers 5-6 times. I’m not really sure how to debug this sort of thing.
Also would it be right to assume the pull up/down resistors were not enabled with MMM-Buttons?
-
RE: MMM-ProfileSwitcher, A Profile/User/Layout Switching Module
@strawberry-3.141 Thanks, I couldnt figure that one out.
return classes.indexOf(self.current_profile) !== -1;
Along with the changes in the previous post I’ve have fully loaded ProfileSwitcher Midori without any errors. It also is showing the correct modules on load (classes = default).
Thanks for the help through this @strawberry-3-141
Managed to figure this all out so thanks to everyone!
-
RE: MMM-ProfileSwitcher, A Profile/User/Layout Switching Module
So ive broken out those functions to the following and now get no errors:
*OLD* value = value.map((x) => { return x === true ? translated : x; }); *NEW* value = value.map( function(x){ return x === true ? translated :x; } ); *OLD* classes.split(" ").forEach((key) => { if (result[key] === undefined) { result[key] = []; } result[key] = result[key].concat(value); }); *NEW* classes.split(" ").forEach( function(key) { if (result[key] === undefined) { result[key] = []; } result[key] = result[key].concat(value); } );
Now the only error i am getting is on line 89
TypeError: undefined is not a function (evaluating 'classes.includes(self.current_profile)')
But im not sure how to fix this one. And this is the function that decides what to show which could be where Midori cannot parse it properly.
-
RE: MMM-ProfileSwitcher, A Profile/User/Layout Switching Module
@strawberry-3.141 Yeah seems to be a midori thing, unfortunately I’m using a pi zero so need to use midori as it runs pretty amazing with the pi. Electron really slows it down.
Wondering if there is a way around this at all? Maybe breaking out the arrow functions to normal one might work?
-
RE: MMM-ProfileSwitcher, A Profile/User/Layout Switching Module
@strawberry-3.141 Thanks, I never seem to have had any issues with these before but only on my pi zero. Loading up the latest profile switcher (using my simple 2 module) i get this error relating to that line
0|mm | ** Message: console message: http://localhost:8080/modules/MMM-ProfileSwitcher//MMM-ProfileSwitcher.js @214: SyntaxError: Unexpected token '>'
But it seems to work via a remote browser (i.e chrome but switching doesnt work) and not the pi’s midori which still shows both modules.
-
RE: MMM-ProfileSwitcher, A Profile/User/Layout Switching Module
@tosti007 Thanks for the updates, still looks like lines 214 & 218 contain the “=>” were these supposed to be switched to >== also?
So just getting those error so far, but still no luck on the switcher. Im really not sure what I’m doing wrong. I’ve simplified my config file to the following to try make it load the default profile and just switch to ‘PAGE2’. But when the MM loads I get both the clock and weather still on the screen.
modules: [ { module: 'alert', }, { module: "updatenotification", position: "top_bar" }, { module: 'MMM-ProfileSwitcher', config: { // See 'Configuration options' for more information. } }, { module: 'MMM-Buttons', config: { buttons: [ { pin: 5, name: "power", shortPress: { notification: "PROFILE_SWITCH", payload: {action: "PAGE2"} } } ] } }, { module: 'clock', classes: 'default', position: 'top_left', }, { module: 'currentweather', classes: 'PAGE2', position: 'top_right', config: { location: '...', locationID: '...', appid: '...' } }, ]
and when i press the button pm2 logs only shows this but nothing happens on the screen.
0|mm | ** Message: console message: [native code] @0: clock received a module notification: PROFILE_SWITCH from sender: MMM-Buttons
edit: On the main HDMI cable monitor the mirror is showing both modules, but if i go via chrome on my laptop it only shows the clock (but still doesnt switch when pressing the button). The inspector in Chrome shows that its hiding non-default modules…seems like Midori doesnt get to this (but I have no way to check)
-
RE: MMM-ProfileSwitcher, A Profile/User/Layout Switching Module
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 x0|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).
-
RE: [MMM-Buttons] Not recognizing button presses
@istepgueu @Jopyth Whoo hoo got it.
MMM-Buttons.js: Semi colons on line 71/72 and line 86 needs to be changed to:
sendAction: function(description) {
where as it currently just reads:
sendAction(description) {