MagicMirror Forum

    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unsolved
    • Solved
    • MagicMirror² Repository
    • Documentation
    • Donate
    • Discord
    1. Home
    2. emailuser
    3. Topics
    E
    • Profile
    • Following 0
    • Followers 0
    • Topics 2
    • Posts 3
    • Best 0
    • Controversial 0
    • Groups 0

    Topics created by emailuser

    • E

      IR Overlay - pulling hair out !
      Troubleshooting • • emailuser

      5
      0
      Votes
      5
      Posts
      376
      Views

      Snille

      Hi, I had the same issue when I built my mirror… Here is how I solved it. Made a .sh script with all the information: 🙂

      #!/bin/bash # 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 form a console: 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-pi/autostart # Added at the end of the file. # @/home/pi/xin.sh # Restarted and it works. # DISPLAY=:0.0 xinput --set-prop "Multi touch Multi touch overlay device" "Coordinate Transformation Matrix" 0 1 0 -1 0 1 0 0 1

      Maybe you guys can use it some how? 🙂

    • E

      MMM-homeassistant-sensors- attributes ?
      Troubleshooting • • emailuser

      2
      0
      Votes
      2
      Posts
      251
      Views

      E

      @emailuser It looks like the very last line of your code has { instead of }

      See if that resolves it?

    • 1 / 1