Search the Community

Just got my two flircs and having my first play tonight. I am using a Harmony 650 with the device set to MCE keyboard. I want to do this as I want maximum flexibility to map as many things as possible. XBMC install is Openelec 1.0.2 I am also using the full keyboard mode in flirc. I am getting a lot of 'Button already exists' errors as I try and record my remote. A by a lot - I mean, basically every button I push. Meaning I pretty much can't record anything. (Of course I know I can use plex/boxee mode with the Harmony but this defeats the whole purpose of the flirc for me). I have tried just the 'minimalist' profile to record the arrows and enter - can't even get through that. It would seem the flirc needs to have finer grained distinction between the signals - Jason - any help??

In searching for a way to get Kodi running on my XBox One, I ran across this site: https://kinkeadtech.com/xbox-one-xbmc-kodi-live-tv-oneguide-integration/ I have not had a chance to play around with this yet. However the author uses Eventghost and a MCE IR dongle. That combination is what FLIRC makes unnecessary. Much of the author's guide is dedicated to getting that combination to work correctly with the XBone. I'm wondering if anyone here has played around with this sort of a setup using FLIRC, and gotten it to work. I may try to find some time this week to play with this, but am pretty busy for the next several weeks. This looks very promising though! EDIT changed title/subject K.

I have Flirc set up with my Logitech Harmony 600 and use a "Full Keyboard" profile. If I try the buttons and keys in Notepad everything is OK. I have tried with Windows 8.1 and Windows 10. But as soon as I try to Pause or move around in Kodi/XBMC, the buttons don't work like they should. For example, I have to press really hard and sometimes it doesn't even react to anything. I don't know if the problem is Flirc or Kodi... I have tried with latest Kodi Isengard 15.1 and also with Helix 14.2... What could be causing this? Please help...

I have a Harmony Touch remote that is set up following the FAQ for harmony remotes here. I have a flirc updated to firmware v3. I cannot get the remote to do any actions at all in XBMC. I have gone into the actions on the harmony remote software and verified that the remote buttons are doing the XBMC actions that I desire but when I use them there is no response. I can go into the Flirc software, full keyboard and learn keys which it says are successfully learned from the remote so I believe the flirc is functional. It can obviously receive signals from the remote. I can verify that the signals are correct via a bluetooth keyboard. Yet when I use the remote buttons nothing happens. I have the XBMC setting selected that remote sends keyboard signals. I have looked around online but can find nothing that actually gets flirc to work. Any help is appreciated.

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.

A few moths ago, I purchased Flirc and programmed it on my windows machine using the Panasonic TV profile as posted at Plugged the Flicr dongle into my XBMCBUNTU machine and everything worked great. Best gadget I have ever purchased. I have since had to reinstall XBMC on that machine and instead of using XBMCBUNTU like I originally did, I installed Ubuntu and added the xbmc packages. I was expecting to just plug the Flicr dongle in and it would work just like before since the programming is contained on the dongle, but it now does nothing. The remote is sending the command(based on the feedback indicator on the remote), but I get no response on the XBMC machine. I did the obvious things: 1. Add 'deb http://apt.flirc.tv/arch/i386 binary/' to /etc/apt/sources.list 2. apt-get update 3. apt-get install flirc Enabled the 'remote sends keyboard commands' option within the XBMC configuration. Was there some other step that I had forgotten or overlooked that was part of the XBMCBuntu install that would be missing by installing the full OS? I have ran out of ideas of what to check, where to look, etc Any suggestions?

I guess my google fu is bad, as I can't find this topic I just bought a mac mini off ebay, and learn about flirc as solution for remote control I have a raspberry pi running openelec, and connected to my panasonic plasma TV I am able to control certain part of xbmc via panasonic TV remote what I want to do is replica this functionalities with the mac mini/flirc/xbmc From my understanding, you need to plug flirc into usb port, and then run flirc app on the machine itself With the mac mini, usb port are all in the back and as far as I know, all mac mini has a buildin IR receiver in the front(??) So... If flirc is plugged into the back of the machine, can flirc still "catch" the IR code that I am pressing on my TV remote when it's in front of the machine? Thanks!

I can see a lot of info on here regarding the Harmony 650 so apologies for starting another thread but I have had no useful success following any of the advice. I currently use an old Sky remote with FLIRC to control XBMC and all works great but I invested in the Harmony so I could also control other hifi boxes and turn off all the system at once. However, its not working half as well as the old remote did. I'm using 2.6 stable version on Ubuntu 64bit. I've chosen allow built in profiles in the advanced settings which is the closest thing I can find to all the mentions on here of a Harmony profile being built into FLIRC post 2.4 builds? Where is this? Is it something that has to be chosen?? I've then proceeded to add all my devices to the Harmony and chosen a Media Centre PC with Flirc build and XBMC model. Firing up XBMC at this stage is a bit of a let down. The direction buttons, number buttons, play / pause and info buttons work but most of the rest do nothing. Most importantly neither the back or exit buttons do anything so you cannot get out of menus in XBMC or clear the screen. However, there is a back shortcut on the LCD activity display that works but thats pretty useless when I have a back button one push away on the remote itself! I've then tried going into FLIRC and reprogramming some of the buttons without much success. Some buttons will record with no problem. Others just simply won't record. 'Back' on the remote won't do anything when trying to record to it. I also wanted, as on the sky remote, to programme keyboard letter E to the 'TV Guide' remote button so it brings up the EPG in XBMC but again nothing happens when pressing it to record a button to it. This is also the same for the red, blue, yellow, green 'colour' buttons that I used on the other remote for TV / Radio / Recordings / Timer screens. I choose the letter in full keyboard view that launches those screens in XBMC but nothing happens when I press them on the remote to record. I've read that they have to have functions assigned to them in Harmony for it to be programmable in FLIRC and ive double checked this and they do indeed have functions assigned. I then tried using the latest beta RC candidate listed here: to see if this would improve the situation but unfortunately I cannot run it on 64bit linux as it looks for shared library files that cannot be found. Is there a 64bit build available? Will it actually improve the situation any if there is? Any help greatly appreciated!

Hi everyone, bought a flirc usb to setup with my rc118 media remote control. Struggling to set up certain button. I thought this would solve remote issues, but it seems like alot more trouble that its worth - may send the flirc back to amazon who i bought it of if i cannot resolve the issues. trying to set the remote (full keyboard) with xbmc. first it wont record f8 - mute button with the corresponding key on remote 2nd it wont record f10 - volume up with volume up on remote. also start button wont work on remote, trying to set xbmc power button but it wont register. please help. Thanks.

Here is how i got my Harmony Smart Control and Flirc to suspend and wake up my HTPC Linux Mint box. Note: make sure you are connecting your Flirc to a consistently powered USB even if the PC is powered off, to choose one; power off your pc and connect your mobile on the desired USB port and make sure your mobile is charging with the box turned off. 1- Download Flirc latest Linux GUI from here (i used the zipped x64 version). 2- Add the file 51-flirc.rules to /etc/udev/rules.d/ (download the file from here), this udev rule insures that the GUI can connect to Flirc without root permissions. 3- Unplug then Plug your Flirc or restart your box for changes to take effect. 4- extract the GUI tools and run the file named Flirc(might need permissions update), you should now see the GUI and the title bar should says connected. 5- Upgrade your Flirc settings and flash it to the latest FW version using the GUI tools, from File -> Advanced, do the following: enable sleep detection. enable noise canceler. enable built-in profiles click on force FW upgrade. 6- by now, you should have no problems running XBMC with flirc and Harmony or any other remote. 7- locate two free buttons on your remote that will be used to wake and suspend your box. 8- follow the steps from 2 to 6 mentioned in this great post (Flirc will apear as 'Clay Logic'). 9- Unplug then Plug your Flirc or restart your box for changes to take effect. 10- Re-lunch you GUI tool and switch to the Full keyboard view. 11- Record the wake on the remote on the Flirc virtual keyboard. 12- Record the suspend button on a combination of your choice (that does not conflict with XBMC's default map!), i used Ctrl+Del. 13- create the file ~/.xbmc/userdata/keymaps/suspend.xml with the following content (change the mapping to your preference in step 12) <?xml version="1.0" encoding="UTF-8"?> <keymap> <global> <keyboard> <delete mod="ctrl">XBMC.Suspend()</delete> </keyboard> </global> </keymap> 14-restart XBMC. 15- if everything went fine, you should now be able to suspend/wake your XBMC box. 16- you can expand the functionality to Gnome by adding the same shortcut to as a keyboard shortcuts to call 'sudo pm-suspend' (need to switch to sudo with no password) 17- using Harmony software i added my wake and sleep buttons to be executed when powering on/off activities or switching between them. Hope this helps, let me know if you need more details! Happy Flircing!

Help Please! The following is the setup I have... and nothing seems to work properly. FLIRC on OUYA running XBMC Setup Harmony Remote as "Manufacturer: Flirc" "Model: XBMC" Recorded buttons to FLIRC on Mac v1.26 app from Harmony Remote I have tried changing the following settings to try and stop either missed button presses, or jumpy presses (multiple hits for a single button press). I seem to either be missing presses, or moving 3 at a time, depending on settings. Harmony : Device Inter-Key delay : 0 - 500ms Inter-Device delay: 500ms (I left this one alone) Command Repeats: 0-3 (I've tried them all) FLIRC: Advanced - Inter-Key Delay: 0 - 6 (tried them all) Noise Canceller: On/Off (I tried this on, seemed to remove the extra keys but caused a huge lag / missed presses. I tried some other settings moved around with this on, but could not get rid of the horrible lag) I'm stuck... Thanks in advance.

Ok, I am at first base with this. This is the video http://www.youtube.com/watch?v=dJHG2K8NQas These are the scripts including the keyboard.xml https://www.dropbox....Z/XBMCEyeTV.zip Features that I have added to the remote are: 1. Screenshots (automatically upload to photo stream) 2. Blacklight 3. Growl notifications toggle (incomplete) and a few more custom app controls as you can see... PS: I dont mean to post such a large image but I cant seem to resize it here.

Hello flirc community. I'm having some trouble with my flirc, and I'm posting here in desperation. I purchased this IR repeater some time ago, and have been using it with great success with flirc on a windows vista machine running xbmc. I recently upgraded my htpc, and switched to linux in the process. I programmed the flirc first without the repeater, and it worked fine. I then moved the htpc into my media closet, cleared the configuraiton and programmed it again through the IR repeater. Flirc records the buttons, but refuses to repeat them. The repeater does still work on my 5.1 receiver. I'm running Ubuntu 14.04, flirc firmware 1.2.6, and the latest flirc packages from the repository. If it matters flirc is plugged into the motherboard usb ports, not the front ones (I ran into that problem when I was running it on vista). Please someone help me salvage this awesome device!

I have a Harmony (650) and I'm setting up Flirc with XBMC. But I can't seem to find any definitive answer on the best method to use. There is a pinned post that describes using a Panasonic or Samsung TV profile to control XBMC (http://forum.flirc.tv/index.php?/topic/22-harmony-remotes/), but that's dated from way back in 2011. Is it still the ideal way to go? Then there's the recent blog post about Flirc having it's own harmony profile now (http://blog.flirc.tv/flirc-has-a-harmony-profile/), and this is dated much more recenlty -- April 1st. However, following the link to the updated firmware that is supposedly needed shows a forum thread marked "(RETIRED)", which would lead me to believe this is no longer needed or supported (I'm not sure which). And when I use this method, nothing seems to work anyway. So, I suppose the ultimate question is: At this point, which method is preferred for using Flirc with a Harmony Remote and XBMC? I'm new here so I hope I'm not rehashing an old question. I might be missing something obvious, so apologies if I am, but I did look. Has there been discussion of creating a Wiki or something similar to consolidate information like this? Also, is there a page that lists the latest firmware versions (stable, beta, etc) so that I can determine if I'm up-to-date?

I looked around and didn't see anything along these lines so hopefully someone can help me out. I have a Harmony Ultimate remote that I'm using with my Flirc that's plugged in to an Ouya. Everything works perfectly with one exception. When I try to use one of the search screens, the arrows don't move around to the different letters so I can spell out my search criteria. Has anyone else had this issue and know of a way to fix it? Thanks in advance for any tips!

GUI Version: 1.06 Firmware Version: 2.0 The AudioNextLanguage mapping in the Harmony XBMC Profile is not working. What it is doing is jumping to the TV Titles Listing.

Hi everyone, So I have my FLIRC running my XBMC (OpenELEC) box and I absolutely love it, but I'm having an issue with what I call hypersensitive wakeup. I put my box to sleep, but absolutely any IR from any remote wakes it back up. I'm using a repurposed Samsung remote from an old DVD player with the FLIRC, but any of my IR remotes will wake the unit. Is there a way to program the FLIRC to only wake on a single, specific key press? Regards, Jeff

I'm using v2.2 of the GUI and I'm trying to get my new Logitech Harmony to work with Flirc + XBMC. I was happy to see that there is a profile for this in the Logitech Harmony database, but when I tried the remote with XBMC launched it didn't seem to work. Is this a known issue or am I doing something wrong?

I'm trying to get this to work with the Flirc but it doesn't respond when I use the Microsoft, MCE, or Media Center PC Codes. Anyone know what codes to use, I would like to use it with XBMC. I even used the codes from and still nothing... PLEASE HELP! :unsure:

Is there a keymap that shows what XBMC functions are assigned to which keys on my Harmony One Remote? The basics are working: play, direction up,down,left,right select. I also have "back" show up on one of the virtual keys on the screen. I am using the updated firmware v256 on my Flirc and have Selected the Flirc XBMC "device" on my Harmony One remote control. XBMC is running on my Raspberry Pi displaying on my TV (via HDMI). I've had a look at the Flirc GUI (Flirc v1.0.0-beta) but from what I can tell there is nothing I need to do there since the keys are already paired - but how are they mapped? There is probably something obvious I am missing and will be happy if someone points it out to me since I am new to XBMC as well as Flirc and Raspberry Pi. Thanks, Cindy

Hey All, I've read a bunch of older threads for this problem and tried the "solutions" they mentioned without any success. I have a Flirc connected directly to a raspberry pi, and I'm controlling it with a Harmony One. I had no problems setting this up using the Flirc XBMC Profile in the harmony software. Everything worked great for 2 days, no issues at all. No double characters, play and pause worked correctly. Today when I came home I was using it, started a video and paused it and noticed it seemed to pause/play really quickly. Then realized it was sending every button press very quickly. I tried the troubleshooting options in the harmony software and adjusted it to 0. The problem still persists. Has anyone found a solution? I've recorded a video of this here: https://onedrive.live.com/redir?resid=5C92638C7D70FFCA!986&authkey=!AKW5-zehJpIA5iU&ithint=video%2c.mp4

Hi Everyone, Here is my gear! thanks ;) Moutaz

So my flirc arrived in the mail today and I'm having an issue with it. Repeated key response is unacceptably slow and if I push a button on my remote thrice in quick succession it skips 9-12 menu entries. I've gone through a few dozen hopelessly outdated forum threads hoping to find a solution with no luck. I've fiddled with the repeat settings and interkey delays with no appreciable difference. If I abandon the flirc entirely and use the generic IR receiver I have everything works fine perfectly, unfortunately the number of keys I'm able to set with it are very limited due to the receiver not being RC6 compliant. I'm using firmware 2.3 and have the "flirc xbmc" device added in the harmony software. Any help would be much appreciated.

Hello, I have a Logitech K700 keyboard (from my Logitech Revue Google TV) that I am going to be using as my keyboard/mouse for my new HTPC. There is a thread on the Autohotkey forums here that uses custom scripts with Autohotkey to add functionality to the K700 keyboard. Before I install the software and attempt this custom script, I'm wondering if anyone knows if using Autohotkey on the "real" keyboard will impact my Flirc unit at all? I don't want any conflicts to mess with it. I may interested in using Autohotkey for the Flirc at some point in the future as I work on switching between WMC and either XBMC and MB3, so I want to see if anyone has any experience with this. Thanks!

Hey everyone, I just ordered my FLIRC two days ago and am still waiting for it to arrive in my mail box. Because I can't actually set up my FLIRC yet, I've just been reading various threads involving XBMC (which I plan on using with FLIRC) but very little on Netflix at all. I have recently experimented with the NetfliXBMC addon for XBMC but found that it's not extremely reliable and doesn't really work as seamlessly as I'd like. I have read elsewhere that there was/is some Netflix addon for Windows Media Center, but I have not managed to actually get it installed as the installation keeps failing. Anyways, what do you guys recommend as the best way to control Netflix with a remote? I'm using a Windows 7 64-bit install running XBMC and Chrome as my Netflix viewer currently, because I need the MediaHint addon to remove geoblocking. Thanks, Brutick :)