Search the Community

Thanks to kramer and Chris! for their replies. The lsusb command did show the device (I'm assuming it is the one showing up as "Clay Logic" as that does not exist when FLIRC is not plugged in). The weird thing was I can run the command twice within seconds of each other and sometimes the devices is there and other times it isn't. I grabbed the remote and hammered the up/down arrows and noticed that when the device does appear using the lsusb command I can get the menu to move up/down, but only once out of every 50 or so presses. The device seems to show up when usb devices are queried about 50% of the time. Moving on to power. I checked my power supply against the RPi requirements. It is 5V and 700mA as specified on the raspberrypi.org website. Would you suggest something with even more amps? What I'm using is just a generic cell phone charger from an Android phone, not the "official" RPi power supply cable you can purchase. I've read in a few other places that powered usb hubs sometimes make a difference when having issues with usb devices as well. Is this worth a try?

Openelec's Raspberry Pi builds have ssh enabled. So you can ssh into your box. ssh -lroot your.box.ip.address ​at the prompt type the following and press enter lsusb the output of this command this will confirm if your flirc is being recognized.

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.

How can I command the FLIRC to open a program when I push a button on my Harmony One remote? I'd liked it to open XBMC, is this even possible?

Yes, that's what I've been doing. Pairing and deleting in the GUI is not a problem for me up to a certain point. Oddly, most buttons delete correctly in GUI mode and in the command line up to a certain point (maybe after I've programmed ~30 keys or so). After that, deleting several other buttons fail, even though it displays a successful deletion attempt ("Erased Button" on the GUI, "Button Deleted Successfully" in the command line). The only way to delete these entries is to wipe everything out. I can still add entries, but I can't delete them. I'm running Flirc Version 1.0.5 [fw_v255.9-18-geb49aca] Firmware Version: 256 04-01-2013, so I think I'm up to date with firmware and software. I'm going to do more tests to see if there are any issues (try another PC or something), but please let me know if you have any ideas.

More information about this error: in both command line mode and in GUI mode, I can attempt to delete the key, and both mention that the deletion is successful. However, using "flirc_util keys" shows that the key is not deleted, and still remains. I tried multiple attempts to delete it in Gui mode, and it keeps saying "Erased Button". Trying to program a keystroke to replace it does not work, and gives the message "Button already exists." Certain other buttons can be programmed and deleted as normal, but not others. Any ideas?

I have the same problem with 2 different boards. Flirc used to wake up an old Acer Revo in Windows, but no luck with these. Boards I'm using: Asus P8H77-I Gigabyte GA-H77N-WIFI I can wake using an MCE IR adapter. Tried latest beta and older betas with recorded wake command. Using both Windows7 and 8.

Oh, I see. In the meantime you can use the "Full keyboard" layout... although the windows key isn't in the GUI (yet) so it would have to be command line: I'll move this thread to "suggestions" part of the forum (sorry for bouncing this thread around)

I went back to the computer that is working with flirc and reset everything from scratch. Confirmed it was working and the keys were programmed correctly using Notepad. Plugged the flirc back into the problem computer. Things are working better, it's not going completely crazy with non-stop phantom keypresses. But I tested it in Notepad and it was sometimes giving me multiple keypresses when I pushed a remote button once. So I adjusted my Windows keyboard settings and that seemed to help with this problem. The Enter key is still being sent periodically, however. I tried setting the interkey delay using the CLI, but couldn't even do that because it sends the Enter key before I can type the command. Is there any way to narrow down what is sending the Enter command? EDIT: Adjusting the Windows keyboard setting didn't help with multiple key presses. It is still randomly sending multiple key presses when I press the remote button once.

I have a Raspberry Pi and I also mucked around with kbdrate and other settings to no avail. I recently found the interkey-delay setting on the flirc command line and voila! No more rapid button presses. Maybe give it a try...

Hello All, I got my first flirc (first two) in the mail today. The first one is for my HTPC (Windoze 7 Pro SP1). I'm running NextPVR and didn't have a working IR input for my Hauppauge 45 button remote. It was no problem to set up, the software works well (although a little time consuming). It seems that all the remote keys are working as I programmed them, to replicate the keystrokes used by NPVR. The trouble is it's only passing every-other remote command through to NPVR. I have to hit every remote button twice to get the response of one from the software. At first I thought I was pressing the remote buttons to fast, but I tried waiting over 10 seconds between presses, it didn't matter, it was still only sending every-other button press. My actual keyboard works fine with NPVR (how I have been using it so far). I saved my config and created a simple Minimalist config with the same remote that I tested with Win-dohs Media Center, which yielded the same every-other result. I've attached my files for both the NPVR config and the minimialist config, if that helps. Any thoughts? Thanks, -Brad H45_minimalist_flirc_config.fcfg H45_NPVR_flirc_config.fcfg

I just received my FLIRC!!!! Very cool! I am running Win 8 with XBMC Frodo. I can configure FLIRC to work with minimalist setting but when I try XBMC, the go command is not responding and nothing records as a key map? Does anyone have suggestions?

First off I just want to say that I really enjoy using my flirc, thanks for making such a great product! That said, I really think this should be the default behavior of the wake command (to also put the computer to sleep when pressed) but that may not be possible so here is my solution. Sorry this is so long but that's only because it goes step by step by step. :) Obtain the beta firmware and utility. Current ones as of this writing available After you extract the zip you might need to move the firmware file to the same folder the flirc_util.exe file is in. Open a command prompt and navigate to the folder flirc_util.exe is in. If you have already set up your remote buttons then you should back up your flirc's config, Type flirc_util saveconfig myConfig Then to upgrade the firmware type flirc_util upgrade fw_255.9.bin You can then reload your config flirc_util loadconfig myConfig.fcfg You can now record a button to wake up your computer when it is sleeping. If the button you want to use is already mapped to something you will have to clear it first with flirc_util delete and press the button on your remote that needs to be cleared. Then record the wake command flirc_util record wake and press the button on your remote you want. To make the flirc able to wake the computer type flirc_util suspend_detect enable (there are still bugs and error messages when this is enabled but you can mostly ignore them.) Save your flirc config again now flirc_util saveconfig myConfigWake At this point you should have a remote that will wake your computer from sleep. Its always good to test things so go ahead and try it out! So now that that works we need a way to put your computer to sleep. Eskro has made a great guide on how to do that with a system call shortcut. But we need to put these two together somehow. So instead of a shortcut to a system call we will make a shortcut to a .bat file that will make the system call and other various things. Before you go any further you should move the flirc_util.exe and your myConfigWake.fcfg somewhere more organized. Mine are at C:\HTPC\Flirc. In this folder create a new txt file and name it Sleep.bat Right click on the Sleep.bat and click edit then paste this into it and save it. cd c:\HTPC\Flirc flirc_util loadconfig myConfigWake.fcfg flirc_util suspend_detect enable rundll32 powrprof.dll,SetSuspendState So there is a little bit more in there then just the sleep command but it will soon be clear why. Next we need a way to run this bat file. In Eskro's thread some people suggested creating a shortcut in your startmenu or on the desktop that has a shortcut key. That worked fine for me until I started XBMC and then it wouldn't work any more so I made an AutoHotKey script for it instead and haven't had any more problems. So go download AutoHotKey and install it. Make another txt file and name it Sleep.ahk. Right click on Sleep.ahk and click edit then paste this into it, save it, close it, and double click it to run it. ^!s::Run C:\HTPC\Flirc\Sleep.bat Also we need to make a shortcut of Sleep.ahk and put that in the startup folder in the startmenu. The ^!s in the AHK script means ctrl-alt-s. You can make this anything you want, just make it something you are not using already. We need to setup flirc now to make one of the buttons on your remote press ctrl-alt-s or whatever you made it to be. Actually we're not going to make just any button do that, we need to make the same button that wakes up your computer to press those keys. So back to the command prompt! Type: cd c:\HTPC\Flirc flirc_util delete flirc_util record_api 5 22 flirc_util saveconfig myConfigSleep If you are not using ctrl-alt-s then you will need to give the record_api command different arguments to reflect your hotkey. You can type flirc_util record_api help for the syntax and you can look up the list of HID codes starting on page 53 of this pdf file. We need to make one more .bat file that will be run by windows Task Scheduler when windows is coming out of sleep mode. Create a new .txt file and name it setFlircSleep.bat. Right click setFlircSleep.bat and click edit and paste this code into it and save it. cd c:\HTPC\Flirc flirc_util suspend_detect disable flirc_util loadconfig myConfigSleep.fcfg Now hit start and in the search bar type Event Viewer (yes Event Viewer, not Task Scheduler.) On the left side expand Windows Logs and click on System. You should have some recent events from when you were testing your wake button with a source listed as "Power-Troubleshooter" and an Event ID of "1". Right click on one of them and click Attatch Task To This Event. Click Next, Next, Next, then click browse and find your setFlircSleep.bat file. One last thing to do is to make a shortcut to setFlircSleep.bat and put that in the startup folder in the startmenu. This is to ensure that in the off chance that your computer loses power while it's sleeping, the remote will still be able to put the computer back to sleep when it turns back on. The final contents of my c:\HTPC\Flirc folder are: flirc_util.exe Sleep.ahk myConfigSleep.fcfg myConfigWake.fcfg setFlircSleep.bat Sleep.bat and both Sleep.ahk and setFlircSleep.bat have shortcuts in the startup folder. And thats it! Congratulations on setting up sleep/wake on the same button with your flirc! note: The use of the flirc_util suspend_detect enable and disable commands may be unnecessary with future firmware. They definitely help at the moment but it still might not work every time. I only tested this on Windows 7 64bit but it should work fine on other versions. Also I consider this solution a super messy hack (reprogramming the whole flirc config twice every cycle lol) and I hope this functionality will eventually be supported in the main application but its working fine for me and I'm happy with it.

Hi Samuk In answer to your questions: This should help: As you've found the XBMC controller preset in the Flirc GUI contains a few errors, some lesser used functions are not present (to simplify it for the user). Using the Keyboard preset in Flirc gui you can match up the command you want from the xbmc keyboard wiki (http://wiki.xbmc.org/index.php?title=Keyboard) with the button on your remote. For example Exit button on your remote - map to "Esc" Back button on your remote - map to "backspace" using the xbmc keyboard wiki shoudl help with this. We (Jason) will be addressing the erronous commands in the next revision of Flirc GUI - sorry about that. To close xbmc map a keyboard button to ALT+f4 (like you would close any other app on windows). Or try this way: To start XBMC: Try doing the above stuff first, see if that helps your set-up. Let us know and ask more questions if you think of any :) Remember you should be able to do anything you can do on a keyboard with Flirc. Happy flirc-ing :)

I figured out a hacky solution for the volume controls on my DirecTV remote. Basically, vsu is correct that the volume buttons send two commands in sequence so you have to get the Flirc program to record only as the second command is being sent. Whereas most buttons only light up the top-left light on my remote, the volume controls light up the top-left then the top-right immediately after and that seems to indicate when each command is being sent. My solution is to: 1) Hover the mouse cursor over the desired key to record in the Flirc program 2) Press the desired volume button on the remote 3) Wait as the first light blinks and then click the mouse as the second light turns on so that only the second command is recorded. You may have to try a few times to get the timing right, but I now have volume up, volume down, and mute all working with the DirecTV remote through Flirc. If you click too late, just click again to cancel the recording and try again. Strangely the XBMC "mute" button preset didn't work so I had to manually set it to F8 in the keyboard controller.

Backstory: So 24 hours in and I have my Flirc doing everything I want (Ill make the appropriate thank you in another post). I wish I could say the experience of setting it up didn't come with a few speed bumps. I ended up running into an issue where the Flirc would program on my Windows 7 box but when I'd get it on my XBMCbuntu system it wouldn't respond. I tried all the USB ports (some are on different hubs) but alas it would not work. I tried rebooting several times, I tried re-flashing / wiping then re-importing / upgrading-fw / downgrading-fw, nothing helped ... finally I tired a very simple setup (arrows only) and it seemed to be fine. So, I decided to watch the raw input and noticed that the device would initialize in linux but the first time I sent an IR command the driver would crash and the input would disconnect with my full config. At this point I had to simply go through and re-map all my keys and custom buttons from my Harmony One Suggestions: Basically all this is why I think some sort of configuration validator would have fixed this, obviously there was something in the config that was not correct. The reason for XML would be: 1) XML would make it easy for an advanced end-user to look through config, manually edit and fix issues. 2) XML validation could pick up on 99% config errors. 3) XML would make it easy to share configuration (mappings) with other users via the forum. Thanks, Clad

I figured out everything but I have some more suggestions because of the 45 minute battle going from my Win7 box to my XBMCubuntu host. Some sort of configuration validation is needed and the fact the config is not written on XML is mind blowing. Basically the USB keyboard driver would crash as soon as the remote sent its first command. I had to catch the input buffer to see it happen. So after flushing the config and re-setting up all the hard buttons and the 15 custom maps I got it working. It seems solid now, I still also stand behind my recommendation/suggestion for playback in the GUI so a user doesn't need a notepad document open to diagnose button mapping.

I am of course a Newb only having a single programming under my belt of a 3 hour old Flirc but I found something horribly annoying (mostly cause of Harmony) but I can see it could help lots of folks. Giving us the ability while not erasing or learning a command the to playback the mapped IR functions of a remote. What I mean is: After I have programmed a map from lets say the "Play" button on my Harmony to the spacebar on a keyboard layout. If I was to press "Play" button on the remote the GUI would identify that the spacebar is the appropriate mapped keystroke by highlighting the spacebar oh, lets say .. red. I think it would help troubleshooting complex setups.

Just reread your two posts on this topic.... You don't have a Flirc do you? The Harmony is the remote that sends an IR signal, The Flirc is the device that receives an IR signal on your PC and converts it to a keyboard command. Without actually buying a Flirc the Flirc software is useless to you. Without an IR receiver of some type the Harmony is useless at controlling your PC.

The only things on are the HTPC, AV receiver, TV. It does seem to change depending on whether the room lights are on. I've just recorded all my commands at sensitivity levels of 1,2,3 all in my Devonshire Fudge Tin. Now trying it in different USB ports in the PC, also seems to be worst when I plug it into the front port. Out of interest Chris, what are your Harmony settings. At the moment mine are all 200ms and the responding too much to commands one is set at 0. And could the interkey delay be of any use? Currently set at 6 but have tried it at 2, can't quite remember the difference if any. Also am I correct in assuming that the sensitivity level of 3 is the least sensitive, only assume this because when I tried 0 each command could be recorded several times each with a different code from the same key, leading me to believe that the Flirc was picking up a lot of noise. Can upload my fcfg files if that helps at all. I'm using the Samsung TV profile recommended, tried the Panasonic one but as I have a Panasonic TV that didn't work so well, also tried the Sky HD PVR one that someone else recommended but it was very sluggish indeed. I can't really think of anything else to try now, and I can't quite get my head around why the Flirc just keeps repeating the same command over and over until I either remove it or use another button. It's like it gets stuck in an endless loop. I had problems with Phantom commands before but managed to sort that one out with the Fudge tin.

Well i have finally got my Flirc today. Might is say first off, Jason & Chris have been excellent and helped me out a lot with obtaining one! Anyway, onto the issue! Basically i have a Harmony One PLus remote to control everything I have the Flirc added as the recommended Panasonic TV profile and this work, BUT only when i go into Devices and then the correct profile on the Harmony remote. If i just go from the 'Current Activity' menu it sends the command to my Main TV which causes it to bring up errors. Is there a way to prioritise which device a command goes to? For example in this one i want every command to go to Flirc and the only ones not to is the volume. Another issue (Which i may just have to deal with) But i will only ever be using Flirc to control XBMC and as you can imagine when i want to use the remote, i have to first select XBMC as the program on my Mac, only then will the buttons work. Is there a way to force it to send the commands to XBMC even if it isn't the App that you are presently controlling? I probably haven't made sense in this but if you can help in anyway i would very much appreciate it! Thanks, Steven

@ ariflirc Thank you for your post - I almost started panicking when I switched from xbmcbuntu with older kernel to minimal 12.10. I had a bit different experience with my system which is based on Zotac H55 board. Using flirc on win7, openelec and xbmcbuntu I never had need to upgrade from v1 fw. When I switched to minimal 12.10 all of the sudden wake did not work. After finding your post I made new udev rule and it all seemed to work, but.. If I used any other fw accept v1 my flirc would wake system on any remote activity in living room and it would not be present in my system until I would plug it into diferent usb. It would be ok if i wake my system with "wake command" but that was impossible ​to achieve. If i used fw 1 with your udev rule i could wake system with any key on remote (like on other systems I used before) but flirc was again not present on my system after resume. Resolution was to use v1 fw, so my system would not wake on any remote activity and to make a resume script that will reset USB port with flirc after resume. sudo nano /etc/pm/sleep.d/20_flirc_resume case "${1}" in hibernate|suspend) # Switch USB buses off echo -n "0000:00:1d.7" | tee /sys/bus/pci/drivers/ehci_hcd/unbind ;; resume|thaw) # Switch USB buses on echo -n "0000:00:1d.7" | tee /sys/bus/pci/drivers/ehci_hcd/bind ;; esac Note: this is copy of my script it will need to be changed to work on different system. If anyone needs more info pls just ask :) Regards burke

You don't need to run the flirc.exe to use your flirc usb stick with a remote. The GUI exe is just used for the configuration. Once configured, the stick "knows" by itself what to do when receiving a command from your remote (remote command/button press > IR signal to Flirc stick > stick translates IR command to a keystroke).

I'm having the same problem with an RC65X remote, but I think this pertains to all DirecTV remotes. I think the problem with the volume up/down, mute, and TV input buttons is that for these buttons the remote sends a DirecTV receiver IR command prior to sending the IR command for the button itself. When you press those buttons you will see the LED on the remote flash indicating transmission of the DirecTV receiver command flash right before it flashes again indicating transmission of the TV command. I believe the flirc only records the first command for the receiver rather than the whole sequence. Since this first command is probably the same, the flirc interprets all four buttons as being the same. I'm guessing there is a timeout in the firmware to catch the end of the IR signal, but is it possible to make this longer so that it sees both IR commands?

Yes!! I did some digging and read a few topic about interference and I finally got it working. My setup: - Mac mini (with built in infrared switched off) - Harmony one + (choose Samsung LN46C650L1F with interkey delay set to 0) - I did a setup with Flirc software on a Windows 7 machine in a different room then my Mac Mini is (to avoid interference) - I used full keyboard layout Now it is working! Also installed Alauncher en configured command+F1 as shortcut key through the Flirc software. This is really cool. I've been struggling for so long with my Harmony remote and Plex. Now I finally found a solution that works. Thanks!!