Search the Community

I've been using a harmony since kodi was xbmp (that's not a typo, it later changed to xbmc). I had it matched with an xbox IR receiver which to this day does not seem to have a match. Since moving off the xbox, I've had the harmony paired against an HP MCE receiver, buttons mapped from a corresponding remote. It's worked well but the range/accuracy was always sub par to the xbox receiver, I was hoping flirc was the answer. It's actually been more frustrating to set up than I would have expected. Since the flirc is a learning receiver, and expects you to use its own software to define keys, having a flirc harmony profile, with Commands defined that should represent concrete actions is simply not a good idea. What do the actions in the profile mean? Zoom+? is that mapped to an MCE command code? does flirc's built in profile somehow translate that into something xbmc / kodi understands? even if so, if Kodi changes its keys - now what? the profile is out of date! This is what I and many others have experienced. I believe, the best idea, is simply to have a harmony flirc profile that has commands named the same as the remote buttons - UpArrow is the UpArrow flirc command with some arbitrary remote scan/hex code. Then you go into the flirc software and record that UpArrwow command / UpArrow button with whatever you want - never requiring a flirc profile update! furthermore, it will save time for people because they won't waste time mapping and wondering why kodi / xbmc isn't responding to some commands and then having to map them again manually anyway. This essentially means that the flirc firmware and logitech profile simply have a notion of command codes that are mapped to known harmony buttons, given that a flirc does not have a remote and thus a specific set of buttons. Does this make sense?

Yes, you can delete the button from the GUI but there is also a delete command in flirc_util.exe. If you run flirc_util.exe without any parameters you will get all available commands. The Fn key is a keyboard controller extension and it's not sending anything to the system itself. It just changes the HID code sent to the system by the controller when the key is pressed with or without holding the Fn key. In your case the PrintScrn key is sent when Fn key is pressed but this is just a hardware keyboard behavior. Using PrintScrn HID code in Flirc should be enough.

Hi, Until the feature is implemented you can use command line util to record keypad buttons. flirc_util.exe record_api XXX YYY where XXX is modifier value and YYY is a key HID code. HID codes for keypad are: 83 Keypad Num Lock and Clear 84 Keypad / 85 Keypad * 86 Keypad - 87 Keypad + 88 Keypad ENTER 89 Keypad 1 and End 90 Keypad 2 and Down Arrow 91 Keypad 3 and PageDn 92 Keypad 4 and Left Arrow 93 Keypad 5 94 Keypad 6 and Right Arrow 95 Keypad 7 and Home 96 Keypad 8 and Up Arrow 97 Keypad 9 and PageUp 98 Keypad 0 and Insert 99 Keypad . and Delete So if you want to record a button for keypad 8 without any modifiers then you should use flirc_util.exe record_api 0 96 and after pressing enter the command should wait for you to press some button on the remote. The modifier value is described in the help of the record_api command itself. The flirc_util.exe is in the same folder where the Flirc.exe is installed.

I can't seem to get my zotac out of suspend mode by using the usb port while having a usb keyboard plugged in or using FLIRC. I have tried in the past but gave up and decide to kick the tires again but with no such luck. I have followed the guide posted on the wiki: Archive:HOW-TO:Enable_Wake-On-Device_for_Ubuntu (wiki) Here is a what the lsusb command looks like: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 002: ID 04f3:0103 Elan Microelectronics Corp. ActiveJet K-2024 Multimedia Keyboard Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 006 Device 004: ID 20a0:0001 Clay Logic Bus 006 Device 002: ID 2109:0811 Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Here is the output of the cat /proc/acpi/wakeup command: Device S-state Status Sysfs node P0P1 S4 *disabled pci:0000:00:1e.0 P0P4 S4 *disabled pci:0000:00:1c.0 P0P5 S4 *disabled pci:0000:00:1c.1 P0P6 S4 *disabled pci:0000:00:1c.2 P0P7 S4 *disabled P0P8 S4 *disabled P0P9 S4 *disabled USB0 S3 *enabled pci:0000:00:1d.0 USB1 S3 *enabled pci:0000:00:1d.1 USB2 S3 *enabled pci:0000:00:1d.2 USB3 S3 *enabled pci:0000:00:1d.3 EUSB S3 *enabled pci:0000:00:1d.7 All USB devices seem to be enabled but I am not able to resume using FLIRC or even a keyboard. Any guidance or help would be appreciated.

Here are the "settings". Is this what you need? If not, what command should I run. The uploaded on this site wont let me upload the config file. can i send it to an email? Recorded Keys: Index hash key ----- --------- --- 0 AD0E248D h 1 A827DC1 u 2 1EDDA9CE return 3 CBD72E1A f 4 A0AB871A up 5 CB58A141 down 6 5DB54866 left 7 5DB5670D right 8 CB58A05A space 9 41A02A81 1 10 41A41E01 2 11 30D15701 3 12 41A04841 4 13 3B27A0CE 5 14 3B23CB0E 6 15 2AD3854E 7 16 30D1561A 8 17 BFD0CB9A r 18 EA7DE5C1 tab

Remote - Philips SRP4004/27 I've tried a variety of devices when I programmed the remote. I wasn't ever able to get the Flirc programmed if the R/Y/G/B buttons were enabled. The other issue I noticed when the R/Y/G/B buttons were enabled is that each button had to be programmed twice. So I would program right arrow once, program it again and the repeat that for the remainder of the buttons. Eventually I would get the "this has already been programmed" message, which then threw off the Flirc mapping entirely. I got close once by saving the profile every time I programmed a button. I would then restore the profile once I received the error and would continue programming the Flirc. That failed once I realized that the play button was sending the same command as another button. All of these issues go away when I program the remote to a device that doesn't have the R/Y/G/B buttons enabled. I was able to duplicate this on v1.3.5-rc.2, v1.3.5-rc.3 and v1.3.6. I know that it worked on the old firmware because this all started when I upgraded the firmware on my Flirc. I shouldn't have upgraded the firmware, because it was working perfectly before...

Hi, I got lots of double press issues with v1.3.6 of the GUI and v3.6 Firmware. I fixed the issues by going via EventGhost which (with a bit of work) allows you to manage things better (see ) The other thing you can try is to set the inter-key delay to 7 by using the command line tool. To do this you need to navigate to where your flirc GUI executable is stored and you'll see a flirc_utlil.exe program which you can execute from the command line. It will show the help summary if you just execute it with no commands; the inter-key delay will be amongst those options. Hope this helps

Hi all, suddenly my Flirc stopped working with harmony 650. I have been using Flirc with Fire TV for about a year and suddenly it stopped registering my key presses. I found out when I am very close to Flirc and push the button it works but only when really close, nearly next to it. Tried to reconfigure and what is strange learning the commands from 650 works with any range, I can point the remote to the ceiling and it still learns the command. This problem also happens when using windows I tested with notepad it registered the key presses only on close range. Nothing changed in my room no possible interferences, I think. Please advise. Thanks! flirc firmware v3 gui v1.3.6

I just received my Flirc the other day and am enjoying it so far. I would like to program my Flirc to emit keystrokes that are not present on my physical keyboard; for example, the function keys F13‒F24, or even “reserved” keys, such as those in the 0xA5‒0xAF range (as documented in the HID spec). My idea is to intercept these keystrokes using something like EventGhost or AutoHotkey and transform them into useful complex actions, without having to worry about the actual keystrokes conflicting with those that might happen to be used in normal applications. I'm having trouble getting this to work. For example, if I use the Flirc GUI app to map something to F13 (using the “Full Keyboard” controller), it appears to take, but then I don't get an F13 when I press the associated remote button. Neither EventGhost nor AutoHotkey sees any keystroke at all. Microsoft Spy++ doesn't see any messages generated either. Same thing happens when I use flirc_util to map, say, 0xA5 using the following command line: flirc_util record_api 0 165Am I doing something wrong? Or have I run into a limitation or bug in Flirc, the HID driver, or the OS? I'm using Flirc 1.3.6 with firmware version 3.6 [07F892FC] under Windows 8.1 Update 1 (x64). In the meantime I've set things up using unlikely keystrokes (such as Ctrl+Alt+Shift+F1), but I'd really prefer to do things the way I described.

Hi, I've been doing some hacking with Flirc and EventGhost to get the best possible setup. I wanted all the keys to be intercepted by EventGhost so I could do some more advanced control schemes. My problem was that I don't like mapping remote keys to some arbitrary shortcuts. The problem here is that in Windows I cannot stop key presses just from a specific keyboard (Flirc in this case) so I loose those shortcuts if I use them in Flirc and EG. Now here comes a little trick. Media buttons are not treated as Keyboard events (they are not intercepted by HID keyboard filter driver) but are available to Generic HID plugin in EventGhost. Why is that? Because media keys are not from default keyboard HID usage table but from the "consumer" one. Media keys in EventGhost's Generic HID are received as decimal value of HID code for those buttons. Unfortunatelly Flirc GUI (and CLI too) doesn't have much media keys available to be used. Fortunatelly saved config file has very simple structure :). I've assigned every button on remote to Play button for a reference and then replaced play button code to ranges that are not officially used in Consumer HID Table, from 0x04 to 0x1F, then from 0x23 to 0x2F - this was enough for my remote but there are other unused ranges. Those can be found here http://www.freebsddiary.org/APC/usb_hid_usages.php, table 12 - Consumer. After loading the config back into Flirc I'm getting correct HID codes in EventGhost when I'm pressing buttons. Here are my two suggestions: 1. I don't know if this can be somehow done in the firmware, but when I hold the button pressed on the remote I'm getting a stream of button press events in HID instead of just one (this also happens for not modified config with standard media buttons). When I release the button then HID gets release event correctly. For now I've modified Generic HID plugin to remember last event and not issue it again if enduring events are enabled (required for long press detection and action repeat configuration). Maybe I'm wrong (I don't know HID specifics) but I think Flirc should only send one key press event (on press and hold) and then one release event. If not then forget this suggestion. 2. It would be nice to be able to set arbitrary codes from Consumer table (possibly using hex notation or detected by 0x before the code) using at least the CLI. Maybe new command in CLI like record_hid or something. I know that Flirc can only store 2 bytes per key (modifier + HID code for keyboard table and HID code + 0x66 as a marker for consumer table) so we cannot access codes above 0xFF but I think this is enough for most cases. This would be great feature for advanced users.

Well it all seems to be working now, however I did need to make use of a hybrid solution. Here is the recipe I followed: Firmware: v3.6 with GUI v1.3.6 Advanced Settings: InterKey delay: 4 Noise Cancellation: Off Built in Profiles: On Sequence Modifiers: On Remember that for this remote you need to program each button twice because each button alternates IR signals on sequential presses. 1) Don't use the WMC profile in the GUI! 2) Go to the media keys profile and configure all of these buttons, for this remote it will leave pause, record, eject and a whole bunch of WMC keys unprogrammed - we'll come back to those. This is important because using these keys flirc will send the specific HID command not the keyboard shortcut. 3) Program the remaining keys using the WMC keyboard shortcuts and numbers using the full keyboard EXCEPT for the WMC start (big green button) and the context menu. I get multiple button presses with these shortcuts so we'll do this differently. 4) Use the flirc_util command line tool to directly set the HID events for record, pause and eject - see the excellent discussion on how to do this here: 5) Install EventGhost and get it responding to the HID events from the remote reliably using the modified EventGhost Generic HID plugin (changes by @yawor) to prevent multiple HID events on a single button press - see to get the modified plugin. Use the already programmed media keys to test. 6) Add in the MCE program interaction plugin (not the MCE remote plugins, they do something different) and setup two macros, one to do the context menu event and one to do WMC start. Using the ability to add arbitrary HID events use two of the unused entries in table 12 (I used 4 and 5) set the flirc to send these HID events on the key presses for 'more information' (context menu) and the big green button and then use these events to trigger the corresponding MCE actions in EventGhost. (note that you have to use EventGhost because the corresponding HID entries are too far up the table for flirc to use - or at least I couldn't get them to work) 7) Have a beer (or other libation of you choosing) and save the configuration Doubtless I'll change things and I will post my ongoing experiences here. UPDATE: The Play, Pause and Guide keys can sometimes be a bit twitchy, especially if the wielder of the remote has heavy fingers. So I've put Play, Pause and the shortcuts (like Guide and Live TV) all on blank HID entries to avoid double presses. So that play and pause still work with PowerDVD, I've also setup a switch in EventGhost that detects whether PowerDVD is in focus, and if so, adds in the appropriate shortcuts. WMC shortcuts don't interfere with PowerDVD but the opposite is not true, hence the need to switch on certain keypresses depending on the program. Very close to calling this 'final' now.

Hi, I seem to be having some issues Double Press issues on a Dell E6410 Win7 x64 setup using a Harmony 650 remote. I've changed the command repeat settings on the remote to 0 and the inter-delay in the FLIRC GUI to 6, but for some reason every button I press results in a double press. I've plugged the FLIRC into my MacBookPro to test on that machine and there are no discernible issues, so this looks like an isolated issue with possibly the Dell or Win7 settings. Has anyone else experienced this issue and if so do you know of a fix? Any feedback is appreciated.

I want to control my devices not via a remote, but via a mobile app that I am developing. Some of my devices are network-ready, but for the others, my only option is IR and for those I'm thinking a network connected IR blaster. But my IR blaster cannot know what to blast unless I find a way to tell it. So I'm thinking I need to record signals from my existing remotes and have the blaster play back the recordings upon command. I'm wondering if the FLIRC can be my tool to do that. Can it RECORD a signal like I want? P.S. where's the python API promised on the homepage? I found the FLIRC github but nothing stuck out as a Python API; is buried somewhere in xbmc drivers or something?

hi lately i'm having issues with my flirc in combination with a harmony touch & openelec. it seems is not picking up the correct sequences anymore. example: latest firmware flirc app on mac set to kodi harmony touch set to flirc>xbmc i press 1 on the remote and 7 lights up in the controller app clear config learn key 1 press 1 on the remote command learned press 1 on the remote 7 lights up try to relearn 1 and error that command is already mapped and this happens for a lot of other key's does anyone have an idea what's happening

Thanks for the fast response, but unfortunately it doesn't work for me... I can use flirc_util to record the command, but it still will not power up from S5. I know the flirc is receiving power in S5 because I have run a 5V line direct from the psu and confirmed with a multimeter. I have tried a microsoft RC6 compatible remote as well as my harmony but it is not working.

Hi, sorry to bump a month-old thread but I also cannot get my Flirc-SE to power on from S5 state. I believe I am running the latest firmware (1.3.6?). The PC is running windows 7 and windows media centre. I am using a harmony remote. Did I read correctly there is something I need to do on the command line to enable this functionality? thanks.

I have new asus chromebox m004u, hamony 650, logitech 830 keyboard I ordered a flirc today and have read a few posts about issues getting to developer screen to run chrome. The logitech 830 does do ctrl-d and works to get in to chrome os problem is the only way back to openelec is to shutdown SINCE THERE APPARENTLY IS NO RESTART ON A CHROMEBOX!!!!!!!!!!!...DIRECTED AT GOOGLE. 1. can flirq learn the ctrl-d from the logitech to boot to chrome os? If not I can live with using the keyboard. 2. can flirq somehow start the chromebox from being off...ie boot up NOT wake up. I know the chrome keyboards come with a power on button that will start the chromebox and I could "borrow" one if I needed to ...would that be a way???..have flirq learn the chrome keyboard boot up command. My chromebox is in a closet with all the other equipment so the only way I have been able to start it and get from chrome back to openelec is to shutdown then walk down the stairs to the basement and push the button on the side of the unit to power it back up. OR better yet this is only to go form chrome back to openelec...is there a keybopard commind to go back htat I missed? any help appreciated?

Hi everyone, just wanted to say I got everything I wanted to work using latest firmware for flirc and my harmony 650, but can't get the restart command, where you hold down select and play for 5 seconds on the fire tv remote duplicted. I tried using the ok and play buttons I had mapped on my harmony using the amazon fire controller gui and I even tried the full keyboard and mapped control alt and delete to a button. I tried just pressing and releasing the button and holding it down til the fire rebooted, but it never did. Any idea on how to map this command? Thanks. Eric

How to use EventGhost and Flirc for maximum XMBC awesomeness. OK folks, I’ve been really waiting for a way to interface FLIRC with XBMC. Unfortunately, the buttons that the FLIRC program provides for XBMC are pretty limited; most universal remotes come with a bajillion buttons that aren’t used under normal conditions for XBMC. Additionally, some buttons don’t really have counterparts in FLIRC or the keyboard, such as YELLOW, BLUE, RED and GREEN. Finally, the practice of editing keymaps.xml or whatever XBMC uses is painful. Because of this, I wanted to interface EventGhost’s XBMC2 plugin as well as FLIRC to maximize the capacity of my remote. Requirements: FLIRC – Duh. XBMC – Double Duh. EventGhost - WINDOWS ONLY, I don’t know any comparable linux or mac software, and don’t ask me about it. A remote control - I am using Vizio Remote Control XRV1TV 3D ($20 on amazon), which comes with the normal remote keys and a qwerty keyboard on the back. This remote is pretty kickass since it has QWERTY if you need it, and is purely IR-based, so FLIRC can program all the buttons for it. However, programming the QWERTY remote makes it more difficult than a regular universal remote. If someone could just create a sexy universal IR remote with QWERTY keys underneath it, it would make me so happy. Unfortunately, no such remote exists, and these VIZIO remotes are probably the best I’ve seen for this purpose. Someone needs to make a kickstarter for these. Technical Background: FLIRC processes signals from your remote control and turns them into keypresses on a virtual keyboard. Eventghost can intercept those keypresses using the Keyboard Plugin, and with the correct addons, can re-translate those button-presses into any arbitrary action you want. In this case, I’ll use it to program specific XBMC-related keys, but this could be extended to many other things, as long as you figure out how to do it in eventghost. Step by Step Instructions. I presume that you know how to navigate XBMC, FLIRC, and hopefully Eventghost. If not, ask someone more technically inclined to help you. 1. Verify that your remote control does not interfere with your TV! This step is very important; I found out after the fact that certain buttons on my Vizio remote work on my Element TV. Power, Info, Menu, Volume, Channel and some QWERTY keys all had effects on my TV. Since the remote isn’t programmable, there’s no way to avoid it. I used a marker to erase the labels on the buttons that had weird effects on my TV so I wouldn’t press them. If you are using a universal remote, try to select a code which has no overlap with your TV or other electronics. 2. Install FLIRC and verify it works with your remote. 3. Install XBMC and verify it works. Maybe setup your library and some videos for or something you can browse through or troubleshoot. 4. Program your basic remote keys on FLIRC. Programming your keys depends on whether you have an ordinary remote, or one with QWERTY keys. An ordinary remote is simple; just use FLIRC’s GUI to program all the keys that you can see direct equivalents for. For example, use the XBMC keyboard layout to program the keys in your remote. Don’t worry at this point if you have a lot of extra keys on your remote that don’t correspond to any keyboard keys. We’ll deal with them later. For the time being, try to map the buttons with the corresponding keys on the XBMC keyboard. (http://wiki.xbmc.org/index.php?title=Keyboard) For a QWERTY remote, the best way to do it is to program the QWERTY keys first, then program the non-qwerty keys (play, pause, ff etc) last. This way, you later have a way of determining which remote buttons collide (are mapped to the same key). Note that switching controllers on the FLIRC menu doesn’t change buttons you programmed on another controller. This means that you can use the extra set of buttons on the Windows Media Player controller and program it to your remote, then switch over to Full keyboard and program another set of keys without losing the WMP-labelled buttons. This allows you to map some extra keys easily. SAVE YOUR WORK AT THIS TIME. 5. Map out remaining keys with modifier keystrokes. Your remote should be pretty well-stocked to do the basics at this point. However, some buttons (color keys, special manufacturer keys etc) have no direct keyboard equivalents. Additionally, I might want to not use a particular button that is keyed to a QWERTY button. To bypass this limitation, let’s program our own keys for these buttons. I want to map out the Yellow button on my remote. To avoid collisions/overlap with other buttons, I’m going to use modifier keystrokes (control, shift, alt, windows keys etc). In this case, setting FLIRC to recognize Control-Alt-Shift-Y should be unique enough as a keystroke. Open FLIRC and go to full keyboard mode, and press the Control-Alt-Shift-Y keys on the on-screen keyboard. I then associate it with the Yellow Button on my remote. This set of keystrokes is unique enough that it is unlikely that any other program requires this keystroke. You can do this for any button, as long as it hasn’t been programmed or something. Feel free to play with any other key combination; I suggest using Control-Alt-Shift or Control-Alt-Win and go down the QWERTY keyboard to simplify mapping your buttons. SAVE YOUR WORK UNDER A DIFFERENT FILENAME SO YOU HAVE A BACKUP. 6. Install Eventghost and make a new configuration. Eventghost will give you some default configuration, which is actually pretty helpful if you want to tinker around and learn some things. But in our case, we’ll start from scratch and just click New Configuration. 7. Install the appropriate plugins. Now the only ones that we really need are Keyboard, the XBMC2 and the Task Create/Switch Events plugins. Feel free to replace the XBMC plugin with whatever one you are using (like WMP/VLC). We add Task Switcher for a later step to ensure that all buttons we map specifically to XBMC will only work when XBMC is run. At this point, you should see something similar to this. For now, right-click the XBMC2 folder, and press “Disable Item” so that we can program buttons easily. Remember to enable it later on. 8. At this point, press a button on your remote, and you should see something (an event) pop up on Eventghost’s left pane. For example, I mapped the Yellow remote button as the Control-Alt-Shift-U key, and if I press it, I see the command Keyboard.LShift+LCtrl+LAlt+U. Several lines pop up for this key combination, but just use the full command. (Ignore the LAlt and L+Alt+Printscreen stuff, this is just an artifact of taking screencaps). Whenever you press anything on your keyboard (real keyboard or FLIRC remote), this will pop up and be accessible as a command. 9. Earlier I mentioned I wanted to map the Yellow button on the remote to the “Movies” screen of XBMC. To do this, open the XBMC2 folder in Eventghost and go to Windows > Show Movies Screen. Press the Yellow button (or whatever button you want to map) to underneath the XBMC2.Show Movies Screen action. This associates pressing Yellow on the remote with XBMC’s Show Movies command. Repeat this for the other buttons you want. Once you are satisfied, right click the XBMC2 folder and enable it. Run XBMC and test the remote if you like (it helps if you run it in windowed mode (the key is “\”). Experiment with the button assignments until you are happy with it. Note that there are bajillion options you can try, which can be confusing, but with luck you can do it. Take a look at the XBMC keyboard map (http://wiki.xbmc.org/index.php?title=Keyboard) for whatever keys are being used by XBMC natively and try to work with or around them. Repeat as necessary for any other special keys you would like. In this way, I was able to program my remote for all the buttons I want. This step is insanely powerful; I can associate any unique keystroke I want with an XBMC action, without it overlapping with the QWERTY keyboard. I can even arbitrarily associate keystrokes with windows functions (restart/reboot/suspend etc)! Just take note which keystrokes you have used for which buttons. Note: The Buttons>Remote section and the Actions>General sections have identical macros for some commands such as direction keys. If there are identical macros, map only one, otherwise you might get multiple keypresses from one button press. Warning: It is not a good idea to associate common keystrokes with eventghost commands, especially with QWERTY remotes. You may get collisions and key interceptions which are hard to diagnose (See last section of this document for details). I suggest leaving most keys unprogrammed, and only map the special 4-button combination keystrokes for those keys you want to remap. 10. Configure the Enable Exclusive commands. Create a new folder (I name it Context) and move the XBMC2 folder inside it. This is a needed step in order for us to use the Enable Exclusive commands. After that, create a new macro (the orange gear thingie) and select “Enable Exclusive folder/macro”, and in the next dialog box, select the XBMC2 folder inside the Context folder. This should give you a macro that says “Enable Exclusive:XBMC2.” Create another macro in the root directory and select “Disable”, and in the next dialog box, select the same XBMC2 folder as before. Start up XBMC, and alt-tab or go to windowed mode, and look at Eventghost’s log. It should have an action “Task.Activated.XBMC” which you should drag to the “Enable Exclusive:XBMC2” macro. Similarly, there should be a “Task.Deactivated.XBMC” which you should drag to the “Disable XBMC” macro. What was the point of this whole thing? If set up correctly, this tells Eventghost to only activate the XBMC remote commands when XBMC is the active window. Once XBMC is minimized/alt-tabbed/closed, the Disable XBMC macro disables the XBMC commands to prevent other apps from recognizing the keyboard commands. Although we used combination keystrokes to map certain buttons, there is still a small chance that a keystroke will be recognized by another program, and using Enable Exclusive will prevent some of that problems. Anything in the same folder at the same level as XBMC2 will be disabled by the Enable Exclusive when it is triggered, so you could put remote commands for another application there. Finally, if you want to map other buttons to work outside XBMC (such as power or others), simply put it outside the Context folder, and it will not be subjected to the Enable-Exclusive command. 11. Sit back and enjoy! (Or swear profusely and bugger with the configuration more.) Notes and Warning: 1. Since FLIRC acts as a virtual keyboard, and since Eventghost can’t distinguish between multiple keyboards, ALL YOUR COMMANDS ARE SENT AS IF YOU TYPED IT ON ANY OF YOUR KEYBOARDS. There isn’t any way (as far as I know) to respond to commands coming from Keyboard#1 separately from commands coming from Keyboard#2. In other words, Eventghost treats all keyboard commands as coming from the same source, and can’t distinguish keystrokes from different keyboards. To sidestep this, the Eventghost forums suggest using something called the HID plugin instead of the keyboard plugin, but it doesn’t seem to work for FLIRC, and I know nothing about it. 2. When using the keyboard plugin, note that Eventghost will intercept the keystrokes if they are assigned to a particular action. As stated in the Keyboard Plugin Description: “Notice: If such a keyboard event is assigned to a macro, the plugin will block the key, so Windows or another application will not see it anymore. This is needed to permit remapping of keys as otherwise the old key would reach the target in conjunction of another action you might want to do and this is mostly not what you intend. But this blocking only happens, if a macro would actually execute in succession of the event. So if the macro or any of its parents is disabled, the keypress will pass through.” In other words, if you’ve mapped a buttonpress, eventghost will intercept it, unless that button-press is disabled. If you forget this, you might wonder why you start missing letters or have strange program behavior when you are typing while eventghost is on. Since many keypresses are pretty much universal and standard (up, down, left right, enter etc) don’t program them, and remember to use the “Enable Exclusive” macro. Only reprogram the keys if necessary. This is a necessary consequence of Note#1, since we can’t do it in a keyboard specific way. 3. The main reason why QWERTY remote programming is more difficult than regular remote programming is you could have collisions between keystrokes (eg. the space button in the QWERTY keyboard works as the pause button in XBMC, but you might want them to be totally separate for your remote). You have to take note which keys correspond to which. Coupled with Note #2, this is why my suggestion is “Only reprogram the keys if necessary.” 4. I still don’t know how to associate XBMC addons to eventghost applications. For example, I want to figure out if I can map the Pandora or XBMCflix app to a button, but so far I don’t know. Online guides mention JSON or some other thing in Eventghost, but I can’t get any namespaces to appear in the JSON options in eventghost. 5. Eventghost has some features which can get around some limitations of FLIRC (Long keypresses, context-dependent button presses, button timing features), but its requires reading and diving into Eventghost. Using these options, I was able to get my HTPC and TV to turn on/off simultaneously with one button. However, the wakeup button requires setting the command-line interface (see elsewhere in the flirc forums on how to do that), and does not actually map a physical button keyboard, but some sort of device-based means to go from suspend mode to normal mode. 6. FLIRC still has some bugs which make the process a little tricky. For example, I had a FLIRC-related bug which prevented me from deleting and remapping several keys. Also, using the command line interface “keys” flag does not show keys with modifiers (see step 5), so try to remember the keystrokes you use for them. All and all, it can be done with some hard work and enough ADHD.

I am not sure if the problem is with Flirc itself or if I am missed a step in the setup process. I have a Harmony Ultimate remote. I added Flirc > xbmc (I also tried Fire TV). Now When I press any button on the remote nothing happens. If I go to the Flirc GUI and try to program any of the buttons nothing happens. ( I select the button I want to program and then press the desired button on the remote). GUI shows FLIRC as connected. I ran it with Firmware v3.6 and v3.5. EDIT: Figured it out. It was my mistakes, the command were being sent through the Harmony hub and not the remote itself. I had to get FLIRC close to the hub :D

I just got a Harmony 650. It's my first ever Harmony remote. Using the MyHarmony software I set up a Sony VCR as the dummy device to use to teach commands to the Flirc. The default inter-key delay is 100 ms, and I can set it for anything in the 0 - 1000 ms range. Are you saying that if I adjust this setting it may help with the return button repeat issue? What do you recommend for the setting? Also, there's a setting called "command repeats". The default setting is 3, but it can also be set at 2, 1, or 0. What I glean from reading the help file is that lowering the value will help with the type of problem we're experiencing. Is that true? I'm away from my system right now or I'd test these settings. On the other hand, if I weren't away from my system right now I'd probably be catching up on my TV shows instead of playing with the Flirc and the FireTV. :)

Hi, This is more of a OS-level issue than Flirc one. I think you would get more answers from Squeezeslave/lite community. I don't even know how those daemons can be controlled remotely. Does they have a TCP or Unix socket open that allows to receive commands? Is there some CLI command that is able to send commands to the daemon? You may want to look at triggerhappy daemon. It has ability to capture input events and execute scripts/binaries assigned to specific key combinations. That way you can separate the issue from the Flirc/keyboard input itself and work out a way to control your daemons :rolleyes: with some scripting.

I think I'm having a related issue although I'm using a Yamaha RAV370 universal remote. I recently upgraded Flirc to 1.3.4 (fw 3.5) and suddenly my keymappings stopped working. I reloaded my config to no avail so I decided to start re-programming it. This remote sends alternating key sequences so I have to record two key presses per key assignment. I'm finding that in some cases Flirc is reading the second key assignment as a previously assigned key. as an example, let's say I assign the up arrow , then I assign the left arrow, the second key assignment for the left arrow will sometimes become the up arrow. It will pop up a "Button already exists!" dialog box. I've followed some of the troubleshooting tips from this page: https://flirc.zendesk.com/hc/en-us/articles/204074695-Flirc-isn-t-sending-the-correct-function-to-my-device are there any additional diagnostics / troubleshooting available? all of this worked properly with firmware 3.3, is there any way to downgrade the firmware for a quick fix? I'm using Flirc on a mac running OS X 10.7.5. I didn't see any command line utilities for the mac. Thanks

Hi all, I have a real newbie question .... I XBMC running on an "always on" Raspberry Pi connected to my TV's HDMI2 socket. I plan to use the TV's remote, via Flirc, to control XBMC but how do I stop Flirc receiving signals, when I am watching TV, and then passing them to XBMC ? For example, suppose I 'link' the channel up button on the remote to be 'page up' in XBMC ... how do I stop Flirc from sending the 'page up' command to XBMC when I change channels when watching TV ? Regards, Adam

Hi, I would like programming two button whis the command - (minus) and + (plus) Today I try to make this command whis the flirc software V. 1.35 and the "Full Keyboard" To generate the command I try the following: create "Minus" in Flirc: --------------------------- Control + Button after the 0 (Zero) Button in the first line from the Flirc "full Keyboard". create "Minus" in Flirc: --------------------------- Control + Button after the 0 (Zero) Button in the first line from the Flirc "full Keyboard". Now my question is it this right or wrong? I ask this because "flirc v.135" will told me I store the following command. -(minus) = lcontrol + dash +(plus) = lcontrol + equals Thank you for your help and sorry for this question. cu, MediaCenter Owner