@Jopyth said in Activate Profiles (via MMM-ProfileSwitcher) using MMM-Remote-Control...:

%22Snille%22

Oh! Works! :) I can’t believe that I did not try that… Thank you! :)

@mortenbirkelund {“status”:“Unexpected token P in JSON at position 1”}

Tried that… :)

Hi all,
I’m trying to switch profiles with the MMM-Remote-Control module via notifications to the MMM-ProfileSwitcher module.
But I can’t get it to work. I do get the MMM-ProfileSwitcher to “switch” but only to a profile called [object Object].
My profile in this case is called “Snille”.
The Profile Switcher work otherwise with the MMM-Touch-Navigation module, so it’s not broken otherwise. :)

Iv’e tried with the following URL (and variants of that):
http://MagicMirorIP:8080/remote?action=NOTIFICATION&notification=CURRENT_PROFILE&payload={“Profile”:“Snille”}
As long as the “json” is ok at the end I get the “Switched to profile [object Object]” on the mirror. But, of course I don’t have any “[object Object]” profile. :)
I do get a: {“status”:“success”} from the MMM-Remote-Control as well (as long as the “json” string is ok as well).
Anybody have any idea? :)

@cowboysdude Actually it was quite fast only 8 days! :)

@cowboysdude Hehe, I’m still waiting for my mirror. Have not yet tested with any glass, just have it leaned against the monitor right now. :) I hope my work can supply a Pilkington MirrorView mirror, if not that’s what I’m going to buy.

@cowboysdude I bought this one: https://www.aliexpress.com/item/32-points-32-Inch-IR-Multi-touch-overlay-kit-without-glass-for-Interactive-Table-Multi-Touch/1195149819.html
And I can actually “zoom” the on the mirror (in the electron browser) which means that multitouch works (at least for two points). :)

@cowboysdude It worked when added to a sh script! Good call! :) Before I just tested with the xinput command directly in the autostart file, but that did not work. So now instead I just created a script called xin.sh.
nano ~/xin.sh
Then added
DISPLAY=:0.0 xinput --set-prop "Multi touch Multi touch overlay device" "Coordinate Transformation Matrix" 0 1 0 -1 0 1 0 0 1
There should actually be 3 spaces between “Multi touch” and “Multi touch overlay device”. For some reason the board removes the extra spaces here.

You can actually find the “name” of the device with this command DISPLAY=:0.0 xinput list
Shows something like this:

⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ Multi touch Multi touch overlay device id=6 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]

Depending on what you have connected to your RPi. :)

So, after creating the xin.sh I added that to the autostart file for LXDE:
Like this:
nano ~/.config/lxsession/LXDE/autostart
Added at the end of the file.
@/home/pi/xin.sh
Restarted and it works. :)

@AlessandroRa Just install xinput sudo apt-get install xinput
Then you are good to go. :)
@cowboysdude I have to know when to start the actual xinput command, I have tried in the “startup” for LXDE, with CRON and in “openbox”:es “statup”. For some reason I cant get it to “take”. I have not made a .sh file, true. But where / when to execute it? :)

@AlessandroRa Hi! Unfortunately the manufacturer do not have any drivers for ARM.
I ended up with using it as a normal “HID” device. I have to rotate the frame manually with this command in SSH: DISPLAY=:0.0 xinput --set-prop "Multi touch Multi touch overlay device" "Coordinate Transformation Matrix" 0 1 0 -1 0 1 0 0 1
But I cant get it to stick after reboot. So, I have to do it after every boot when everything has started.
I did not get the xinnput_calibration values to stick either. I’m in Rasbian Jessie Lite.

Hi all, do the font “Awesome” get updated regularly in the mirror ecosystem some how? Or (if possible) do “we” have to do PR for that? :)