Search the Community

I just got my Flirc and set it up using the Flirc Profile in the Logitech Harmony One Software for Harmony One. Everything is working great! Even the context and the info menu which was a huge issue for me! I need to configure three more command but I'm not sure how to do them. - Launch XBMC - Close XBMC - Shutdown PC How do I go about doing them? I don't see many updates on this topic since the profile was released in the summer . I've tried using the keyboard short cuts but I'm getting errors left and right of the buttons already being used and such, yet I can't select them in the Harmony software. Any help would be greatly appreciated! This would make my HTPC complete.

I see the conundrum. If you could hold the whole keymap in read/write memory, then I'd say just send the whole thing based on what the user says he wants in the GUI. If you can't do that because it won't fit, then I can see how you came to the conclusion that you did. I do think that an error message that essentially says "Can't delete that key because it's built-in, but it doesn't consume space in the 160 key 'user area'" would be good. It's the faux success that threw me off, not that I really wanted to delete the "1" key in my example. i would prefer Option 2 because I can see the benefit in not having to learn every single command for the common use case, but would also like the opportunity to remap those keys if I want. XBMC is very flexible at keymapping on the app side, so it would be nice to have that same flexibility in flirc. Just make it clear what's being done for the user and what they need to do if they don't like it. As far as distributing flirc_util, I was suggesting that it live somewhere in the flirc.app package, not in the DMG. Like in the "Resources" directory. If the update mechanism updates the entire App package, then you'd get a new one along with the new GUI. You may have to stick it in there manually after you build the app (or maybe not?), but that would keep the GUI and flirc_util app together. Rob

Ah, that makes sense. Yes, I'm using the Harmony profile. If it isn't possible, I'd expect the delete to fail with an appropriate error message :). Maybe you could send a pre-configured set of keys if the user selects it in the GUI, rather than having them live forever in the device. That way, you could start with a known set and change it without wasting space. I'd prefer to be in complete control over what's in the device, but I don't really care as long as it doesn't prevent me from doing something. Incidentally, this helps me understand why sometimes, inexplicably it would work. I must have tried different keys. As far as the command line app, can it just live in the App package for the GUI? Maybe impossible, but that would keep them together. I don't immediately see your email address on the site (forgive me if it's obvious), so I'll submit another support request and that'll have my email address in it. Thanks, Rob

Thanks, Jason. I have my Flirc, but not the remote control that I used to program it (I'm traveling). Rather than mess it up more than it is, I'd prefer to wait until I get home to experiment with it. It will be really helpful to have the command line version of the 1.07 OS X app - I'm usually more confident in the results that I get from the command line than I am with a GUI that's trying to outsmart me :) Rob

Sorry you are having trouble... I don't have a Raspberry Pi to test, so I don't know how much I can do personally, but does the Flirc GUI and command line utility work on your system? Perhaps knowing whether those are working and it's only the XBMC plugin that's failing, or if other elements are also having trouble might make it easier for Jason to narrow down what's missing on your system that is already present on other Linux systems. The Flirc Add-on has been really reliable on my XBMC box, which is an Ubuntu 12.0.4 system. Also, what version of the Flirc software and firmware are you running? And can you pastebin an XBMC log that includes the Flirc Add-on failure? Do you see a failed script error message in XBMC or does it only refuse to connect to your Flirc and otherwise run without error? Thanks!

Hi all- I'm trying to record just the Windows button- just the basic press of the Windows key (between Ctrl+Alt)... It doesn't seem to be listed in the command line record options and the GUI seems to only want me to be able to use it for shortcuts like Windows+R, etc... What am I missing?

Found this link: http://askubuntu.com/questions/107230/what-happened-to-the-ia32-libs-package I was able to get a list of the needed shared libraries using the "readelf" command and started installing some. But it's time consuming to find the package name that provides the desired shared library, and I wonder if the ABIs will be compatible. So I'll manage with flirc_util for now.

Just want to say "Me too". I'm running Mythbuntu 13.10 saucy x86_64, upgraded from Mythbuntu precise 12.04. I am logged in as root when I try to execute ./Flirc, but I get the following error: -su: ./Flirc: No such file or directory But the file is there and if I type: # file ./Flirc I get: ./Flirc: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.0.0, not stripped But if I try to check what shared libraries it needs with the command: # ldd ./Flirc I get: not a dynamic executable I don't have any 32 bit executables to compare to, but running "file" on the typical 64 bit executable says: <filename>: : ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.24, BuildID[sha1]=<long hash code>, stripped Perhaps executables built against GNU/Linux 2.0.0 cannot run on distros using GNU/Linux 2.6.24? FWIW, I just downloaded the zip file 1.0.6 last night, which was dated Dec 18 01:57. flirc_util works, for the most part, more details in a separate thread. HTH

Correct. You have to map a command to the virtual button using myharmony then sync it. Otherwise the button won't send anything when pressed. I haven't checked in on the status of the Flirc harmony profile but last time I checked it didn't allow custom (almost 'placeholder') buttons that the user could map a function to (as existing functions are premapped in flirc firmware)

I never respond when I see posts about Harmony profiles because I don't have one, but I guess I don't see what's stopping you from mapping any unmapped button on your Harmony to the ESC key using the full keyboard view in the Flirc GUI, or the flirc utility's record function from a command line. Does the Harmony not send IR codes on undefined buttons or something?

Hey Jason, I tried pasting what you put above into Terminal but it didn't work - I just got 'No such file or directory' returned I'm not familiar with Unix commands but Googled this command 'open -a /Applications/Flirc.app/Contents/MacOS/Flirc' and used that instead I'm afraid I got the same looking log come up in a window titled 'Flirc quit unexpectedly' The log is at the following link http://pastebin.com/FktWuX42

Greetings. I can now confirm that the Microsoft DVD Remote (original XBOX) won't work properly thanks to the older posts that mentioned it It is very skiddish and most keys will not program at all or if they do they are erratic and seem confused (sends two or more commands and not even the correct key pressed). :( I bought 2 flircs (and would have needed two more) but since this remote doesn't work correctly with flirc, isn't as cool as I hoped. I guess it's my bad for not searching the forums before buying a product that touts "Any Remote". Should have an * on that tag line. Sorry. However, it has the same basic issue using Scientific Atlanta Explorer remotes (model 8300hd and 4250HD ) which is a second strike. :( :( I can get it to work on the tv remotes I have with no problem, but where I need them the most, the controllers lack media control buttons so they are useless with the WAF factor as well. Bummer really. Strike :( :( :( I really thought though my flircs were defective since I tried to program on (2) Win 7 64 PCs and an Ubunutu 32 bit box using 6 different remotes (albeit that 3 were the Xbox, 2 were the 4250HD and 1 was the 8300HDs). I tried beta firmware, Win command line and linux command lines as well. I spent way too much time on something I didn't think to check out - the forums; well, at least in the case of the MS XBOX remote. I was about to give up before I thought to try my crappy TV remotes (Samsung, Mitsubishi and some other generic LCD I have [cheap brand - forget which]) and they all worked. Who woulda thunk it? :huh: Anyway.... To summarize.... FLIRC DOESN'T WORK PROPERLY WITH: original XBOX DVD Playback Remote Scientific Atlanta Explorer 8300HD DVR Scientific Atlanta Explorer 4250HD Cable Box - Optimum Is there any possibility of the MS support increasing? Same for the SA boxes (very popular cable boxes)? Anyway... great product, but for me, not so great to make use of my existing WAF approved remotes.

I am on RC 6 and I am having the same issue. Clear Configuration doesn't do anything. When I try to reprogram keys, it says Button Already Exists. I have also formatted via command line. This renders Flirc completely useless and I barely got it 2 days ago.

While it won't help with your actual request (to save a string to a remote keypress), I may be able to help. I have an HTPC that I RDP into frequently, and was frustrated that, after doing so, I'd have to put in the password again from my couch. So, I created a batch file on the desktop that runs this command: C:\Windows\System32\tscon.exe 1 /dest:console That will disconnect the RDP session without locking the computer. To disconnect, I just double click it. *Note: I have found that sometimes, I have to put in 2 instead of 1 in that command. Haven't figured out why, exactly, but experience tells me it happens. If that happens for you as well, you can just put the command in the batch file twice, once with a 1 and once with a 2.

Unplugged and plugged it back in. Still not working. No big deal as long as I can start it from the command line. Thanks for your help!

I just got my flirc. I'm running 13.10 64 bit. I also cannot load the GUI. How do you start the GUI from the command line? Just typing flirc seems to run the command line utility.

Sounds like you will have to use the Command Line Interface, or yeah just wipe out the whole thing. I'll look for a thread on using the CLI, I have never used it myself.

Hi, how many commands need to be assigned? It should be doable by combining 3 things (I don’t know if this will work or not, but it should): Doing it the way described below does not leak any key press events to any other application we could use the remaining free 'usage page 7' HID commands for that purpose, although that can be considered a hack, as those are undefined and may be redefined to whatever later(unlikely). Those key values don’t generate any high-level key press event, so we define dead keys that will not interfere with existing applications. We will use them later at the RAW device level. look here for free values under usage page 7, everything above 0xE7 seems to be free: http://code.metager.de/source/xref/NetBSD/src/lib/libusbhid/usb_hid_usages use mpris-remote as a MPRIS CLI interface. We need to work out a set of commands that do what we want and note them down. link: http://incise.org/mpris-remote.html As a user daemon we can use Touché, that is designed for exactly this purpose, namely binding otherwise dead keys to useful features: link: https://github.com/GuLinux/Touche We use this program to connect the keys with the mpris-remote commands: Bind the keys at the HIDRAW level to those mpris-remote commands (look at the README below) Touché README (extract, second half is important): mpris-remote: The software is there (except for the Flirc GUI profile, but we can use the CLI to program the Flirc hardware using flirc_util record_api command) We just need to cleverly combine what is available

The question isn't really What keys do the remote commands convert to, because they convert to whatever button you have selected in the Flirc GUI. The question is, what keyboard command codes is this beta software expecting for (PLAY/PAUSE/RW/FW/STOP) ? These command codes it is expecting may not be the same codes that the Flirc sends as its keyboard commands.

sry for the late reply, i have 2 scripts running triggered by the callback add-on for xbmc, on screensaver on, a file is created and a 30 minut timer starts. if the file is still in place after 30 minuts, my amplifier get a IR command to shutdown. on screensaver off, the script removes the file. the 1st script then opun not finding it, does nothing, telling me enjoy my buissines. The reason i like to execute a command outside xbmc is because if i decide to play some vinyl after watching a serie, the timer will kill the amp. and removing the little file with an 3th script will let me enjoy my music without disruption. its not a big problem, maybe i have to rethink the whole process anyway. tnx for the link burke, it looks promissing, only thing thats not working is getting the escape code part ( im ssh-ing) but i read something on this forum about that, so ill digg some later. cheers!

Hi; On Windows 8.1, I cannot update interkey delay using flirc_util or the GUI. Luckily I programmed everything I needed before I upgraded but now I have sticky keys and it's a nightmare. Running flirc_util thru an administrator command prompt I receive: C:\Program Files (x86)\flirc>flirc_util.exe interkey_delay 4 Warning: cannot open USB deviceusb transfer failed, error code[-99] Other error usb transfer failed, error code[-99] Other error usb transfer failed, error code[-99] Other error failed to update settings Using the GUI makes no difference; no settings are sticking. Latest firmware (v1.0.0-rc.2) Have updated to latest WinUSB drivers using ZADIG utility Please assist

Edit: Just noticed I posted under wrong topic. Can this be moved? In the past I ran XBMC on a full Ubuntu desktop 10.04 environment, installed Flirc, used the GUI setup, and all was well. I just reinstalled XBMC on top of Ubuntu Minimal (used this script http://forum.xbmc.org/showthread.php?tid=141369) and now my remote will not work at all. I tried the command line with; $ flirc record and mapped all of my keys, saved the config with; $ flirc saveconfig $ flirc normal but still no luck. I've searched the forum but cannot find this topic. Anyone familiar with my issue? Thanks for any help. Flirc Version 1.0.2 Firmware Version: 1 10-02-2011 Remote: Universal Remote Control URC-R50 Ubuntu minimal: 13.04 XBMC: Think Eden

I'm reading through the forums looking for a solution to my intermittent key repeating using a SKY+ remote with a Raspberry Pi running OpenELEC XBMC. The more I read the more I feel (some of?) the issues are caused by IR interference. I experienced this years ago with a simple IR repeater and was surprised when I saw the clear plastic design of the FLIRC as normally the 'red' plastic in front of the IR receiver acts as a filter to unwanted IR wavelengths outside of the standard IR wavelengths which would then also cause insensitivity due to background sunlight or the noise produced by Plasma and LCD screens. I assume the unwanted IR can also end up with a command being repeated as the FLIRC thinks it is still receiving the IR command when it may just be unfiltered noise? The post above by Boltron also points to this physical issue. Were any steps taken to physically limit unwanted IR light, which we find all around us, being received by the IR detectors?

I read about this issue before, but can't find it anywhere anymore (and don't remember if there was a solution). I finally got everything to work. Yeah, very happy :-) But....there is always a but.... I get my Mediacenter-PC to fall asleep and wake-up using the Harmony smart control remote and Flirc. However, when watching TV, the PC is also waking up almost randomly. I have searched in the device manager in Windows and found that if I disable 'wake-up' for the keyboard, the Flirc isn't responding on the wake-up command either. I also notice that there are 2 keyboard devices listed in the device manager (windows 8) and I don't see the Flirc listed. I guess what is happening is that the PC somehow received something like a keyboard command (I cannot imagine it wakes up from other remote commands which are not the exact same as the wake-up command that is programmed). Anyone knows how to deal with this. Obviously I don't want the PC to wake-up when I don't press the wake-button. Thanks!

If you are familiar with running Command Line, "fdisk /mbr" should have nearly the same effect.