xinput finds the wrong touchscreen device

Question

I have an Ubuntu 18.04.1 which I want to control via touch screens. There are two monitors connected, both with touchscreen capabilities

~$ lsusb
Bus 002 Device 004: ID 0eef:0001 D-WAV Scientific Co., Ltd eGalax TouchScreen
Bus 001 Device 004: ID 0eef:0001 D-WAV Scientific Co., Ltd eGalax TouchScreen

Unfortunately they each register two devices, as seen in

~$ sudo evtest
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0:  Power Button
/dev/input/event1:  Power Button
/dev/input/event2:  Thustmaster Joystick - HOTAS Warthog
/dev/input/event3:  eGalax Inc. USB TouchController
/dev/input/event4:  eGalax Inc. USB TouchController Touchscreen
/dev/input/event5:  eGalax Inc. USB TouchController
/dev/input/event6:  eGalax Inc. USB TouchController Touchscreen
/dev/input/event7:  Logitech USB Keyboard
/dev/input/event8:  Logitech USB Keyboard Consumer Control
/dev/input/event9:  Logitech USB Keyboard System Control
/dev/input/event10: Logitech USB-PS/2 Optical Mouse

Using device 4 or 6, I can see touch inputs beeing registered:

Select the device event number [0-16]: 4
Input driver version is 1.0.1
Input device ID: bus 0x3 vendor 0xeef product 0x1 version 0x210
Input device name: "eGalax Inc. USB TouchController Touchscreen"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 320 (BTN_TOOL_PEN)
    Event code 330 (BTN_TOUCH)
  Event type 3 (EV_ABS)
    Event code 0 (ABS_X)
      Value   1918
      Min       30
      Max     4040
    Event code 1 (ABS_Y)
      Value   2801
      Min       60
      Max     4035
  Event type 4 (EV_MSC)
    Event code 4 (MSC_SCAN)
Properties:
Testing ... (interrupt to exit)
Event: time 1556810214.532981, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042
Event: time 1556810214.532981, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1556810214.532981, type 3 (EV_ABS), code 0 (ABS_X), value 3122
Event: time 1556810214.532981, type 3 (EV_ABS), code 1 (ABS_Y), value 2328
Event: time 1556810214.532981, -------------- SYN_REPORT ------------
Event: time 1556810214.538936, type 3 (EV_ABS), code 0 (ABS_X), value 3117
Event: time 1556810214.538936, type 3 (EV_ABS), code 1 (ABS_Y), value 2325
Event: time 1556810214.538936, -------------- SYN_REPORT ------------
Event: time 1556810214.544902, type 3 (EV_ABS), code 0 (ABS_X), value 3118
Event: time 1556810214.544902, type 3 (EV_ABS), code 1 (ABS_Y), value 2326
Event: time 1556810214.544902, -------------- SYN_REPORT ------------
Event: time 1556810214.550879, type 3 (EV_ABS), code 0 (ABS_X), value 3116
Event: time 1556810214.550879, type 3 (EV_ABS), code 1 (ABS_Y), value 2329
...

Device 3 and 5 give me nothing. Unfortunately 3 and 5 are recognoized by xinput which is probably why I cannot move the mouse currently.

~$ xinput
⎡ Virtual core pointer                      id=2    [master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer                id=4    [slave  pointer  (2)]
⎜   ↳ Logitech USB-PS/2 Optical Mouse           id=11   [slave  pointer  (2)]
⎜   ↳ eGalax Inc. USB TouchController           id=12   [slave  pointer  (2)]
⎜   ↳ eGalax Inc. USB TouchController           id=13   [slave  pointer  (2)]
⎣ Virtual core keyboard                     id=3    [master keyboard (2)]
    ↳ Virtual core XTEST keyboard               id=5    [slave  keyboard (3)]
    ↳ Power Button                              id=6    [slave  keyboard (3)]
    ↳ Power Button                              id=7    [slave  keyboard (3)]
    ↳ Logitech USB Keyboard                     id=8    [slave  keyboard (3)]
    ↳ Logitech USB Keyboard Consumer Control    id=9    [slave  keyboard (3)]
    ↳ Logitech USB Keyboard System Control      id=10   [slave  keyboard (3)]

If I run xinput_calibrator, it is also probing for 'eGalax Inc. USB TouchController' which is obviously wrong.

How can I get xinput to use the correct two devices?

Thank you