Probleme mit Andoer MX3 Funkfernbedienung

ewl · Aug 21st 2021

Ich bin ziemlich sicher, dass ich die gleiche Fernbedienung wie in Funk Fernbedienung / USB - mit Keyboard und Remote Plugin (oder auch ohne...) beschrieben habe, wenn auch unter anderem Namen: https://www.amazon.de/Andoer%C…ung-Type-2/dp/B00WDSCTR4/

Ich habe versucht, die Instruktionen, die ich dort gefunden habe, zu folgen, verstehend, dass manche Keys nicht funktionieren werden, aber hoffentlich mehr als mit dem Standard-Setup.

Code

$ cat /etc/udev/rules.d/95-wireless_remote.rules
# Telink Wireless Receiver
ACTION=="add|remove", SUBSYSTEM=="input", \
ENV{ID_VENDOR_ID}=="248a", ENV{ID_MODEL_ID}=="8367", \
ENV{eventlircd_enable}="true", \
ENV{eventlircd_evmap}="03_$env{ID_VENDOR_ID}_$env{ID_MODEL_ID}.evmap", \
ENV{ID_INPUT.tags}="eventlircd"
$ touch /etc/eventlircd.d/03_248a_8367.evmap
$ reboot

Danach schlägt das Starten von eventlircd fehl, von der Kommandozeile reproduzierbar:

Code

$ sudo /usr/sbin/eventlircd -f --socket=/var/run/lirc/lircd -vvv
eventlircd[2353]: eventlircd_socket_path: /var/run/lirc/lircd
eventlircd[2353]: input device /dev/input/event3: events of unsupported event type EV_MSC will be discarded
eventlircd[2353]: input device /dev/input/event3: event code 0x04 of unsupported event type EV_MSC will be discarded
eventlircd[2353]: input device /dev/input/event3: grabbed
eventlircd[2353]: input device /dev/input/event3: created output event device
eventlircd[2353]: input device /dev/input/mouse0: device grab failed: Inappropriate ioctl for device
eventlircd[2353]: input device /dev/input/event3: output event device destroyed
eventlircd[2353]: intput device /dev/input/event3: released

Code

$ udevadm info --query=all --name=/dev/input/event3
P: /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/0003:248A:8367.0001/input/input6/event3
N: input/event3
L: 0
S: input/by-id/usb-Telink_Wireless_Receiver-event-mouse
S: input/by-path/pci-0000:00:1a.0-usb-0:1.2:1.0-event-mouse
E: DEVPATH=/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/0003:248A:8367.0001/input/input6/event3
E: DEVNAME=/dev/input/event3
E: MAJOR=13
E: MINOR=67
E: SUBSYSTEM=input
E: USEC_INITIALIZED=4187371
E: ID_INPUT=1
E: ID_INPUT_MOUSE=1
E: ID_VENDOR=Telink
E: ID_VENDOR_ENC=Telink
E: ID_VENDOR_ID=248a
E: ID_MODEL=Wireless_Receiver
E: ID_MODEL_ENC=Wireless\x20Receiver
E: ID_MODEL_ID=8367
E: ID_REVISION=0100
E: ID_SERIAL=Telink_Wireless_Receiver
E: ID_TYPE=hid
E: ID_BUS=usb
E: ID_USB_INTERFACES=:030102:030101:
E: ID_USB_INTERFACE_NUM=00
E: ID_USB_DRIVER=usbhid
E: ID_PATH=pci-0000:00:1a.0-usb-0:1.2:1.0
E: ID_PATH_TAG=pci-0000_00_1a_0-usb-0_1_2_1_0
E: LIBINPUT_DEVICE_GROUP=3/248a/8367:usb-0000:00:1a.0-1
E: eventlircd_enable=true
E: eventlircd_evmap=03_248a_8367.evmap
E: ID_INPUT.tags=eventlircd
E: DEVLINKS=/dev/input/by-id/usb-Telink_Wireless_Receiver-event-mouse /dev/input/by-path/pci-0000:00:1a.0-usb-0:1.2:1.0-event-mouse
$ udevadm info --query=all --name=/dev/input/mouse0
P: /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/0003:248A:8367.0001/input/input6/mouse0
N: input/mouse0
L: 0
S: input/by-path/pci-0000:00:1a.0-usb-0:1.2:1.0-mouse
S: input/by-id/usb-Telink_Wireless_Receiver-mouse
E: DEVPATH=/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/0003:248A:8367.0001/input/input6/mouse0
E: DEVNAME=/dev/input/mouse0
E: MAJOR=13
E: MINOR=32
E: SUBSYSTEM=input
E: USEC_INITIALIZED=4135708
E: ID_INPUT=1
E: ID_INPUT_MOUSE=1
E: ID_VENDOR=Telink
E: ID_VENDOR_ENC=Telink
E: ID_VENDOR_ID=248a
E: ID_MODEL=Wireless_Receiver
E: ID_MODEL_ENC=Wireless\x20Receiver
E: ID_MODEL_ID=8367
E: ID_REVISION=0100
E: ID_SERIAL=Telink_Wireless_Receiver
E: ID_TYPE=hid
E: ID_BUS=usb
E: ID_USB_INTERFACES=:030102:030101:
E: ID_USB_INTERFACE_NUM=00
E: ID_USB_DRIVER=usbhid
E: ID_PATH=pci-0000:00:1a.0-usb-0:1.2:1.0
E: ID_PATH_TAG=pci-0000_00_1a_0-usb-0_1_2_1_0
E: eventlircd_enable=true
E: eventlircd_evmap=03_248a_8367.evmap
E: ID_INPUT.tags=eventlircd
E: DEVLINKS=/dev/input/by-path/pci-0000:00:1a.0-usb-0:1.2:1.0-mouse /dev/input/by-id/usb-Telink_Wireless_Receiver-mouse

Display More

Ich vermute, dass ich die mouse0 aus der udev-Regel ausschliessen müsste, aber ich weiss nicht wie, und ob es wirklich das Problem ist.

ewl · Aug 21st 2021

OK, I added `KERNEL=="event*"` to the conditions of the udev rules and now eventlircd runs, but it actually works worse than before, even though the relevant devices seem to be grabbed correctly:

Code

# /usr/sbin/eventlircd -f --socket=/var/run/lirc/lircd -vvv
eventlircd[1985]: eventlircd_socket_path: /var/run/lirc/lircd
eventlircd[1985]: input device /dev/input/event3: events of unsupported event type EV_MSC will be discarded
eventlircd[1985]: input device /dev/input/event3: event code 0x04 of unsupported event type EV_MSC will be discarded
eventlircd[1985]: input device /dev/input/event3: grabbed
eventlircd[1985]: input device /dev/input/event3: created output event device
eventlircd[1985]: input device /dev/input/event4: events of unsupported event type EV_MSC will be discarded
eventlircd[1985]: input device /dev/input/event4: event code 0x04 of unsupported event type EV_MSC will be discarded
eventlircd[1985]: input device /dev/input/event4: grabbed
eventlircd[1985]: input device /dev/input/event4: created output event device
eventlircd[1985]: input device /dev/input/event5: events of unsupported event type EV_MSC will be discarded
eventlircd[1985]: input device /dev/input/event5: event code 0x04 of unsupported event type EV_MSC will be discarded
eventlircd[1985]: input device /dev/input/event5: grabbed
eventlircd[1985]: input device /dev/input/event6: events of unsupported event type EV_MSC will be discarded
eventlircd[1985]: input device /dev/input/event6: event code 0x04 of unsupported event type EV_MSC will be discarded
eventlircd[1985]: input device /dev/input/event6: unsupported event code 0x03 of event type EV_LED will be discarded
eventlircd[1985]: input device /dev/input/event6: unsupported event code 0x04 of event type EV_LED will be discarded
eventlircd[1985]: input device /dev/input/event6: events of unsupported event type EV_REP will be discarded
eventlircd[1985]: input device /dev/input/event6: grabbed
eventlircd[1985]: input device /dev/input/event7: events of unsupported event type EV_REP will be discarded
eventlircd[1985]: input device /dev/input/event7: grabbed
eventlircd[1985]: input device /dev/input/event7: created output event device
eventlircd[1985]: input device /dev/input/event8: events of unsupported event type EV_MSC will be discarded
eventlircd[1985]: input device /dev/input/event8: event code 0x04 of unsupported event type EV_MSC will be discarded
eventlircd[1985]: input device /dev/input/event8: events of unsupported event type EV_REP will be discarded
eventlircd[1985]: input device /dev/input/event8: grabbed
eventlircd[1985]: input device /dev/input/event8: created output event device

Display More

e.g. the keys for program changes which used to work, don't work anymore, and the air mouse doesn't work either.

ewl · Aug 21st 2021

Sorry, my fault, I didn't expect so many keys to require a mapping to work:

Code

# cat /etc/eventlircd.d/03_248a_8367.evmap
KEY_SLEEP = KEY_POWER2
KEY_PREVIOUSSONG = KEY_BACK
KEY_NEXTSONG = KEY_NEXT
KEY_SEARCH = KEY_INFO
KEY_ZOOMOUT = KEY_MODE
KEY_ZOOMIN = KEY_SUBTITLE
KEY_COMPOSE = KEY_MENU
KEY_HOMEPAGE = KEY_PVR
KEY_BACK = KEY_ESC
KEY_ENTER = KEY_OK
KEY_PAGEUP = KEY_CHANNELUP
KEY_PAGEDOWN = KEY_CHANNELDOWN
KEY_CONFIG = KEY_RED
KEY_MAIL = KEY_GREEN
KEY_F2 = KEY_YELLOW
KEY_WWW = KEY_BLUE
# doesn't work due to KEY_F21 being sent in parallel
KEY_HELP = KEY_RED
KEY_PROPS = KEY_GREEN
KEY_FRONT = KEY_YELLOW
KEY_STOP = KEY_BLUE

Display More

I'm still wondering what to do with the KEY_PLAYPAUSE, it's either in the YaVDR play or pause, but not the combination. Would it be possible to add it?

ewl · Aug 24th 2021

Um meine eigene Frage zu beantworten: KEY_PLAYPAUSE tut richtig in VDR und KODI, auch wenn der Code nicht in der Tabelle gelistet ist.

seahawk1986 · Aug 24th 2021

ewl wrote:

auch wenn der Code nicht in der Tabelle gelistet ist

Ich habe die Taste mal in der Dokumentation ergänzt (https://www.yavdr.org/document…ocumentation.html#remotes). Das Playbook nutzt die für VDR (https://github.com/yavdr/yavdr…vdr/files/remote.conf#L25) und KODI (https://github.com/yavdr/yavdr…/userdata/Lircmap.xml#L29).

ewl · Sep 9th 2021

Danke. Ich habe noch ein Problem festgestellt: auf der anderen Seite der Fernbedienung ist eine Tastatur, die Tasten reagieren auch normal auf evtest, mit KEY_A, KEY_B, bzw. KEY_ESC oder KEY_UP, usw... `/dev/input/event6` wird auch von eventlircd "ge-grabbed", und manche wenige Tasten wie KEY_ESC und KEY_UP funktionieren, aber die normalen Buchstaben tun nicht, z.B. um den Namen einer Aufnahme anzugeben. Es tut weder in VDR noch in KODI, oder auch nicht in z.B. Firefox.

Ich kann mich nicht erinnern, dass ich jemals die Buchstaben mappen musste, aber kann es sein, dass eventlircd dazwischenfunkt, und daher die Buchstaben für VDR/KODI/Xorg "geschluckt" werden? Ich könnte vielleicht event6 von eventlircd ausschließen aber manche Tasten auf der Fernbedienungsseite hängen auch dran, daher bin ich unschlüssig, was meine beste Wahl sein soll.

ewl · Sep 9th 2021

Removing event6 with "event[345]" from the udev rule doesn't make it work better, the keyboard still doesn't work. I'm now even more unsure what my options are....

seahawk1986 · Sep 9th 2021

Wenn sich eventlircd ein Input-Gerät greift, dann leitet es alle KEY-Events auf seinem Lirc-Sockel weiter, nur Mouse-Events werden durchgelassen.

Kannst du mal mit evtest schauen, welche Tastencodes von welchem Gerät gesendet werden können (normalerweise bekommt man eine Liste, wenn man es auf ein Gerät loslässt)?

ewl · Sep 11th 2021

Here it is, attached because else too long... I didn't stop eventlircd hence the "grabbed by another process" warnings.

It is to be noted that the device declares more keys than actually exist physically, but the letters do all exist

seahawk1986 · Sep 11th 2021

Ok, so the current /dev/input/event5 implements the keyboard part and some of the keys are used to control the vdr and the others could act as keyboard input for letters (if the output plugin would support it - currently the code that should handle those inputs is commented out: https://github.com/ua0lnj/vdr-…vid/softhddevice.cpp#L330, because it does not work as intended: yaVDR ansible & Tastaur/Keyboard).

eventlircd isn't able to grab only a subset of keys, so you need to work around this limitation by

not using eventlircd and adapt the remote.conf so it uses the key events from the X-Server
write a program that creates two uinput devices that distributes the key events (although this might not be practical if you want to use Keys in other programs that don't read key presses from eventlircd's socket)

ewl · Sep 25th 2021

OK, thanks for the insight but that sounds way above my head (a few Ansible playbooks is nothing compared to this), or the price too high. Perhaps I'll try with the first option though.

Share