Start by pressing a few buttons you should see some output on the screen. Lets see if we can get some input from the remote to our server and then see that on the screen. If you saw a message about not finding your device with the test use the ‘device’ where the comes from the the output from ir-keytable without any arguments. Ls -l /dev/lir* # for virtual machines / Raspberry Pi Ls -l /dev/input/by-path/*-ir # for real hardware
It is possible to find it with one of the following. If there was no output you will need to specify the device name. When your device is not automatically found You can also see that the output for my remote shows On real hardware it will come out like this /dev/input/event7 Strange as I definitely do not have lircd installed not even a little bit. My device was listed as lirc device as /dev/lirc0. You may need to know the device name assigned to the receiver for some of the ir-keytable commands, see below.
So we now know that the system can see our device, with lsusb and with ir-keytable. Repeat delay = 500 ms, repeat period = 125 ms Supported protocols: lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmpīus: 3, vendor/product: 1784:0011, version: 0x0100 eHome Infrared Remote Transceiver (1784:0011) You can run the next command with or without sudo (as root) without root you get less information, You will not see the bus data and extra capabilities.įound /sys/class/rc/rc0/ (/dev/input/event7) with: We can do some checks without configuring anything. If you have it installed you can remove it if you like with the following. You do not need lircd or lircd-x installed to get this working, it will not even come in handy later. If you have tried to get lircd working on Ubuntu 18.04 and succeed very well done! I gave up and sorted it out this way. The name it returns is a bit of a give away ? eHome Infrared Transceiverīus 002 Device 002: ID 80ee:0021 VirtualBox USB Tabletīus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub The receiver will then be visible in your server.īus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubīus 002 Device 003: ID 1784:0011 TopSeed Technology Corp. You did make a backup didn’t you? Please do not use comments to say your production mythtv-frontend got screwed up. Make sure you back it up before you start. Since this is going to end up controlling Mythtv you will probably use a convenient front end machine. The IR sensor is USB so that goes into the host and then when the virtual machine is running use the menu option Devices -> USB -> TopSeed Technology Corp. I did my testing on a Virtualbox guest running a Minimal Ubuntu Linux 18.04 server and Raspbian Stretch. Similar to the black one on the right but mine is silver ? It is also a look-a-like for a MCE remote.
I use a generic IR remote which is IR6 compatible. with ir-keytable there are less files and less configuring to deal with.