[How to do instruction] Using FLIRC and other USB input devices for remote control

[musiclover]

(Assume you have updated the Flirc Firmware to the latest ?)

Plug the flirc into a PC and open the Flirc app. There is a setting for adjusting the key response. Adjust and save then plug back into the Pi.
https://support.flirc.tv/hc/en-us/articl...ey-Presses

Otherwise there is an old posting from Jason on the Flirc forum indicating a problem with some remotes and a fix. Ymmv.
http://forum.flirc.tv/index.php?/topic/9...ls_19_menu

Thanks for the tips. Unfortunately setting the inter-key-delay is not possible. The current Flirc windows software doesn't have this menu item, and flirc_util from the command line says "N/A for current firmware". Today I tried a different remote, but to the same effect...

[TheOldPresbyope]

One a freshly installed 6.7.1 if I say

thd –dump/dev/input/event* | tee keycodes.cap

I get

Error opening '–dump/dev/input/event*': No such file or directory

So I found out that there is a type in the first Code-Box, the command must be like in the second one:

thd --dump /dev/input/event* | tee keycodes.cap

Thanks for posting this and my apology for not acting sooner. (A house move has severely disrupted my online life!) I fixed the offending line.

Regards,
Kent

[TheOldPresbyope]

So I managed to activate Flirc on moOde and remote controlling my Pi is working. But the funny thing is: I have to press each button twice before it works. From the command line e. g. "mpc toggle" works perfectly well, but activating it from the remote needs two keystrokes. Anyone any idea?

It's been a while since I worked with this so I'll need to get back up to speed. What remotes have you tried? (This is mostly a matter of personal curiosity.)

If you have to press a button twice to trigger an action in moOde, what do you see in the output from the thd --dump exercise when you press and release the same button twice? For all the remotes I've tried, I get the same output for each cycle. I haven't been able to replicate the odd behavior you are experiencing.

Regards,
Kent

[musiclover]

[quote pid='27617' dateline='1606836718']
It's been a while since I worked with this so I'll need to get back up to speed. What remotes have you tried? (This is mostly a matter of personal curiosity.)

If you have to press a button twice to trigger an action in moOde, what do you see in the output from the thd --dump exercise when you press and release the same button twice? For all the remotes I've tried, I get the same output for each cycle. I haven't been able to replicate the odd behavior you are experiencing.

Regards,
Kent
[/quote]

I've tried the Justboom remote and an older one for a Marantz CD Player, both to the same effect.

thd --dump etc. shows the following:

First press of the button: not reaction, second one:

EV_KEY  KEY_STOPCD      1       /dev/input/event1
# KEY_STOPCD    1       command
EV_KEY  KEY_STOPCD      0       /dev/input/event1
# KEY_STOPCD    0       command

The Marantz remote worked without this double press effect on a lircd install on Volumio...

Thanks for you help.

Joerg

[musiclover]

[quote pid='27617' dateline='1606836718']
It's been a while since I worked with this so I'll need to get back up to speed. What remotes have you tried? (This is mostly a matter of personal curiosity.)

If you have to press a button twice to trigger an action in moOde, what do you see in the output from the thd --dump exercise when you press and release the same button twice? For all the remotes I've tried, I get the same output for each cycle. I haven't been able to replicate the odd behavior you are experiencing.

Regards,
Kent

I've tried the Justboom remote and an older one for a Marantz CD Player, both to the same effect.

thd --dump etc. shows the following:

First press of the button: not reaction, second one:

EV_KEY  KEY_STOPCD      1       /dev/input/event1
# KEY_STOPCD    1       command
EV_KEY  KEY_STOPCD      0       /dev/input/event1
# KEY_STOPCD    0       command

The Marantz remote worked without this double press effect on a lircd install on Volumio...

Thanks for you help.

Joerg
[/quote]

[TheOldPresbyope]

@musiclover 

First press of the button: not reaction, second one:

EV_KEY  KEY_STOPCD      1       /dev/input/event1
# KEY_STOPCD    1       command
EV_KEY  KEY_STOPCD      0       /dev/input/event1
# KEY_STOPCD    0       command

Well, no reaction to the first press explains why you need two button presses before moOde will respond but I don't understand why there's no reaction.

I'm not aware of any reason why the remote or the Flirc would need to be "waked up" and the triggerhappy daemon is constantly listening for events once it is enabled. [By way of contrast, I do have a Bluetooth remote which goes into a power-save mode after a period of inactivity and has to be waked up again with an initial press before it will transmit but that's an RF-based technology, totally different from the IR-based technology here.]

I don't have a moOde 6.7.1 player running at the moment. I just now tested my Flirc/Roku combination with the latest release candidate of the upcoming moOde 7.0.0 and each button press/release gives the thd output I expect.

Random thoughts which likely lead nowhere - What model RPi are you using and is it adequately powered? What other USB devices are plugged in, especially HID devices?

Regards,
Kent

[DRONE7]

(Assume you have updated the Flirc Firmware to the latest ?)

Plug the flirc into a PC and open the Flirc app. There is a setting for adjusting the key response. Adjust and save then plug back into the Pi.
https://support.flirc.tv/hc/en-us/articl...ey-Presses

Otherwise there is an old posting from Jason on the Flirc forum indicating a problem with some remotes and a fix. Ymmv.
http://forum.flirc.tv/index.php?/topic/9...ls_19_menu

Thanks for the tips. Unfortunately setting the inter-key-delay is not possible. The current Flirc windows software doesn't have this menu item, and flirc_util from the command line says "N/A for current firmware". Today I tried a different remote, but to the same effect...

Option would be to download an Ubuntu linux distro and burn it to USB pendrive using Etcher then boot your PC from that and use the Flirc app there.

[TheOldPresbyope]

Are we on the same page here? The linked material at support.flirc.tv discusses what seems to be the reverse problem: one button press generates two duplicate responses when only one is wanted; not two button presses are required to generate just one response.

Regards,
Kent

[DRONE7]

Are we on the same page here? The linked material at support.flirc.tv discusses what seems to be the reverse problem: one button press generates two duplicate responses when only one is wanted; not two button presses are required to generate just one response.

Regards,
Kent

Totally !     The adjustment works plus and minus so if the Flirc has been set-up from another PC or for another O/S (eg XBMC) and is in Plus mode then 2 buttons....so adjust for minus mode...

I bought a used Flirc and had the same problem....adjusting worked..

Then there is always the other link...  
http://forum.flirc.tv/index.php?/topic/9...ls_19_menu

[TheOldPresbyope]

Ok, thanks. The penny finally dropped.

PS - it appears one can install Flirc configuration software on a Mac OsX or Linux host rather than have to use a Windows host, although I haven't tried.

https://flirc.tv/support/flirc-usb