Search the Community

A Harmony would take care of this problem. Due to the fact you have activities as well as individual devices programmed in, so when it's sending a command to your TV only your TV will get the command. Flirc will have it's own separate device and commands.

Oh, sorry, it's in the Harmony setup. The remote by default repeats an IR send up to 3 times (depending on the receiving device), to make sure the command is received. For the Flirc, it should be set to repeat once, but if you've configured the Flirc as another device it could be more. I've found the Flirc doesn't need a repeat, and setting repeats to zero has reduced my accidental double-presses. Repeats The Repeats are the number of times the remote repeats a command for a device to properly respond to the command. For instance, many devices need longer or shorter command repetitions to respond properly. Example: Any time I press channel up, my Digital Set Top Box skips two channels at a time. To adjust the Repeats, from the Harmony Remote Software: Click 1. Troubleshoot at the top of the Harmony Remote Software window. 2. Select the device you want to adjust repeats for, and click Next. 3. Select Device responds to some commands either too many times or only occasionally and click Next 4. Adjust the repeats by selecting a higher or lower number, and click 5. SAVE

Hi all, new here. Got my flirc last night & seems to work quite well with my Harmony remote, much better than the crappy IR receiver built in my laptop. Have a couple issues with my PC sleeping by itself and also randomly waking up, stupid thing woke me up this morning a few time hearing the fan spin up haha, just had to turn it off. Was hoping someone can help, I'll explain how i've set it up first. I am running Win 8 x64, XBMC Frodo, Harmony 650 remote, Flirc beta rc4, using the Harmony flirc xbmc profile. It looks like I've done something similar to here. In the Harmony software I've setup two custom Additional Buttons (the ones you see on the little remote screen) for my XBMC Activity, called them 'XBMC On' and 'XBMC Off'. I mapped these two buttons to use the Yellow and Blue buttons on my Samsung TV since I already had this device in my Harmony config and these buttons were unused. I then went over to my XBMC machine and opened up the Flirc GUI and programmed my new custom buttons. My 'XBMC On' button sends the 'Wake' key from the Full Keyboard controller, and my 'XBMC Off' button sends the Shutdown key from the XBMC controller (I've set the Shutdown command in XBMC to Sleep). These two buttons work perfectly, however I am having a problem where if I leave my PC idle for a few minutes or so it will go to sleep, and even worse the PC will randomly wake itself up later on. I'm not too sure if it's Flirc, my remote, or Windows causing this. I had the suspend_detect option enabled in the Flirc GUI, could this be causing it? One thing I didn't check was maybe turning off my network adapter from allowing it to wake my PC (I think you can do that?). Anyone have any other ideas? I'm at work at the moment so I'll have to play around with it a bit again tonight. Thanks in advance for any help (and sorry for the long post) :)

Hmm having problems as when I try to map a new command to the remote it says no more space for new buttons for some reason. Can delete the existing mapping but that doesn't help for some reason - should be so straightforward but it doesn't like something! Appreciate any advice

Hmm.. Tried to learn the esc command - but the Flirc software is not recognising that I have pressed a key on the remote? Very odd :-(

Am very happy with the way the flirc works with my Harmony 525 using the latest beta firmware. What button command do I use to get back to the XBMC main page (where you select films/video/settings etc)? Or something equivalent to pressing escape on the keyboard?

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.

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.

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 would like to see a flirc that would also have an IR emitter, and the right software to become an universal remote command translator. In fact we can do this with USB-UIRT but I like the idea behind flirc that does not need any programming expertise to associate IR signals it receives to keyboard commands. The idea would be to record IR signals from two different remotes and make FLIRC send the IR signal of remote #2 when it receives IR signal of remote #1. This way we could use remotes like the PS3 V2 that can command TV from various makers but is limited to Sony for audio equipment control. I'm sure it could prove very useful in many other scenarios to unify multiple equipment control over a single remote

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...