Search the Community

Hi guys, I'm having an issue with Flirc that I'm struggling to get my head around and would appreciate a little assistance with. On my HTPC I can record commands ok, however they don't do anything. Stranger still, if I try to erase a command, it tells me 'Button already erased' indicating the command hadn't been recorded after all. I have tested this with several remotes, always with the same result. The Flirc device itself is fine. I know this as I can attach it to my laptop and commands record and operate perfectly. My device is the v2 Dori firmware v4.9.3 The below log is straight after I cleared the config and then recorded the 'Wake' command onto my remote, followed by two presses of the button I had programmed. Any idea on how I can troubleshoot the issue? I have searched the forums but don't see anything that helps me get to the bottom of this Wed Oct 28 2020 19:10:16 Flirc GUI Version v3.25.3 Operating System: Windows *** Device Disconnected *** *** Device Connected *** Firmware Version: v4.9.3 SKU: Flirc 2.0 [dori] Git Hash: 0xcb185bde <3>delete_hash(394): hash not found <3>delete_hash(394): hash not found :e:25824 0,1821,438,2354,5266,215,2233,188,2298,499,1893,665,1121,478,2397,235,2018,430,1944,529,4753,550,1788,1561,2026,1293,943,740,2837,430,2228,404,520,310,998,581,1103,555 :e:25 0,1002,404,352,253,926,360,748,323,266,10115,555,3842,374,1965,132,2305,630,1810,638,4636,374,2285,878,2505,396,2077,555,1159,180,1392,525,1974,1370,1129,421,1469,354 :e:26 0,294,1237,762,1116,132,5685,451,2043,159,2241,585,2104,369,1172,322,2185,477,2181,292,2021,477,4713,615,1922,1159,2167,210,848,322,1568,214,947,581,1154,499,1840,1508,1206,473,994,581 :e:5865 0,1662,438,1586,456,244,5308,607,1732,767,2129,348,1883,482,1046,767,1814,633,2396,266,1784,612,4558,714,1789,685,257,607,1840,711,546,318,994,525,1146,538,1223,456,1706,1642,965,637,964,659 :e:26 0,2746,231,1133,5594,441,2114,421,1841,637,2129,396,1072,529,1789,633,1944,637,1948,551,4714,449,1991,1365,1918,1426,1185,633,1020,607,991,734,1812,1492,956,158,1452,715 :e:26 0,497,352,913,568,1081,598,396,5305,581,1892,607,1733,771,1866,473,1180,659,2281,214,1862,163,313,266,1758,607,4689,585,1819,448,334,448,2211,1056,1603,396,1525,240,1004,542,1970,874,1495,551,1206,560 :e:1340 0,4548,5193,771,2000,452,2073,400,1840,659,1064,641,1840,607,1793,767,1784,663,4796,482,2022,1375,2000,1348,1073,606,866,736,1064,162,2298,1029,2000,288,891,581 :e:26 0,2244,378,1677,5342,359,1784,741,1936,162,262,240,1827,512,965,741,1737,715,1785,711,2043,482,4645,689,1884,1409,1763,1638,836,766,1003,258,1387,711,1814,1535,1103,499,1102,555 :e:26 0,3065,356,1298,5094,607,1841,688,1962,188,2535,344,1038,563,1759,767,1948,581,1944,504,4856,447,1815,1586,1732,792,469,343,1099,473,995,663,990,685,1793,1556,917,737,891,767

Just got my FLIRC today. Was very excited to try it. Now, three hours later, pretty upset with it. After ignoring a virus warning (via Windows 10 Defender) in both Firefox and Edge, I installed the FLIRC gui. I launched the gui, the device was found as connected. The gui asked me to upgrade the firmware from my shipped firmware to 4.9.3. I did so. I programmed several buttons (via the Harmony Hub remote app on iOS) to test functionality. Simple stuff, just red button types 'a' on the keyboard. Nothing works. The debug log shows that IR commands are being received but no commands are recognized by Windows. E.g., pressing the red button in the Harmony app (which should type 'a' on the keyboard via the FLIRC gui mapping I've permed) does nothing. Read through the forums and reddit for about two hours or so looking for a solution. Uninstall, reboot, reinstall software twice, including manual deletion of Program Files dir for FLIRC. Nothing works. At one point, the FLIRC gui shows the FLIRC dongle as disconnected. After another reinstall, this was fixed. Create a forum account to download firmware 4.9.1. Install 4.9.1 firmware. Remap keys (e.g., 'a' to red button again). Still nothing. Any suggestions? The fact I can't even get the FLIRC to do something as basic as push 'a' or the 'enter' key on command (despite IR logs in the app responding to those keypresses) is just about enough for me to be convinced my FLIRC is broken. Log from FLIRC gui: ------------------- Wed Sep 9 2020 17:43:08 Flirc GUI Version v3.25.3 Operating System: Windows *** Device Disconnected *** *** Device Connected *** Firmware Version: v4.9.1 SKU: Flirc 2.0 [dori] Git Hash: 0x24052832 :e:17441 0,4947,4793,909,1577,903,1583,899,1587,899,743,929,1557,903,1584,903,1583,904,4370,899,748,899,743,903,743,899,743,930,1557,903,744,899,743,1744,1583,904,743,899,743,878 :e:24 0,4950,4792,899,1587,924,1562,899,1587,898,744,903,1583,898,1588,898,1588,899,4370,903,743,899,748,898,743,903,744,898,1588,898,743,903,743,1743,1583,899,747,899,747,899 :e:24 0,4949,4792,903,1583,903,1583,899,1639,847,748,898,1588,898,1588,899,1587,899,4370,899,747,899,747,899,747,895,747,899,1587,899,747,899,769,1712,1592,894,748,898,769,877 ------------------- flirc_log.zip

Is it possible to launch a command line ? My first guest was to try to replace your keyboard strokes mentioned , by Windows + R (only Windows will not allow to be recorded), then switch to macro record, 's', 'h", etc. For type shutdown -t 300 -s Are you able to proceed on your side ? There is a better option in GUI ?

I have set up flirc on windows 7, I have the harmony 650 remote control. I have gone through the relevant how to guides to set up flirc with harmony. When I open kodi, flirc is doing random left control, so if watching videos it is forever going backwards every couple of seconds, on menu's it is going into to setting, but essentially the command of left is just repeating itself. Any help please?

I'm hoping to use the Flirc so that a family member who is not comfortable with change can continue using the simple generic remote control they are used to ("GE Big Button" - 33701). I'm not trying to map all of the TiVo controls just a few select items. I've managed to get channel up/down mapped to "Page up" / "Page down" which mimics those buttons for them. But I'm missing is the volume controls. I haven't been able to find a button combination that controls volume so far. I saw that Flirc can apparently transmit IR codes as well as receive them but I have not been able to figure out how that works. I have the existing TV control so I have been able to see the IR pattern for those buttons on the original TV remote. If I could figure out how to map that original IR pattern to the appropriate volume up/down/mute buttons that would be awesome. Or if anyone could give me some suggestions for keyboard combinations that might be worth trying? I even tried plugging a USB keyboard in and tried a lot of different keys with no luck. The only other option I can think of is to get a remote that can learn IR commands and teach it the TV volume command and then use the Flirc for commands that need to go through the TiVo Stream. That may be the direction I have to go with if I can't figure out a way for the Flirc to control volume either through the Stream or by relaying the IR code. I'd rather stick with the remote they know. Appreciate any suggestions.

Good Evening, i bought a Xiaomi TV 4S (Android TV based). It's Bluetooth controlled. So i try Flirc to remote it with a Harmony One+. I tried several configurations in the harmony Software but no command reached the tv. Is there a Guideline/HowTo which are the first steps to do? Thanks in advance.

@randman but also to you happens, that you have to point the remote ir towards the shield ? If you point the ir remote, a little more sideways can you still command the shield? or does it not receive infrared signal?

I bought a 8 device universal remote, thinking i could customize some of the extra buttons on it. turns out if the 4 digit profile device doesnt have a command assigned to it the IR stays blank (confirmed by using smartphone camera to see IR code) Anyone know what real physical device has the app1 app2 and app3 buttons along with all the other buttons? i want to assin all keys in nvidia shield using app called button mapper.

I am trying to configure FLIRC USB v2 with Kodi. It is all working fine apart from being able to use long-press of the Enter key to access the Context menu. I am using an LG Magic Remote programmed to emulate a Samsung Blu-Ray remote. If I use the original Samsung remote and long-press the Enter key, the context menu in Kodi appears ok. If I use the LG Magic Remote and long-press the Enter key it just acts like a short press of the Enter key. I think I need to assign the 'C' key to the long press of the Enter key but whenever I try and assign a command to the long-press of the Enter key I get a message indicating that it is expecting the second key (macro?). I can successfully program a number key on the remote to be the C key which opens the context menu. I just cannot get the long press to work. What I want is: short-press of Enter key = Enter key on the keyboard long-press of Enter key = C key on the keyboard

Hi all A new user and a new owner of Flirc V2, I am having problems trying to figrure Out how to shut my pc down using the logitech harmony hub with the IOS App. I can wake my pc no problem as any command key wakes the system but for the life of me i can not figure out how to shut down xbmc/kodi at all. All i want is to shutdown xbmc/kodi with a single command and also to create a activity in ios. I dont have a remote i just use ipad ios logitech harmony hub app and there does not seem to have any commands to shut a pc down xbmc/kodi power. I have even tried mapping the red button to a keymap in xbmc/kodi and still will not work.. I loaded the software in a different computer to try and see if i could change a keypress but everytime i press a key it wants to learn a command which i can not do as i dont have a remote that sends a shutdown code to kodi. am i missing somthing here ? as when i added the flirc and used kodi there seems to be very littile buttons to do anything with not even keyboard shortcuts. any help would be great thanks

Use this guide to derive the HID page and key code of an HID event device or original remote connected e.g. via USB, I2C or Bluetooth to a Linux PC, or to verify that your Flirc actually sends the events you expect. HID page and key code can be grabbed under Linux following these steps: 1. Find the event devices associated with your HID devices using "udevadm info -a <device>" with <device> walking through /dev/input/event*. There might be multiple devices for a single hardware component, e.g. for a Harmony Hub there is one for HID mouse events, one for HID keyboard events, one for HID consumer control events, one for HID system control events, ... 2. Monitor the desired event devices (usually requires root) using "sudo evtest [--grab<] <device>" for each device required. The optional parameter "--grab" is essential if you want to stop the recorded events to be forwarded to and interpreted by the system, like I did to stop my system going into standby whenever I sent the sleep event that I wanted to record. If you want to use "--grab" on your local keyboard or such, you might want to either attach a second keyboard or run the command over the network via SSH, so you can abort the monitoring by sending Ctrl+C. 3. Perform the key presses on the device you want to record. Each key press will emit 2 events, one for key down (press), one for key up (release), example output for the "0" key: Event: time 1593381762.020128, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70027 Event: time 1593381762.020128, type 1 (EV_KEY), code 11 (KEY_0), value 1 Event: time 1593381762.020128, -------------- SYN_REPORT ------------ Event: time 1593381762.020198, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70027 Event: time 1593381762.020198, type 1 (EV_KEY), code 11 (KEY_0), value 0 Event: time 1593381762.020198, -------------- SYN_REPORT ------------ 4. Interpret the output; you are interested in the value of the MSC_SCAN (scancode) of EV_MSC (miscellaneous) events. The value is hexadecimal and for HID devices with the last 4 digits being the HID key code (0x0027) and leading digit(s) the HID page (0x07). 5. HID page 0x07 events (HID keyboard) can be programmed using "flirc_util record_api <modifiers> <key code>", where <key code> is the decimal representation of the HID key code you fetched above (e.g. 0x27 = 39), and <modifier> is a logical or-ed list of modifier keys to be held down while <key code> is sent (see "flirc_util help record_api"). I ran into an intentional limitation of flirc_util, limiting <key code> to values <= 101. Unfortunately, flirc_util silently programs the key anyway without a warning, leaving a key that is never sent. This cost me a lot of time while trying to send the correct codes to my hardware, being the Flirc the culprit by never sending the programmed keys. Jason is currently checking whether the limitation will be removed.

Using evtest I found out that the Harmony Hub emits HID page 0x07 code 0xf8 (KEY_SLEEP), thus using "flirc_util record_api 0 248" should record a key that emits this button press. The key gets recorded by the command without any error or warning, but also using evtest I found out, that the button press is actually not emitted (nothing is emitted at all). This is not limited to key code 248 but seems to be true for every key code >101. Is this a bug in flirc_util or in the Flirc firmware?

Hi, I just bought a Flirc to finally get control over my Xiaomi Laser TV. It is an Android TV based projector that I currently control using a Harmony Hub via Bluetooth, but the BT connection is not reliably established, so this is where Flirc shall get into the game. I was able to set up all keys using flirc_util recory_api and both the HID Keyboard/Keypad and Consumer pages from the Android documentation [ https://source.android.com/devices/input/keyboard-devices ] and the USB.oro and FreeBSD HID documentation except for the PowerOff button, that should put the device into standby mode. Unfortunately all the Power/Sleep/Coffee/Screenlock keycodes from the docs either let the shutdown menu pop up (which does not allow activating standby but only full system shutdown), or have no function. So I tried adding a new "NVIDIA Shield" (not Shield TV) device, which emits the correct PowerOff command via BT, to the Harmony Hub and pair it with my Linux PC to try and extract the keycode using e.g. xev. Unfortunately, sending this command to my PC via BT immediately puts it into sleep mode without logging any keypress, even after removing the corresponding keyboard bindings from the GNOME settings and systemd-logind. Also issuing the PowerOn button only emits the character "0" (== keycode 102, which is used for all keycodes from HID page 0x0c), but not the required modifiers which encode the actual command on page 0x0c. So I have to assume that the PowerOff button will give me unuseful information, too. Any help or hints on either how to capture the required HID data for this key from BT further commands to try beside those from https://source.android.com/devices/input/keyboard-devices pages 0x07 und 0x0c how to encode further HID pages such as 0x01 generic system commands with flirc_util record_api is greatly appreciated. Thanks in advance! UPDATE WITH SOLUTIONS TO MY REQUEST ABOVE (for anyone running into a similar problem): HID page and code can be grabbed under Linux following these steps: 1. Find the event devices associated with your HID devices using "udevadm info -a <device>" with <device> walking through /dev/input/event*. There might be multiple devices for a single hardware component, e.g. for my Harmony Hub there is one for HID mouse events, one for HID keyboard events, one for HID consumer control events, one for HID system control events, ... 2. Monitor the desired event devices (usually needs root) using "evtest --grab <device>" for each device required. The parameter --grab is essential if you need to stop the recorded events to be forwarded to the system, like I did to stop my system going into standby whenever I send the sleep event that I want to record. 3. Perform the key presses on the device you want to record. Each key press will emit 2 events, one for key down (press), one for key up (release), example output for the "0" key: Event: time 1593381762.020128, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70027 Event: time 1593381762.020128, type 1 (EV_KEY), code 11 (KEY_0), value 1 Event: time 1593381762.020128, -------------- SYN_REPORT ------------ Event: time 1593381762.020198, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70027 Event: time 1593381762.020198, type 1 (EV_KEY), code 11 (KEY_0), value 0 Event: time 1593381762.020198, -------------- SYN_REPORT ------------ 4. Interpret the output; you are interested in the value of the MSC_SCAN (scancode) of EV_MSC (miscellaneous) events. The value is hexadecimal and for HID devices with the last 4 digits being the HID key code (0x0027) and leading digit(s) the HID page (0x07). 5. HID page 0x07 events (HID keyboard) can be programmed using "flirc_util record_api <modifiers> <key code>", where <key code> is the decimal interpretion of the HID key code you fetched above (e.g. 0x27 = 39), and <modifier> is a logical or-ed list of modifier keys to be held down while <key code> is sent (see "flirc_util help record_api"). I ran into an intentional limitation of flirc_util limiting <key code> to values <= 101. Unfortunately, flirc_util silently programs the key anyway without a warning, leaving a key that is never sent. This is what initially cost me a lot of time while trying to send the correct codes to my hardware, being the Flirc the culprit by never sending the programmed keys. Jason is currently checking whether the limitation will be removed.

Well, that's a weird one. Raspberry 4, Flirc v2 (4.9.3) Flirc app 3.25.3 sees the flirc dongle, can program it etc... The second I play a track (mpd) the gui shows disconnected and freezes. I stop playing the music, and after a few seconds the guy becomes responsive again. Same from command line (after quitting the GUI just to be sure). flirc_util commands are working fine, but if I play a track: "device disconnected, can't run command" The Raspberry pi 4 is attached to an external USB DAC. I initially thought a USB power issue and bought the official raspberry wall unit but it did not solve the problem. Sadly the logs say little. THis is when I plug the flirc: Jun 17 21:57:54 raspberrypi kernel: [ 1530.238733] usb 1-1.3: new full-speed USB device number 11 using xhci_hcd Jun 17 21:57:54 raspberrypi kernel: [ 1530.379765] usb 1-1.3: New USB device found, idVendor=20a0, idProduct=0006, bcdDevice= 2.00 Jun 17 21:57:54 raspberrypi kernel: [ 1530.379781] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Jun 17 21:57:54 raspberrypi kernel: [ 1530.379793] usb 1-1.3: Product: flirc Jun 17 21:57:54 raspberrypi kernel: [ 1530.379806] usb 1-1.3: Manufacturer: flirc.tv Jun 17 21:57:54 raspberrypi kernel: [ 1530.394739] hid-generic 0003:20A0:0006.000A: hiddev96,hidraw1: USB HID v1.11 Device [flirc.tv flirc] on usb-0000:01:00.0-1.3/input0 Jun 17 21:57:54 raspberrypi kernel: [ 1530.405952] input: flirc.tv flirc Keyboard as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3/1-1.3:1.1/0003:20A0:0006.000B/input/input9 Jun 17 21:57:54 raspberrypi kernel: [ 1530.469246] input: flirc.tv flirc Consumer Control as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3/1-1.3:1.1/0003:20A0:0006.000B/input/input10 Jun 17 21:57:54 raspberrypi kernel: [ 1530.469646] input: flirc.tv flirc System Control as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3/1-1.3:1.1/0003:20A0:0006.000B/input/input11 Jun 17 21:57:54 raspberrypi kernel: [ 1530.470106] hid-generic 0003:20A0:0006.000B: input,hidraw2: USB HID v1.01 Keyboard [flirc.tv flirc] on usb-0000:01:00.0-1.3/input1 Jun 17 21:57:54 raspberrypi kernel: [ 1530.479915] hid-generic 0003:20A0:0006.000C: hiddev97,hidraw3: USB HID v1.11 Device [flirc.tv flirc] on usb-0000:01:00.0-1.3/input2 Jun 17 21:57:54 raspberrypi mtp-probe: checking bus 1, device 11: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3" Jun 17 21:57:54 raspberrypi mtp-probe: bus: 1, device: 11 was not an MTP device Jun 17 21:57:54 raspberrypi mtp-probe: checking bus 1, device 11: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3" Jun 17 21:57:54 raspberrypi mtp-probe: bus: 1, device: 11 was not an MTP device There are no new log entries as I start/stop the music and get the disconnect/reconnect. Not sure what to do ....

Hi, I've configured a One For All remote with Flirc to replace an Nvidia Shield 2019 remote. My problem is that I configured a button in the remote using the long press option and now, if I leave the button pressed too long, it sends the command twice. So in the end, I need to release the button the moment I see the Shield react to the command to avoid this issue. I've also tested with Kodi and it does the same thing. Is this a known bug? Thanks.

I was hoping to use the Flirc USB IR receiver as a way of adding a remote into my music server setup. I'm currently using Daphile as the platform for my server. It supports keybindings for player functions and I've tested it with a number of usb keyboards and it recognizes them all. Daphile recognizes the Flirc USB receiver as: "flirc.tv flirc Keyboard [usb-0000:00:13.0-1.3/input 1] " "flirc.tv flirc Consumer Control [usb-0000:00:13.0-1.3/input 1] " "flirc.tv flirc System Control [usb-0000:00:13.0-1.3/input 1] " however it won't capture key presses with any of these selected. What's strange is I was even able to control the local UI of Daphile with Flirc and a remote with buttons mapped to arrow and enter keys.... I believe Daphile is built on Gentoo Linux. I also tried using the Linux command line flirc_util options (enabling/disabling USB modes, etc.) but nothing seemed to change. Any help/suggestions/other firmware or configuration recommendations would be appreciated! Thanks!

SOLVED: this was caused by a USB extension cable. Set the USB module straight into the pi and no pb. and on rasbpian (Linux raspberrypi 4.19.118-v7l+ #1311 SMP Mon Apr 27 14:26:42 BST 2020 armv7l GNU/Linux ) I get: flirc_util settings [E] lib/libtransport/hid.c hid_recv_packet(161): Wrong response length = 0 [E] lib/libtransport/hid.c hid_recv_packet(162): hidapi: (null) [E] lib/libtransport/transport.c _recv_packet(126): _recv_packet: recv packet error = -1 [E] lib/libtransport/transport.c _dev_send_cmd(201): recv timeout Error getting version device disconnected, can't run command

Hello! I use Flirc v2 together with a Logitech Harmony One+ on Debian Buster (10.4) and MythTV. On the Flirc I have selected a full keyboard layout. The problem is that I need to press every remote button twice for the command to work. Before I bought a Flirc I used ir-keytable and did not experience this problem. Any help or suggestion would be appreciated. Best regards, Peter

Thanks, I see your post Mick. This seems more like a workaround than an actual solution. I did connect Jason with someone from Logitech support but he couldn't get them to connect him to the right people to get the command added to the myharmony software so the problem lingers. Until then maybe I will try your solution, or just keep manually putting it to sleep before shutting down my system. Thanks!

OK, still playing around with it trying to get it work the way I want and found that part of the problem is with the Built in Profiles being selected. If I uncheck all of the Built in Profiles, I don't get the a2a2a2a2 any more but I must now press a given button twice to get a single command. I started a new thread in the Bugs forum.

I have been trying to get my FLIRC working with an MCE remote to interface to an older (non-MCE) app and have found the following. I go into the GUI, clear the configuration and uncheck all of the Build in Profiles (Side note: After exiting and restarting the GUI I sometimes find some or all of the Built in Profiles are now checked. Multiple retries will finally get them all unchecked). I then confirm using Notepad that none of the numeric keys on the remote are sending any commands. I return to the GUI and using the Full Keyboard controller, I map the "a" key to the "1" button, "b" key to the "2" button ...... "j" key to the "0" button. I return to Notepad to confirm operation and find I must press a numeric button twice to get a single letter. I simply want to send an "a" each time I press the "1" button and so on. How do I get that to work? Thanks, Bill Windows 10 Home Version 1909 (OS Build 18363.836) FLIRC GUI Version 3.25.3 Firmware v4.9.3

Hi there I have the same behaviour with a panasonic vieja TV. Five month ago, i tried to setup FLIRC for my HTPC with Logitech Harmony Hub. I gave up after some crazy sessions trying to configure the device. Today i try to setup Flirc for Libreelec on PI4, same behaviour. The setup was impossible because of ghost events. FLIRC debug IR mode receive tons of signals. I was becoming mad when i search for the device responsible of it, i finally try setup on laptop and not on HTPC and when i turned off my TV there was no more ghost IR signal received. The odd thing is when there's no direct path between TV and FLIRC, it reflects on glass (windows, small table with glass on it, mirrors). @Polarfox when Jason talk about backlight i think it's not light behind TV but a technique where a light straighten image behind front screen (so a light send towards you). I will make setup with tv off and try to use FLIRC with TV on. Then if FLIRC don't work correctly trying to put it in an opaque pipe to see if i can get it better. Best regards PS : TV model used is TX-P50VT30E EDIT: I just tried what i suggest above : FLIRC Setup : OK with the pipe and TV ON FLIRC Use with nothing : Fail, flirc unusable, 1 of 10 try on the same command is caught by the FLIRC, 0 received for some other commands. FLIRC Use with a long pipe and a cover : OK, works perfectly even if remote is not exactly aiming directly into the tube So i will think of smaller pipe to see if i can get it work. @jason do you think of a way to ignore ghost events ? Is it possible to decrease FLIRC sensibility ? if not possible actually can it be a firmware improvment ? Best regards

Not a linux user but in Windows CMD do you replace bash $ flirc_until with flirc_until.exe? I'm currently having issues with my Flirc's excepting commands for Kodi and I thought I'd try command line. Thus far I've only done flirc_util.exe settings to see what the current settings are. They are as follows: 3.25.3 FW Version: v4.9.3 SKU: Flirc 2.0 [dori] Branch: master Config: release Hash: 0xCB185BDE Settings: sleep detection: always enabled noise canceler: always enabled inter-key delay: N/A for current firmware variant: Flirc builtin profiles: NA Memory Info: NA product sku: Flirc 2.0 [dori] Recorded Keys: Index hash IK ID key ----- -------- --- -- ------------ 0 A0AB871A 077 02 menu_up 1 5DB5670D 076 02 menu_right 2 CB58A141 076 02 menu_down 3 5DB54866 077 02 menu_left 4 CB58A05A 076 02 menu_pick 5 791733F0 054 04 browser_back 6 1EDDA9CE 077 04 browser_home

To change the viewed channel on Kodi with a keyboard it is necessary to use the up and down buttons to find the channel then press enter to select it. Kodi changes to the channel and after a short delay, removes the information pane from the screen. I am trying to reproduce this behaviour with Flirc. I started by programming the up button with "up" then programming the same button with a Long Press for "enter" and that worked fine. When I tried the same with the down button I kept getting this: ~ % flirc_util record down Press any button on the remote to link it with 'down' Succesfully recorded button ~ % flirc_util record_lp return Press any button on the remote to link it with 'return' [E] lib/libflirc/firmware/fw_4.0.c fl_ver4_set_interrupt(380): Error: key not found Error: You must first record this remote button with the regular flirc_util record command. Example: flirc_util record `<first function>` flirc_util record_lp return I finally guessed it might mean that the first button was already assigned although the error message did not say that. So I deleted the button and redid it and it worked. Perhaps the error message needs amending to be more expanatory? Now when I use it, sometimes it works fine, sometimes when the long press is used it shows the next channel 9i.e., the short press up or down is actioned and then the long press) but opens the one I want but sometimes it not only flips to the next channel on screen but opens it instead of the one I want. I can't reproduce it every time, it simply happens occasionally. Is there anything I can do to prevent it? Additionally, sometimes the screen information clears but sometimes it does not and then the up and down buttons will not work unless I first escape to the plain screen. Again, it is not a consistent error, sometimes it happens and sometimes it does not. Any ideas on this one?

Make sure the GUI is closed before running the command line.