Search the Community

Awesome. Can anyone direct me to the command line instructions?

@00g I had exactly the same problem (also a Sony remote, probably not a coincidence) I can confirm that setting the sensitivity to 0 via the command line fixed the problem. A value of 3 doesn't work, I've not tried 1 or 2. I guess the down and left buttons work on very similar frequencies.

i just updated the FW to the beta "wake up" version, and the problem persists. And it doesn't matter if I'm scrolling through a list quickly or slowly. Every one in a while it'll just go left. I've used command line stuff in the past. But, not much. Mostly just for rooting my phones and what-not.

We could change the sensitivity dynamically, are you familiar with the command line? This hasn't made it's way into the GUI yet.

Issues with Microsoft MCE and MCE keyboard configured remotes (including universal remotes) Symptoms (all or one) When Programming FLIRC message of 'Button already exists' even though a different keyboard button is being programmed by a different remote control press Having to press a key on the remote twice to send a command Programming FLIRC issues when a different USB port is used from when it was originally programmed Cause (to each of the symptoms above) This remote profile is a microsoft protocol that uses a non-standard frequency. Flirc can work with it, but it's not the best The remote sends out a unique key code every other consecutive key press, for the same physical button. Probably one of those microsoft remotes that use the non standard frequency, 56kHz. 38kHz is the frequency most remotes use, which is the center frequency for flirc. Tricks have been played to get flirc to work at 56kHz, the placement from the front of the computer, to the back of the computer, will actually have slightly different frequency drifts, changing the unique pattern associated with a button. Solution (Remedy for all issues) Try another device setting; sony, samsung, boxee, plex. It won't matter which one you choose as you'll be programming flirc what each button does. other possible solutions: - (For issue 1) The quick remedy to this is to record each button twice, and "catch" each unique key code for every button. - (For issue 2) The flirc command line has an option called sensitivity. You can try lowering this number

I meant to flag the + and - issue as you can't access them in the keyboard UI. i neglected to mention it as I found out that in harmony software you can map volume button to another device on you remote. e.g. in my case when in the setting to control xbmc when I press volume up it sends the volume up command to the tv using the tv device setting.

The major problem with using the other profiles (MCE/Plex etc) is the limit on the number of keys and the hassle of not having easy to understand 1:1 mapping. In particular, if you use a Plex/MCE remote mimic in your Harmony, and you want to program the 'extra' harmony buttons at the top of the harmony remotes, which you can have an unlimited number of for doing all sorts of fancy things - you have to map each of these to some MCE remote button first and then program that in remote.xml to do what you want .... and pretty soon your run out of available remote buttons. Far easier just to do a direct 1:1 mapping - set your Harmony up as a keyboard, then look at the list of keyboard commands in XBMC. Program each letter in the flirc software to be that button on the remote. Then you know your remote is sending 'P' for play, for example. And you can easily then use ALL keys, with modifiers etc....lots of buttons to play with. I don't have (or want) any keyboard attached. I will give the sensitivity settings a try and see if that helps. (My RC6 receivers already do just fine with the remote set to MCE remote mode so I don't really need the flirc to help me with that). Jason - good support for this would make your product a lot more flexible again and I am happy to help with any testing etc required. Can flirc be started from the command line with some debugging output then?

This remote profile is a microsoft protocol that uses a non-standard frequency. Flirc can work with it, but it's not the best as I had to play a lot of tricks. The flirc command line has an option called sensitivity. You can try lowering this number: flirc sensitivity 2 (for example) With each sensitivity, you need to re-learn your keys. I can't do this on the fly as it's a limitation of my algorithm. Another circumvention would be to use a different remote profile. Most people assume to use media center remote profiles like; plex, boxee, apple tv, etc. When really, you can use any ol' remote. Try a samsung, or panasonic. I always recommend those as I've always been sure they don't do anything out of the norm like Microsoft.

+1 I purchased with the same intentions and got the same results, I started with programming the Flirc with my Harmony setup as a MCE Keyboard and ran into conflicts within the first four directional keys. I skipped those and moved on the the numerical characters (1-9) and ran into a conflict after getting to the number "4". I looked at the Plex Player in the Harmony settings put it is limited to the amount of keys to program and then I would have to edit the keymap.xml file in XBMC which I was hoping to avoid by purchasing the flirc. I was able to get my harmony working by using the IR learn command and programming the remote from my original Microsoft MCE Remote and then using that to teach flirc my settings. However, I still have an issue with having to press every key on the remote twice to get the flirc and xbmc to do anything. A bit cumbersome. Hopefully someone has a better answer, as I had great hope for this product. Thanks!