Search the Community

I am using the FireTV Controller View setting in the Flirc Config software. I am not sure what you mean by the XBMC buttons don't match? If the ParentFolder command is not the right one to send from the Harmony then can you please tell me what is?

With Harmony remotes, I'm 99.6364% sure you want a low value inter-key delay to keep the IR command from repeating. Try setting it to the lowest or second to lowest number. -Randy

Increasing the Interkey Delay to 5 or 6 actually made the problem worse and now other keys like Up etc. are sending the command twice! Any other way to solve this?

I have a Harmony 525 and have set it up using the Flirc -> XBMC profile in the Harmony Software and everything works ok except for the remote seems to be sending 2 commands on occasion when it should only send 1 particularly for the Back command! I have tried the fix that another poster has mentioned here: https://flirc.zendesk.com/hc/en-us/articles/202819236 and reduced the setting to 0 but it does not seem to make any difference... Are there any other fixes for this? Also might the Inter Key Delay in the Flirc Software under Advanced help with this as well?

The MCE remote and its provided receiver will wake the Fire. The button in the extreme lower right that looks like a PC and is labeled "Desktop." In theory though, any key should wake it up. Haven't found anything that will put it to sleep reliably yet. Which is kind of surprising since the Fire has a built-in sleep command.

I think just about any input wakes it and the standard sleep works to shut it down. I have the xbmc power off command using the harmony profile and it shuts the firetv down (sleep) to wake you could record home or menu etc.

I just got in a Flirc from Amazon, and I'm trying to set it up to use my FiOS remote. Everything was working perfectly for about 5 minutes, until I made the dumb mistake of updating the firmware. Now, the unit will not program any buttons correctly. It seems to be clearing the configuration correctly, because the command line says 0 buttons programmed. However, when trying to record buttons using the GUI, it doesn't work. It will record the first button correctly (up), but when moving onto the next (left), it says "Button already exists". No matter how many times I clear the configuration, it still says the same thing. I can manually erase the buttons, but even when doing that, the buttons all seem to have the same action. If I program up first, everything goes up. It seems like the firmware update messed up the Flirc, because I can't think of anything else that I did between it working and it not working. Please help.

I am curious about getting an "exact" list of how you set this up. If I set it up in Harmony as FLIRC/XBMC, I do not get enough buttons (no home, menu, not sure what else). So, I thought, this thing is programmable, and Microsoft/Media Center PC will have all the buttons, so I programmed the Harmony as WMC PC. Sure enough, I have all the buttons and they all work except for the issue described above - pushing the up or down key registers as a double-press. Oh, this is on version 3.4 RC2 EDIT: Got it working! I went back to FLIRC/XBMC in Harmony, then renamed this device Amazon Fire TV. Then, for the screen buttons I assigned Red to Home, and Green to Menu. Then I assigned the Harmony's Exit and Menu button to Red, and the Guide buttons to Green. (is this confusing yet?) Now, all the buttons work like I want, the buttons assigned on the screen are labeled for WAF (wife acceptance factor), and the Guide, Exit, and Menu buttons all make sense to me. Of course you can assign them any way you want, but this worked for me. Also, I customized the activity to send a "Home" (Red with my mapping) command to the AFTV at the tail of the macro, so that it would power up and be at the home screen.

That's the latest RPM I could find too. It's old and I got the same errors you did. Here's what I did to create a working (and current) version: Download the latest DEB file that matches your architecture here: http://apt.flirc.tv/arch. For example, for 64 bit at this time that's http://apt.flirc.tv/arch/x64/binary/flirc_1.3.2-1_amd64.deb. Convert it to an RPM with alien: sudo alien -r flirc_1.3.2-1_amd64.deb Remove the unnecessary and conflicting entries: rpmrebuild -p --change-spec-files="grep -i flirc" flirc-1.3.2-2.x86_64.rpm That command will create a new rpm that should install cleanly and seems to work fine for me. I'm on Fedora 21 64-bit.

Oh I got it!!! I used an old xtreamer remote. Teached the Flirc the FF IR Code and bind it to key 'F' at the keyboard profile. Then the same for Rewind. All I have to do is teach the Logitech harmony remote flirc profile the xtreamer remote IR codes (as new commands) and that's it. WORKS LIKE A A CHARM!!! The potential of this small thing is amazing! I can write a powershell script and run it with IR command!!!

I'm trying to install my new Flirc on a Zotac AD03 running Mythbuntu 12.04. I got the sources list modified and the apt-get-update and apt-get install flirc work fine and the program shows up in Applications -> Accessoreis -> Flirc. When I click on it it does not launch. The wait icon is present for a few seconds before the normal mouse pointer returns. Just on a chance I installed ia32-libs, nothing. I found a command line approach but I can't find a firmware version that doesn't return a 404 when I attempt a wget http://downloads.flirc.tv/fw/fw_x.x.bin. How do I get firmware into the device? mike

irw is a Linux command line function which directs input from the USB port to the terminal screen. I happen to be using RC-6 and hopefully won't need to change. If I am reading you correctly, I need to make sure that each button has all its signals set to the same key combination and I should be ok, correct? Also, once I do that I can save it to file and program other Flircs to be identical simply by loading that configuration, correct? mike

I also have the Flirc/harmony/ouya and this exact problem has happened to me.....all the sudden the flirc has become unresponsive. I had been using the flirc just fine for the past while on firmware 2.4 and only recently upgraded to the latest (3.3) to see if I figure out how to wake my ouya from sleep. Big mistake. I wish I had of just left it alone. My pc is able to recognize the flirc ...I'm able to record buttons through the GUI but it refuses to command them upon press. I've tried the flirc using different remotes on my ps3, pc, and my ouya each time producing with the same result...unresponsive. I left it for about an hour and suddenly it worked for bout 5 minute then shit the bed again. Is there a way to downgrade my firmware back to v2.4.?

Not sure if this is what you're asking but flirc_util stuff can be found here: https://flirc.zendesk.com/hc/en-us/articles/203688495-Using-Command-Line-with-Flirc

You don't load the config into GUI. It is loaded directly into Flirc. So you just need to connect next Flirc and select Load configuration from menu or use flirc_util loadconfig command and that's all. You don't need to do anything else.

And here is the Command line documentation in the knowledge base (freshly added :) ): https://flirc.zendesk.com/hc/en-us/articles/203688495

:( :( :( P.S. Jason, I recall reading you had deliberatly left command line ...err... commands out of the GUI. I didn't catch why, but maybe if you put them under and "ADVANCED" tab?

The USB connector on mine is also slightly bent so don't worry. Also the status command shows this exact message for me too - I think only Jason knows why :). I'm just helping on the forum so I don't know what return path/method you should take. I think you could try writing to Jason directly (via PM or E-mail - address is on his profile page) or wait until he responds here.

In the flirc gui, go to 'controllers' menu and choose 'full keyboard'. You can add any key from there, for example, you would just click on F4 and then press the button on the remote that you want to send the F4 command.

If I could get to the GUI I would do as you suggest. When I said the program does not launch I meant the GUI. I click on Flirc in Accessories and nothing happens. I don't mind using command line if I knew how to find the firmware version. fw_1.0.bin is no longer available (404 error). mike

hi, i've got a harmony 700. i'm seeing repeated keypresses being emitted at the slightest touch of (especially) the red/green/yellow/blue buttons. i've programmed these particular keys to be alt+z, alt+x, alt+c, alt+v. even after setting repeats to zero (in harmony), setting inter-key delay to 1000ms on the harmony, and setting inter-key delay to 7 on the flirc, i am still having this issue. what is very odd to me is that holding a key will emit about 10 repeats a second. if i understand what inter-key delay is supposed to do, a setting of 1000ms should only emit 1 keypress a second at a maximum. but i'm still seeing about 10/s emitted. so it seems like this setting is being ignored. does that sound right? strangely, although regular keys also repeat quickly, as if they ignore inter-key delay, they don't emit multiple keypress events at the slightest touch like the ones configured with record_api do. another thing i've noticed is that since recording them with flirc_util record_api, i can't delete them (they don't appear in the output of 'settings'), and i can't re-record them using the standard 'record' command (it says key already in use). so i'm unable to test if the hair-trigger nature of the red/green/yellow/red keys is a result of using record_api, or there is something else going on (at least without formatting and losing *all* of my settings). in conclusion, either i'm misunderstanding inter-key delay in thinking that it will rate-limit key repeats proportional to the specified delay, or inter-key delay is horribly broken somewhere. and, i am unable to re-record keys as non-modifier keys that were previously recorded with record_api, nor am i able to delete them using flirc_util. p.s. this is on firmware 3.0 / flirc_util 1.2.7

yes, I need to update my command utility so you can delete them by index, they don't show up, however, you can do flirc_util delete, and then hit the button on your remote, that should do it. Yes, sounds like harmony is ignoring it. It wouldn't be the first time. On my harmony, If I press the button twice in 20ms, it will insert a delay of 1s in between them, always. So if I hit the key 10 times, it takes ten f&*$@#'n seconds to get to my tv.

yeah still working on it, but just open up a command prompt, and type: sudo Flirc It runs as super user, I just can't figure out why it wont run without elevated privileges

Hi, thanks for the info. OK, when I save it using the command line, it automatically saves it with the correct extension ie if I type in flirc_util saveconfig ~/Desktop/my_flirc_config it saves the config file as "my_flirc_config.fcfg" The good news is that this file is now automatically listed by the GUI, & by manually renaming the other backup configs that I've done, they now show up too. I haven't actually loaded one of the files though, as my flirc is doing nearly everything that I need it to currently.

Hey guys, finally got time to test RC2 myself. My findings, all on Windows: 1.) Installed Gui 1.3, started Gui, plugged in Flirc, gets recognised as FW 3.1, Guis asks to upgrade to 3.3, Gui upgrades, recognises Flirc as FW 3.3, down in the middel of the GUI it says "Unsupported firmware, try upgrading". Tried closing Gui, unpluggins Flirc and redo the process multiple times. Asks me for the eighth time now after reopeneing the Gui to upgrade firmware. Flirc_Util says on status: Last upgrade attempt: Error Ignoring the upgrade message and just clear config and go ahead learning some keys works flawless for me. Some more testing needed though. 2.) Forcing FW upgrade through the menus says "Your firmware version is: 3,3 The latest firmware version is: 3.2" Sound like a typo. After doing the force upgrade, flirc_util still says error on last upgrade attempt. GUI says "Firmware successfully upgraded". 3.) While trying to use the 334kb sized flirc_util.exe from the extracted zip (release/windows), it cries about missing libusb-1.0.dll. Using flirc_util.exe (505kb) that gets installed by the installer works fine. Still, typing flirc_util without its .exe extension in a command prompt just does not work, you HAVE to write "flirc_util.exe". Not an expetected behavior. So yeah, learning keys obviously works, but some messages are very confusing. That's all for now. Cheers guys and thanks to Jason for fighting bugs for us. :-D