[mythtv-users] iMon remote, some keys not working?

Tom Harris thom.j.harris at gmail.com
Sat Oct 3 16:48:48 UTC 2015


Thanks for the responses.

Hika's response was correct, I was able to add Play/Pause events via the
MythTV settings.    But, there were some keypresses that I can see in
ir-keytable, which didn't generate a key event within MythTV.

After a bit more digging, I found that the basic key code mappings are in
/lib/udev/rc_keymaps/imon_pad
For some of the keys that MythTV was not picking up, I re-mapped them to
simple keyboard inputs.    Since this system only runs mythfrontend, that's
not a problem.  But, it does seem kludgey to do it this way..  and I'm sure
I'll forget about it by the time I do my next frontend upgrade in a couple
years.

It seems like this was close to "just working" out of the box.  The USB
device was auto-detected and the drivers mapped the remote keys to
reasonable settings.   The gap was that MythTV did not recognize the
multimedia keys by default.    This seems odd.  Isn't MythTV an extremely
good use case for those multimedia key inputs like "KEY_PAUSE"?  It also
doesn't seem like there would be drawbacks to mapping these by default.



On Thu, Oct 1, 2015 at 12:08 PM, Alec Leamas <leamas.alec at gmail.com> wrote:

> On 01/10/15 18:40, Hika van den Hoven wrote:
>
>> Hoi Tom,
>>
>> Thursday, October 1, 2015, 6:36:46 PM, you wrote:
>>
>> On Thu, Oct 1, 2015 at 5:20 AM, Hika van den Hoven <hikavdh at gmail.com>
>>> wrote:
>>>
>>
>>
>
>> I was struggling to understand the relationship among all these layers and
>>> to pull any debugging info at each point.  So, this really helps.
>>>
>>
>>
>> As said I haven't tried it, but I assume it to work. The other way
>> would be to use lirc and .lircrc as in the old way. e.g.
>>
>> begin
>>        prog = mythtv
>>        button = KEY_PAUSE
>>        config = P
>> end
>>
>>
> With ir-keytable decoding all keys you should basically be able to do it
> with or without LIRC. However, here is potential to run both tracks
> simultaneously and that might certainly be a mess.
>
> If you not use LIRC, just disable the comṕlete service so it doesn't mess
> with anything. This means that  the application will receive events from a
> /dev/input/eventXX interface without any lirc involvement.
>
> If you want to use lirc, use the devinput driver and the same event
> interface as device. This will make the button presses available on the
> lircd socket (var/run/lirc/lircd?) where multiple applications can read it
> and map it using ~/.lircrc. Applications (here multiple) must not access
> the event interface, they should listen to the lircd socket.
>
> Cheers!
>
> --alec
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20151003/3b4f5c53/attachment.html>


More information about the mythtv-users mailing list