Search the Community

A small update on my case. i followed the guide at http://www.missingremote.com/guide/creating-htpc-activity-logitech-harmony-one, and now all the buttons seem to be working fine. But when using flirc it seems it doesn't catch every IR command sent. I tested it with another IR receiver and that worked fine. If first thought it was the delay between keypresses but any value between 0 and 200ms didn't have any impact. Maybe i will go back to the television device as stated on these forums and try what videonisse suggests. But i can't remember having to do both device and activity in the past for other things. But it might be that i always did the mappings for the activity and not devices.

Printscreen isn't like the modifier keys, Flirc already understands it. If it's not shown in the full keyboard layout on your OS, try programming it from the command line. On a Linux box I use: flirc record printscreen On Windows it should work with: flirc.exe record printscreen I'm sure there's a way to program from the CLI on OS X too but not finding the location of the flirc command at the moment...

After much learning and help from Chris!, I am happy to report that my Charter Cable system remote, made by Universal Electronics (see attachment), works like a champ to control XBMC using FLIRC. This remote is a little unique from the Harmony in that there is a master System Power button that cycles through all the devices for turn-on or turn-off - very handy. The issues to be resolved to get this bad boy to work may be common to lots of other cable and satellite remotes, so hopefully this helps others: 1) My Win7 HTPC has a DVD player installed, so I assigned XBMC to the DVD mode. Different device or mode selections on these remotes can behave differently, so be sure to read your remote manual carefully! 2) By default, this remote control's channel control capabilities are locked to the cable converter mode CBL. The affected keys are 1 through 0, CH+, CH-, and LAST. Deactivate this feature to allow programming these keys to other modes or devices for XBMC. 3) By default, this remote control's volume control capabilities are locket to the television mode TV. The affected keys are VOL+, VOL-, and MUTE. Deactivate this feature to allow programming these keys to other modes or devices for XBMC. 4) The operation of the Power/System Power buttons is dependent on the hardware features of your HTPC. a] Power-down: Every HTPC will have the capability to shutdown the computer from XBMC by programming the remote's mode select button (DVD in my case) to the keyboard END button. Power-down is then activated by selecting the mode on the remote then activiating the POWER button as an XBMC computer shutdown command. b] Power-on: Most HTPC systems do not have the hardware capability to do a true power-on from the remote. At best, you can set the HTPC to go into SLEEP mode on shutdown so that the USB ports remain functional and the HTPC can awaken on a subsequent power key command from the remote. SLEEP mode can sometimes be flaky - I have seen lots of spontaneous restarts from SLEEP mode. In my case, I have a cabinet fan powered from a USB port, so the SLEEP mode doesn't turn it off. I have to do a complete shutdown and use the front panel button to turn on the HTPC. Other solutions exist - search the FLIRC forums for some interesting fixes. Power-on and automatically run XBMC usually requires putting an XBMC shortcut in the HTPC Startup directory (see MS Win7 Help for directions). You should add some delay to the XBMC shortcut to be sure the HTPC is completly booted and stable before XBMC is started - not doing so can result in odd behavior from the remote and XBMC. Search the XBMC forums for more information. In my case, I needed to add 25 seconds to be sure the wireless network was connected and stable. The resulting shortcut command was everything within the brackets including all punctuation ["C:\Program files\XBMC\XBMC.exe" -d 25]. 5) FLIRC keystroke entry: For some unknown reason, my HTPC system required that the remote send a repeat of each key code for XBMC to recognize the command. The ability to do this in FLIRC is not well documented but works well when implemented (thanks to Chris! here). It turns out that you can repeat the key programming at least twice in sucession for each remote button (and sometimes more, it seems), and FLIRC will dutifully send the sequence when you activate the button. Two programming cycles for each button did the trick on my system. Hope this helps!

Hi Chris! I just did a quick check on your input. A symbol lights up whenever an IR command is actually sent, so i tested the play and other buttons in both activity and device mode. In device mode it lights up and flirc recieves it, but in activity mode these buttons show no activity. So it seems to be more of a misconfiguration on my part or some software error on logitech's part. I'm guessing it's number one, so i'll wipe it and start over again. I'll post my findings here, should anyone ever google this and have the same issue. Flirc in itself is an amazing simple product, does as described and does it well, i'm very happy with that.

ok, using profile for SAMSUNG LN46C650L1F - doesn't seem to be listened-to by my samsung av receiver - Got it working. Seems to receive all the button presses. Some niggles: after programming it on my mac i plugged it into my linux xbmc box, and it didn't seem to be working. plugged it back into my mac; working. further investigation showed a kernel oops logged in dmesg when the flirc was plugged in. rebooted, then it seemed to work. unwelcome for something that's supposed to be presenting as a keyboard. Because of that, wanted to do future programming on that linux box, installed flirc from deb repository (system is ubuntu precise 12.04 64-bit), but it doesn't recognise that the flirc is connected. even as it's there, working, receiving and processing button-presses on my remote, flirc app thinks it's not there. literally, using arrow keys on remote to go back the bash history to the flirc command, and pressing ok to enter it, flirc thinks there's no flirc there with "Warning: cannot open USB deviceFlirc Version 1.0.2 [a3bbc3e70a32c4f2] Device Disconnected" (then help output) I note the linux app is lagging the mac app by a few minor versions.

I'm confused about what you're trying to do but can't. The arrow keys (and every other key on your keyboard) are easily programmable in both the flirc GUI and from the command line. What have you tried so far? Is there a step we can help with?

For what it's worth, on Linux I think the command line is the best way to program the device anyway.

Yep, looks like a bug of some kind. Thanks for the screenshot Joachim. For the moment users can program Flirc using the command line () or use another OS. Hopefully this will get a solution soon. Chris!

Just ordered a Flirc for my Raspberry to use with my Apple Remote since the Flirc seems like the easiest way to get things working - GREAT! But this might be an idea for "future Flircs". In my living room I have a media cabinet with a Receiver, DVD, TV and a Mac Mini (running Plex). Since this is a closed cabinet, IR won't work and I rather control everything from ONE remote than several. So to solve this, I have installed a GlobalCaché iTach WF2IR. This device receives commands from the OpenRemote controller installed on my NAS. Then I have OpenRemote Panel installed on my iPhone to control each device. All of them connected to my WLAN so when I press a button on my iPhone panel, it sends the command to the controller which sends the command to the iTach which converts the signal to the IR emitters and sends it to the device (Receiver, TV etc). Have you seen iRuleAtHome? Well, this is more or less the same thing but Open Source. If you want more info on my setup, see this post (not yet updated for Raspberry/Flirc). So here's my idea. The devices I can control is limited to the media cabinet in the living room since the IR emitters needs to be connected to the iTach with cables (a few meters)? If I need to control my media PC (Raspberry) in the bedroom I would need to get another iTach ($150) and connect 1 IR emitter to that which sends the command to the Flirc. Now, wouldn't it be better if there was a "WLAN version" of the Flirc compatible directly with Flirc? First, it shouldn't set you back $150 and second, it would receive power from the USB port rather than a dedicated power adapter like the iTach. Sure, this might not be the way Flirc is heading and development would probably take a while, but if you're up to another challenge... ;) Keep up the good work!

I'm trying to configure the standard keyboard media buttons but as they are not available in the GUI I try finding a way to do it manually using the CLI. It is exactly the below HID's I want to program, but I don't understand what number I should use together with the command "flirc.exe record_api ", can someone help me out? :huh: (for example "Stop" is 1<<2 which should be 4 (binary 100). However, "HID_a" is said to be 4???

Appreciate the quick response. Flirc installed fine and I can control it (moreso once the USB receiver gets here in 2 weeks!) via command line. I'm assuming this message is something I can ignore. Correct me if I'm wrong; I'm a linux noob. You might want to run 'apt-get -f install' to correct these: The following packages have unmet dependencies: flirc : Depends: libqt4-svg (>= 4:4.5.3) but it is not going to be installed E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).

Hi TBS, Currently by command line only: Would be great if you made this thread into a how to for users who aren't command line strong and want the windows button. Pleasant regards Chris!

Actually, you can make AppleScripts and/or shell scripts into Automator services really easily, and they can be called by any keyboard shortcut you want to assign in system preferences, without the need for any third party software at all. You could potentially get a ton of mileage out of your flirc on a Mac this way, making shortcuts for almost anything your computer can do, and they can be set up to work only when pressed from individual applications, or from any application universally. Open Automator and create a new service (there's a Service template you can select from the menu when you first launch Automator) In the far left column, choose Utilities For this example, I'll choose Run Shell Script from the second column. Double-click it. In the main workflow area, edit the text of the shell script to say simply: pmset sleepnow Notice the top part of the workflow area lets you choose context. From the left pulldown, choose 'no input.' By default a new service will work text from any application, but if you want your sleep command only to work when XBMC or something else is in focus, just browse to the app from the pull down menu near the top right. Save your service. I'll call this example service 'sleep'. Your new service will be saved in ~/Library/Services/ (the tilde (~) represents your home folder). If you specified 'any application' in step 5, you should now be able to get to your new service from the menu bar of any app. For example, if Finder is in the foreground, click the Finder menu -> Services, and you should see your service. If you chose to make your service work from only a specific app, bring that app into focus first and then check the menu. Now, to assign a shortcut key: open System Preferences -> Keyboard and choose the Keyboard Shortcuts tab. In the left column, choose Services. On the right, under General, you should see the 'sleep' service we created. Highlight the service and click the 'add shortcut' button (or double-click it). Press the keyboard shortcut combination you want to assign. That's it, you're done! Edit: It may be worth noting that on Lion this was broken at first for me. When I just redid this to make sure my instructions were accurate, I could see my example sleep service in the Services submenu under any application, and clicking on it put the machine to sleep, but the shortcut key I assigned wasn't working. I fixed this by changing the automator workflow, saving, changing it back and resaving. Simply rebooting may have done the trick too. Edit 2: I just noticed that there's already a service called Put System to Sleep in System Preferences -> Keyboard -> Keyboard Shortcuts. Highlight Services, and it will be under the Text section. So technically if all you want is a quick sleep shortcut, you could start this process at step 8, but expand the Text section instead of the General section in step 9. I'll leave the rest of the tutorial though, as it demonstrates how you could run other scripts that aren't already provided in the menu system.

Woah, cool. Agreed that the apple button would be easier. If Jason knows their maybe a command line key modifier. Pleasant regards, Chris!

I think I may have cracked it. Just to be clear, I am using a 2012 Mac Mini with Lion preinstalled as an XBMC media streamer linked to an AV receiver (and projector) with a Harmony 900 RF-IR remote control and Flirc in one of the Mini's USB ports. I bought Flirc because I had problems with both the standard Harmony Plex setup and later RemoteBuddy in that the first was unable to wake the Mini. Remote Buddy could do it but not as consistently as I would like. Flirc will wake up the Mini, even if I sometimes have to repeat the key press (I tend to use the enter key). This is what I did. I set up the Harmony using one of the two recommended remotes (Panasonic TC-P65VT30 or Samsung LN46C650L1F) and made sure all keys were occupied (doesn't mater with what but make a note of it for later use). I also defined a soft key for "Sleep" and assigned a random command to it I used AppleScript Editor to create two scripts: the first will put the Mini to sleep: do shell script "pmset sleepnow" the second starts XBMC: application "XBMC" activate In order to link these scripts to shortcut keys I had to use an external app and I chose FastScripts (free with a max of 10 shortcuts) to which I linked these two scripts (Ctrl+Sm Ctrl+X). Using the Flirc.app I associated Ctrl+s and Ctrl+x with the relevant buttons on the Harmony. In the Harmony activity I had also set things up in such a way that every time I switch away from using the Mini the "Sleep" button is activated. That did it. I can now call up XBMC from the Mini desktop and when I switch away from using the Mini it will be put in sleep mode (fortunately, the Harmony will also use this script when switching everything off in my home theatre). All this would have been superfluous I think if the flirc.app had had a Mac keyboard with the eject key so I could have used Opt+Cmd+Eject for sleep and I would not have had to mess around with scripts and external apps. On the positive side, I have learned a little bit about using AppleScripts (I am a novice Apple user). PS. The scripts MUST be moved to ~\Users\username\library\scripts

Hey, I'm so sorry for my delay. The windows key is a modifier key. I never imagined on anyone wanting to hit modifier keys by themselves. If you want to do this, you can do this with the commandline. In windows, the commandline is located in the Flirc installation directory. You'll have to open up the commandline utility. Here is the command that you want: flirc record_api 8 0

I'm curious to know if anybody running XBMCbuntu (or any other Linux setup) has successfully programmed a Logitech Harmony remote for full functionality. I installed the Flirc GUI within XBMCbuntu, which seemed to record the basic functionality. I had to use the terminal command line to record advanced keystrokes. Within XBMC, however, I get almost no real functionality. Only the directional buttons "work," and that is occasional and usually scrolls in whatever direction it chooses, regardless of the actual input. I think the problem may be in the device or activity setup within the Logitech Harmony software. Obviously, neither XBMC nor Flirc have profiles within the software, but some users running Linux XBMC builds have reported success in the past. Unfortunately, I've never been able to replicate. The device profiles I've tried include DVD Player, MCE Keyboard and a Panasonic/Samsung TV as suggested by a user in another thread. No joy, but it could be that I'm setting up the activity improperly or customizing the buttons differently... haven't found any advice on those fronts. Any suggestions on what device profile should be used, how the activity should be setup, or how the buttons should be customized? Really looking for help here, I'm on my last nerve finding a working solution. Thanks in advance.

Okay, I got it working. This is something I've tried multiple times before with other IR receivers, but this is the first time it's been 100% successful... so kudos to you guys for Flirc. it seems to be the missing piece to my puzzle. :) 1) Using my generic Media Center remote, I recorded keystrokes using the terminal command line. (I picked the most useful from this list: http://wiki.xbmc.org...?title=Keyboard ). **Because I'm using a generic MCE remote, I had to record each keystroke twice in the command line to avoid pressing each button twice in XBMC, per this thread: 2) In the Harmony software, I created a device, "Flirc," based on a generic Microsoft MCE Remote (Computer > Media Center PC > Microsoft > MCE Remote). 3) In the device settings, I created a list of custom IR commands (at the bottom of the page); I simply named them after the keystroke they emulate (X, P, Spacebar, etc.). The only default IR commands I used were the directional commands. 4) Using the Harmony remote, I learned this set of custom IR commands from the MCE remote. 5) In the device settings, I customized the Harmony remote buttons by assigning them to the newly-learned, custom IR commands (Menu = M, Pause = Spacebar, etc.). 6) In the Harmony software, I created an activity to turn on my TV, set it to the correct input, and select my Flirc device. 7) In the activity settings, I once again customized my Harmony remote buttons appropriately, assigning most to the Flirc IR commands, and others, such as volume control, to the TV. 8) ???? 9) Profit!! I now have a 100% working Harmony remote with one-touch access to my XBMC setup. Well, almost one-touch... I'm still trying to figure out how to use the Harmony remote to turn on my HTPC or resume XBMC from sleep... but that's another headache for another day. Hope this helps.

Chris, Thanks for the reply. I really don't think it's my rig, simply because programming Flirc using a generic Media Center remote works fine. Doing so, however, somewhat defeats the purpose of my Harmony remote - to have one remote. I saw Digitalb0y's thread previously; I used it as a guide for programming Flirc from the command line in the Linux terminal. My issues on that front are limited... namely that the numbered buttons seem to confuse the recording actions, resulting in overlapping and conflicting signals among them. This is not a huge concern for me, as I have yet to need a numbered keypad within XBMC. With the remote recording properly from the command line, the issue for me is getting those commands/keystrokes to be recognized and executed properly within the XBMC environment. Again, I believe this is related to the Harmony remote setup. Since there is no "XBMC" or "Flirc" device listed in the software's database, I have to create a custom device and assign button actions manually. Furthermore, each "activity" set up in the Harmony software. For example: 1) I set up Flirc as a device in the Harmony software using a generic "DVD player" config. 2) Using the remote to control this generic "DVD player," I assign keystrokes to the remote buttons using Flirc's command line. 3) Within the Harmony software, I create an activity which, when started, turns on my TV, sets it to the proper HDMI input and selects the "DVD player" (Flirc) 4) Within the activity settings, each button on the remote is set to control either the TV or Flirc; i.e., volume controls the TV, where "Info" sends the keystroke "I" to Flirc (as was recorded successfully in the command line). Since Flirc is obviously working with other remotes, I think it's just a matter of setting up the remote properly to handle Flirc. Thanks again for any advice.

Hey David You tried the latest v6 release? http://forum.flirc.tv/index.php?/forum/32-wake-up-command/ Are these two different systems running the same hardware? Are they running the same version of the OS? Can you try taking the 'working' one and using it in the other system to see if the problem follows the device, or the system? Thanks David.

I noticed when I was programming my flirc that after programming period (.) and comma (,), when I tried to map w and O, they responded with period and comma. I am using a Harmony One, configured for Samsung LN46C650L1F TV. Yellow is programmed to Skip Back, which is comma (,) Green is programmed to Skip Forward which is period (.) C is programmed to o B is programmed to w Any ideas why this is happening? To record perio and comma, I state: flirc record . flirc record , Should the command be different? Thanks!

Hi iainmacleod, It may be that the code the signal the remote is sending is the same or similar. If you are using the GUI (which from the command line prompt you provided above you're not) it will show that the button is already recorded. Two things to try: 1) Use the Flirc GUI to program those buttons - see if anything unusual happens 2) Check in the harmony software that the buttons are definitely mapped to different functions I may give digitalb0y and friendly message to see if he can help or suggest anything to do via command line if GUI option isn't viable to you (as he's very knowledgeable in those parts) Pleasant regards, Chris!

Firmware: 153 aka fw_wake.bin Flirc Version 1.0.3 Remote Harmony 885 (Using Samsung profile posted elsewhere) System Windows 7 x64 Problem: Getting "error: no space on device" using Flirc.exe from then commandline Steps: flirc.exe record wake or any other button, only in this case it was the wake key Output result Succesfully recorded button Test the command using the remote, nothing. so usualy I repeat the command flirc.exe record xxxx until i get an output result of: error: button exists Then I know it recorded ok. However doing this today resulted in error: no space on device What it looks like, is that the Flirc is *maybe??* recording a slightly different remote signal every time, thus filling up the internal memory. Attached is my config file, if that's of any use. Thanks Neal nospace.zip

I've set up the wake command as DigitalBoy stated and it seems to be working well. I tried to set up the suspend command that burke mentioned above, but am having problems. If I try to map the "All Off" power button on my harmony to the f2 key, I get an error that the button is already mapped - I get the Button Already Exists message from flirc. What I'd like to have happen is if I press the All Off button on the remote, XBMC is suspended and the TV et al are turned off. Is this possible using firmware 1.0?

OMG, installed Windows 8 Released Preview and driver with my previous changes is invalid, need to reinstall WDK and use inf2cat again. Or better, I'm not sure, because the error message is a little different now: -------------------------------------------------------------------- EDIT: oh, my bad, forgot to disable driver signing on Bcdedit command. Anyway this post would be useful for someone seaching about same error message.