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

[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