Search the Community

I guess this may not be an issue that FLIRC can help with...seems I need to add a custom Command to the FLIRC device in my Harmony One setup. I have an older remote. It does seem that the newer software might provide a way to add custom Commands, but I'm not seeing it in the software I have. Maybe I can upgrade the software. If I'm on the right track, please let me know....but it does seem that this would be solved if a Home or Main Menu command pre-existed with the FLIRC (XMBC) profile. Thanks.

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

I have not been able to configure this with the Flirc yet. I can only confirm that "browser_back" is the correct key. I've been trying to get the Flirc command line utility under Ubuntu to work, but it doesn't seem to be working. That is, I can't seem to get the command line utility to work with any key, not just "browser_back". As far as I can see, the command line utility is required for learning browser_back. I will try this again under Windows. I just haven't had the chance yet, as things have been a little busy lately. If it works, I will report back here.

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.

Hi, EDIT: I did some additional research and it seems that MR400Q is distributed with LG Google TV models - not the classic Smart TV ones. If you have a Google TV model then it probably won't work the way I've described. I don't know anything about LG Google TV models so I don't even know if LG implemented the universal remote function in it or not. I have MR400 model, but I think that besides full keyboard on the back of MR400Q model both models work in the same way. The LG Magic remotes work by connecting to TV using Bluetooth. All commands except power button (which is sent using IR diode in the remote) are sent over Bluetooth. Flirc can only receive IR signals. Fortunately LG has added an ability to their TVs that allows to control other devices using Magic remotes (and only Magic, standard remotes don't have this ability). The way LG implemented this function is really smart. The remote itself doesn't know anything about other devices. It is all implemented in the TV's firmware. When you are in the universal remote mode and press some button the command is still sent using Bluetooth to the TV. The TV knows that it is in universal remote mode and knows what device is selected and what IR code should be sent. It sends this info back into the Magic remote using Bluetooth and the remote blasts the IR signal using its own IR diode. You need to set it up using TV input source menu. I have all the menus in my language so I don't know how exactly those menus are called in English so you need to try and guess what I mean if it's not exact name of the menu or function. 1. Go into Input source selection menu. 2. Press yellow button: "Universal remote setup". 3. Press "Start" on the screen and you should be presented with device type selection (there may be other screens between, just skip them). (below points are based on my research - I've spent hours finding a device which would allow me to use as much buttons as the remote allows - this is based on the MR400 model which doesn't have many buttons to begin with - you can use this config if you don't have home cinema or soundbar or some other device from LG besides TV) 4. Select Home Cinema. 5. Select Input on which you have your computer with Flirc connected (like HDMI1 etc). 6. Select LG. 7. Select Remote model 1. 8. Finish the setup. If you have some other LG hardware (like soundbar or some other speaker system or home cinema) then you probably need to select other device type or manufacturer. I didn't have much success with other device types than Home cinema so my best bet is to still use Home cinema and just select different manufacturer or remote model. I actually have LG Soundbar but fortunately the keys I have on the Magic remote didn't interfere with Soundbar much. The Magic remote will automatically switch modes depending on which input is your TV. When it's on inputs other than the one you have your computer on it will act like a normal TV remote. But when you switch to the input you configured the universal remote on then it will start sending IR signals for some keys (depending on device selected during setup). In addition to physical buttons on the remote you also have an on screen remote where you can press additional buttons not available on the remote itself. Because the way this whole function works (I've described it in the beginning of this post) by pressing the button on on screen remote the remote still sends proper IR signal. Now there are some restrictions with this mode: - For universal remote mode to be active the TV must be turned on and correct input must be selected. - Physical power button on the remote always sends the power on/off command to the TV itself - if you want to send a power on/off command to the Flirc then you need to use on screen remote when in universal remote mode. The TV also gives you the ability to send Power On command when you switch to the input you have your remote configured on and there is no signal. The dialog will pop up with Power On button on it. When you press it, the remote will send proper IR power on signal. - Some keys are always mapped to the TV itself and you can't use them with other devices. On my MR400 those are buttons are: Smart, 3D, [1][2][3]/Q.MENU (this button activates on screen remote), Mute and Volume buttons. Those are always invoking actions directly on the TV. Of course MR400Q has more buttons so I can't tell you how it will behave. - The scroll doesn't work in universal remote mode - at least I couldn't find a device which maps it somehow. - The gesture control does nothing for the universal remote. When you activate gesture control the cursor on the TV appears and you are back in TV remote mode - it goes back to universal remote mode when the cursor disappears. I don't know how will the keyboard part of the remote behave but I suspect that it won't work in universal remote mode or it will invoke functions directly in the TV. If you have some additional questions then don't hesitate to ask. I'll try to answer then the best I can.

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

Just to followup and confirm. I just tried the media play/pause/FF/RW buttons on my flirc using this chart and the record_api command to set the keys. Rewind puts the Nexus player to sleep Fast forward did nothing Play toggled play and pause Pause did nothing Stop did nothing I tried all the keys while playing back media just to verify. I'm going to update my post in the other thread just so no one gets confused.

What exactly do you need help with? The Harmony profile provided from Flirc includes a Poweroff command that sends the XBMC the keyboard command Ctrl-F12. Since that keyboard command does absolutely nothing I'm simply telling the XMBC to respond to that keyboard command by suspending through a custom keymap profile. This is how to ssh into openelec: http://wiki.openelec.tv/index.php/OpenELEC_FAQ#SSH This tells you everything you need to know about keymapping in xbmc: http://kodi.wiki/view/Keymap

Hello, I have the same "Keys stuck" problem that many others seem to have recently. As in this thread: I'm using openelec on an x86 computer and I'm using a Samsung TV remote to control it. I am a firmware programmer with experience in USB HID devices and I've studied this problem with my USB analyzer. I believe I understand the problem. First a bit of background: The Flirc firmware enumerates as a USB HID keyboard which sends keypresses. It also detects IR signals from remotes. IR remotes use codes that repeat when a button is held down, so filtering is necessary to prevent unwanted repetition of a keypress. Keyboards also have key repeat rates, but it is implemented differently than IR remotes. USB Keyboards use key on and key off messages. It is up to the OS or application to fascilitate key repeat. The problem is that this key repeat delay varies from O/S to O/S, and in some cases from program to program, which is why the inter-key delay settings don't work the same for everyone. If you press and hold down a key on your keyboard you'll see the keypress immediately register, then a short delay, then it will begin to repeat that key. Another thing that complicates things is that IR signals takes some time to actually be received and the IR remote repeat rate varies from remote to remote.. I'm assuming that the vast majority of remotes should take less than 50mS to send a key press, hence my default InterButtonDelay value below. I've captured the USB traffic with several different inter-key delay settings in the Flirc v3.1 firmware. It appears that the inter-key delay setting is actually changing 2 separate things with one delay. I think this is where the trouble lies. Both the IR command ignore delay AND the key down time seem to be modified by this one setting. If the delay is set too low, then the IR repeat rate becomes the dominant factor and you get multiple key presses because of the IR remote sending too quickly (which is unavoidable). If the delay is set high, then the key down time starts becoming long enough that the O/S thinks the key is being held down, so it starts repeating the key. The key down time shouldn't be increased simply because the IR button delay time is increased. When changing both of these, it becomes a balancing act between the two indpendent problems. Most people don't realize that setting the delay to 6 isn't actually the safest choice and 0 doesn't work well either. It isn't obvious why this would be the case though. You really have to find the happy medium that works best. I found a setting of 5 worked best for me, but it still wasn't working completely perfectly. I propose a different implementation of the inter-key delay that works by detecting how long the button has been released and sending the key up message as soon as it has been detected as released. Expected behavior: *If the button is pressed rapidly, as long as there is at least a 50mS pause between presses (button press 20 times per second should be a reasonable limit), then all presses should be recognized as individual presses and releases. *If the button is held down, as long as it is not released for more than 50mS, then the key released event will not be fired and the OS will eventually start repeating the key as expected. *If two different buttons are pressed within 50mS of each other, then the first will be pressed briefly and released as the next is pressed. (This should yield expected behavior) I implemented the keyboard sending code as a queue to guarantee that if 2 commands are needed back to back before the next USB EP1 IN request, then both are guaranteed to be done. This could be implemented a few different ways. A queue is just the mechanism I used. Initialization: ButtonPressed = false; ButtonReleasedTime = 0; InterButtonDelay = 50; //default value in milliseconds.. should be configurable. (this is the time the button is RELEASED, not held...) Upon receiving a recognized IR command (ReceivedKeyCode): if (!ButtonPressed) { QueueSendKeyboardCode(ReceivedKeyCode); //new button pressed: ButtonReleasedTime = 0; //Keep track of how long the button has been released ButtonPressed = true; ButtonPressKeyCode = ReceivedKeyCode; } else { //a button was pressed and we are waiting the minimum release time of that button: if (ButtonPressKeyCode == ReceivedKeyCode) { //Same button was pressed: ButtonReleasedTime = 0; //restart the release timer } else { //different button pressed before the release timeout. Switch buttons QueueSendRelease(); //release previously held button QueueSendKeyboardCode(ReceivedKeyCode); //send new button //new button pressed: ButtonReleasedTime = 0; ButtonPressed = true; ButtonPressKeyCode = ReceivedKeyCode; } } Timer routine (every millisecond - should be thread safe... should be non-interrupt context: same as above code): if (ButtonPressed) { ButtonReleasedTime++; if (ButtonReleasedTime > InterButtonDelay) { QueueSendReleased(); ButtonPressed = false; } } By the way, I understand that this is a closed source project, but if you'd allow me access to the source I'd be happy to work on the project. I don't have direct experience with Atmel chips, but I have worked with Microchip and ST, and to be honest it doesn't make all that much difference once you have the basic framework in place. I've attached one of the USB captures I made that I exported to excel format to analyze what was going on. Joe flic brief presses several repeats interkeydelay is 3.zip

Alt+esc got the home button!! Although I'm on a mac right now and the command+esc and command+space didn't do home/search. I can try again later from a windows machine but I assume they send the same keys.

You should not be able to record the same key again without deleting it before recording again. My last suggestion is for you to try all codes from 1 to 255 (second number still 102). I know that this may take some time. Maybe save your current config from the GUI or command line, then erase Flirc and start recording starting from code 1 102 and increment for all available buttons on the remote (remember which code for which button). Then try all the buttons with Android TV and if you don't find the Home button then erase again and start from next code after the one you recorded in previous round.

Normally the record_api command in flirc_util.exe allows you to record a key with a modifier. The first number is a combination of modifiers (left/right shift/control/alt/windows) and the second is a USB HID key code of the key. There is a special case when the second number is 102. This tells Flirc to send a key code defined by a first number from different HID usage table. The code 154 then means a Media Select Home button. I'm not sure if this is the correct one so you need to check it yourself. I've described more in this thread:

Same problem also here with same setup. Interkey 0 and noise cancelling helped a bit, but often when pressing up und down the command is issued twice. Latest FW 3.1 running with Fire TV profile.