[mythtv-users] USB IR Receivers

[Kirk Bocek]

On 8/30/2015 11:31 PM, Alec Leamas wrote:
> On 31/08/15 02:36, Kirk Bocek wrote:
>>
>> So we do have something here. I see note about installing the output of
>> -r elsewhere so it can be used.
>
> This basically means that you should be able to use the devinput 
> driver and configuration file using this device as input (or, perhaps 
> better, the corresponding link under /dev/input/by_id). This is with 
> the devinput limitations, notably the lack of sending (blasting) support.
>
> Also, depending on what buttons you actually are pressing, the key 
> mappings looks strange... If a plain 'left' button is decoded as 
> LEFTSHIFT, LEFTALT and/or LEFTMETA ther moight be a problem. It should 
> then be resolved at the kernel side (ir-keytable has many options, 
> none of which I'm used to).
>

So, circling back, why can't I get any output out of this receiver (that 
I was *promised* would work)?

  /etc/lirc/lircd.conf:

include "/etc/lirc/lircd.conf.devinput"

/etc/lirc/lirc_options.conf:

driver          = devinput
device          = /dev/input/by-path/pci-0000:00:14.0-usb-0:1:1.0-event-ir

by-path and by-name are the same thing, they are both symlinks to 
/dev/input/eventX. Running IRW with a generic MCE remote working with 
another setup gives no output. But systemctl shows IRW connecting:

$systemctl status lircd
â lircd.service - LIRC Infrared Signal Decoder
    Loaded: loaded (/usr/lib/systemd/system/lircd.service; enabled)
    Active: active (running) since Mon 2015-08-31 07:23:43 PDT; 5min ago
  Main PID: 2851 (lircd)
    CGroup: /system.slice/lircd.service
            ââ2851 /usr/sbin/lircd --nodaemon

Aug 31 07:23:43 liva2 lircd[2851]: lircd-0.9.1a[2851]: lircd(devinput) 
ready, using /var/run/...ircd
Aug 31 07:23:43 liva2 lircd-0.9.1a[2851]: lircd(devinput) ready, using 
/var/run/lirc/lircd
Aug 31 07:23:56 liva2 lircd-0.9.1a[2851]: accepted new client on 
/var/run/lirc/lircd
Aug 31 07:23:56 liva2 lircd-0.9.1a[2851]: initializing 
'/dev/input/by-path/pci-0000:00:14.0-us...ir'
Aug 31 07:23:56 liva2 lircd[2851]: lircd-0.9.1a[2851]: accepted new 
client on /var/run/lirc/lircd
Aug 31 07:23:56 liva2 lircd[2851]: lircd-0.9.1a[2851]: initializing 
'/dev/input/by-path/pci-0...-ir'
Aug 31 07:24:07 liva2 lircd-0.9.1a[2851]: removed client
Aug 31 07:24:07 liva2 lircd-0.9.1a[2851]: closing 
'/dev/input/by-path/pci-0000:00:14.0-usb-0:1...ir'

ir-keytable --device 
/dev/input/by-path/pci-0000:00:14.0-usb-0:1:1.0-event-ir -t

Yields nothing with this generic MCE remote.

Now at the end of

ir-keytable --device 
/dev/input/by-path/pci-0000:00:14.0-usb-0:1:1.0-event-ir -r

I see:

...
scancode 0xff0000fe = KEY_RESERVED (0x00)
scancode 0xff0000ff = KEY_RESERVED (0x00)
Enabled protocols:

So, knowing the MCE remote is RC-6 let's try adding that protocol to the 
testing:

$ir-keytable --device 
/dev/input/by-path/pci-0000:00:14.0-usb-0:1:1.0-event-ir -t --protocol rc-6
Invalid protocols selected
Couldn't change the IR protocols
Testing events. Please, press CTRL-C to abort.

So I'm stumped here. Can this receiver work with a generic remote? Does 
it only work with the funky little remote it came with needing two 
CR2032 batteries (which will render it useless for me.)