[SOLVED] My RF remote has stopped working after migration to Kodi v17

Help and Support Raspberry Pi
46

Thanks to @eubuleus and @schetz, both of which passed on critical info. After ssh into the box, monitoring the udev output by unplugging and replugging the 2.4 GHz dongle created lots of chatter, but the IDproduct and VendorID were right there. That is a solid way to discover the ID numbers you need.

I have a Lynec T5 remote, ProductID=2404 VendorID=25a7, and this worked like a champ.

For the record, I elected to create the file 51-these-are-not-joysticks-rm.rules (the ‘second’ method referred to in the github reference) manually. Autogenerating it created lots of entries I really didn’t need. After discovering the correct product and vendor ID’s, I navigated to the correct directory

cd /etc/udev/rules.d

and created the file I needed with

touch 51-these-are-not-joysticks-rm.rules

edit the file however you like (I installed vim) and added this text

# /etc/udev/rules.d/51-these-are-not-joysticks-rm.rules
#
# This file is auto-generated. For more information:
# https://github.com/denilsonsa/udev-joystick-blacklist

SUBSYSTEM=="input", ATTRS{idVendor}=="25a7", ATTRS{idProduct}=="2402", ENV{ID_INPUT_JOYSTICK}=="?*", ENV{ID_INPUT_JOYSTICK}=""
SUBSYSTEM=="input", ATTRS{idVendor}=="25a7", ATTRS{idProduct}=="2402", KERNEL=="js[0-9]*", RUN+="/bin/rm %E{DEVNAME}", ENV{ID_INPUT_JOYSTICK}=""

and saved the file. I rebooted from the interface and everything worked.

Thanks to everyone. This was a slick fix.

3 Likes