Search the Community

Let me start out by saying my problem only occurs with a specific remote code which I am trying to use to get more buttons working. Flirc works quite well when I used any other code with my BellTV remote and my fallback is to simply reload a previously saved configuration. However, I would like to get more keys working. Specifically, I want to get all the PVR (DVR) keys to work on this remote. It's similar, if not identical, to Dish remotes. I am using FW1.0 with GUI0.96. The issues also occur with the recent Release Candidates including 1.0.0.3 release hours ago. I'm trying to use the remote code as described but get the issues as mentioned in the subject line when trying to record buttons. Here is a very simple demonstration using the command line: C:\>flirc_util.exe format Formatting Device, please wait... Done! C:\>flirc_util.exe record 1 Press any button on the remote to link it with '1' Error: button already exists It's appears to be random how many buttons I can record before I get that error message. If I try again, I'll be able to record the button. After this, however, the buttons will not be mapped correctly. Pressing 9 will send a 7, for example. I've uploaded the config file from this particular example session. Flashing to new/old firmware and erasing/formating the configuration hasn't helped. I have a second flirc and it exhibits similar behaviour with this remote code. Doug flirc.fcfg

I have been experimenting and it looks like you can manually add new commands to the Harmony Flirc profile just like other Harmony profiles. I was afraid that if a remote button was mapped to a command/key in Flirc using the GUI or CLI that the new configuration would completely override the firmware default mappings that the Harmony profile relies on but it appears to not be the case. I have been able to add new commands/codes to the Harmony Flirc profile from within MyHarmony using the "add a command" function under Devices or Buttons which allows the Harmony to learn new codes from another remote. Then I use the Flirc GUI or CLI to map the new button/code to the key/command I want Flirc to send. An example is that I created a "Wake" command in the Harmony Flirc profile and learned the power on code from another remote to the Harmony. I then went into the Flirc CLI (also was able to repeat with the GUI) and recorded this new Harmony button to the "Wake" key. All the other default commands remain active and the keys command in the CLI just shows the new keys added. I hope this make sense (maybe everyone already new this) because it allows the use of the current Harmony profile to generate the majority of your Harmony commands and you only have to add the missing ones instead of trying to come up with another good base remote profile like the "Panasonic TV" remote etc. Overall I think that there will be less commands that need to be added. I guess basically this is a composite of the two solutions for setting up a Harmony remote. Along with murkyl's post above this appears to open up a whole range of customizing possibilities w/o having to start from complete scratch on the the more basic/common commands. I have not tried to assign a button that is sending an existing/default Harmony profile command/code to a new key/command in the Flirc GUI or CLI (like ContextMenu to key "M" instead of "C") nor have I tried to create a new Harmony command/code and assign it to an already existing default firmaware key/command (like Home to "Back").

patchseven, when you try with the 1.1 beta firmware, you have to enable the feature via the command line utilities (this is not included in the GUI). It worked for my harmony 785.

OK, so I found another way to access the shutdown menu from the skin and I can always manually wake my HTPC by pushing the power button so not a lost cause it just leaves things to complicated for my wife to run unfortunately. Aslo I think the poweroff command in the Flirc profile does not work because I am using Frodo and it looks like this profile is based on Eden and I think the keyboard commands changed with Frodo for this function. I will hope that these features are added eventually and in the meantime consider changing back to the non-Flirc profile method. Besides wake and sleep I would also recommend adding Esc in the future as well. I also wonder if possible now or in the future to combine the built in commands from the Harmony profile with adding additional commands or overriding some commands from the Flirc GUI or command line utility programs.

Is there anyway to get the custom Flirc device/profile for Harmony Remote to be able to wake and sleep the computer with single button presses. I understand that not all possible commands are implemented in the Harmony device profile at this point but it seems given the new firmware with one of its main features being a wake command that this would have been an obvious command to implement in the Harmony profile. Shut down or sleep can be done through XBMC menu selection I guess although that can take several steps depending on what skin you have and may not be possible at all, again depending on the skin setup and the current available Harmony commands. For example I have Openelec with Frodo 12.2 and Transparency skin and the only way I know to shut down or sleep the system is with the "S" key (shutdown or system menu) or Ctrl+end (exit XBMC) both of which are not available in the current profile. As far as waking, again there is no wake command and if I do not implement this feature then with the new firmware any remote key press will wake my system whether programmed into Flirc or not. See my previous post

I'm also having this issue. The new firmware seems to have triggered it. Now I get key repeats constantly and it makes the remote unusable. flirc_util can no longer connect to the flirc either, reporting this error on the issue of any command: Warning: cannot open USB devicedevice disconnected, can't run command Strange because the OS seems to pick it up fine. From dmesg: usb 1-1.3: new low-speed USB device number 7 using dwc_otg usb 1-1.3: New USB device found, idVendor=20a0, idProduct=0001 usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 1-1.3: Product: flirc usb 1-1.3: Manufacturer: flirc.tv input: flirc.tv flirc as /devices/platform/bcm2708_usb/usb1/1-1/1-1.3/1-1.3:1.0/input/input4hid-generic 0003:20A0:0001.0005: input,hidraw0: USB HID v1.01 Keyboard [flirc.tv flirc] on usb-bcm2708_usb-1.3/input0 This is on the raspberry pi also

Awesome -- thanks so much Chris! for the super-fast response! I was able to get everything working very easily using the Harmony profile. Just one note: It would be really great (if it's even possible) if there were some extra "custom" commands added to the Harmony profile. So, for instance, if I wanted to create a button to launch my Video listings directly: in my Harmony setup I could map one of these custom commands (say, "Custom1" or something) to my button, then use the Flirc software to map that button to the Ctrl-E keyboard shortcut. Otherwise I'll have to either 1) add an additional device to my Harmony and map a random button from that device (but I'm already maxed out because Logitech insists on arbitrarily limiting me to 5 devices on my 650); or 2) learn a random command from another remote I'm not using, and map that. Unless there's some easier way to do this that I'm completely missing? Is there somewhere I can file some sort of feature request for something like this? Thanks again!

Hi, I tried to program a Windows MCE remote. After learning i.e. button up, I noticed that only every second remote button press was recognized as UP. So I programmed the button again. That did the trick. I then changed to flirc_utility and did a format command. Then I recorded UP with the command utility and listed the result via KEYS command. It says HASH B47CA919 up. Then I recorded same button UP again and did another listing. No there are 2 commands: B47CA919 up F3B14639 up Same remote, same button, two hashes. I think that is the reason for my initial problem that only every second button press worked. But is this a normal bevahiour? Why are there 2 hashes for the same key recognized? Another MCE remote ended up with the same result. Bug or feature? Regards Knilch P.S.: I use the latest development RC2 package.

I just wanted to add that I have the exact same problem, except I'm on a Windows machine. Sometimes flirc goes into a loop and sends the same command over and over. I have checked this with applications such as notepad, where I can see all the repeats.

I realise I'm at risk here, because this topic may sound a lot like the 'delay' and 'repeating keys' issues. However, I really think this is different. And I hope there's help out there! I often (have not yet found the trigger that causes this) have the following: I press my Harmony remote button with an XBMC (Flirc in combination with RaspBMC) command, and then the XBMC goes crazy because it starts receiving repeated commands from the Flirc. I have checked the harmony: it is NOT sending out multiple commands (you can see the IR signal when looking at it through an iPhone camera). If during these repeated commands I simply pull the flirc out of the raspberry pi, then the repeating stops. I can then control the raspberry pi with the XBMC app. So this suggests it really is the Flirc sending repeated commands to the Raspberry pi, even though it is NOT receiving any repeated commands from the remote (harmony). Does anybody recognize this and better yet: is there a solution? thanks for the help in advance!!

Update: I got flirc to work. Can someone please help me by getting the fw_repeat.bin file please. I can't seem to download it from here. Are there any other suggestions. When I click on right or left, It works sometimes and then keeps the button pressed and move lots of pointers forward. Is there any other suggestion guys? At this moment. So far the best solution found till date is the PS3 Bluetooth remote. It works very well but has its own minor if's and buts. Pros of the PS3 Blumote. Works perfectly all the time and rage is not an issue. A simple minor click will make it work. All color buttons work perfectly. The blumote software is very customizable. Cons of the PS3 Blumote. You have to use the hibernate settings to conserve battery. IF the remote is not set to hibernate then you will have to replace the batteries once in every 4 days. If in hibernate mode, when you press a key and the remote is hibernated, for example you are watching a movie and press pause and the remote is hibernated, it will take about 2 seconds to send the pause command as it has to wake up the remote. The above two points are the only cons but with the flirc, I feel there are too many if's and buts to make it work perfectly. For example. Pros of Flirc. Infra Red so batteries wont die. You can use your universal remote instead of an alternate PS3 remote. Cons. Flaky in a sense, flirc will learn the remote but not play back well. Constant additional key presses. Has an external object sticking out. If you use a bluletooth keyboard and mouse then the ps3blulmote is a total clean solution vs a flirc. Having said that I really like the possibility of using my universal remote vs an alternate ps3 remote. Hope someone can help out.

Yes I used the up down left right in the learner to make it learn and the software showed that it has learnt. In the command line utility it also shows that the keys have been programmed but they don't work. I test the up down left right in xbmc and also on notepad to see if it works and it does not.

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.