Search the Community

Thanks for the answer Chris! I have tried noise cancelling and it doesn't seem to change anything. No other devices either, but checking that was a good suggestion. I have a new theory though: At night we often roll up in blankets at this time of the year and I guess they will lessen the reflection of our surroundings. The funny thing is that sometimes the AVR blinks as it recognises a remote press (it does so even when it doesn't react, I use the directional keys for flirc which don't do anything for the AVR while not in a menu) and the Mac doesn't react, even when I'm right in front of the flirc. It seems to me that this happens when I don't press the button all the way down or at a slight angle. I tried to learn this "slight press" but it doesn't seem to give a different signal, flirc GUI says "button already learned" It's not too bad really. I just thought that I maybe missed some command for the CLI to increase sensitivity and was a bit surprised that the AVR picks the signal up more easily. Really love the Flirc and just wished I had found it before I spent weeks unsuccessfully trying to find a universal remote I liked.

Well I fixed my own issue. I ran Flirc from the command line as root and it connected. I haven't tried it in my HTPC but at least it appears to work on my desktop

ok so this is kinda specific android treatment for android devices where flirc is connected to!? Flirc receives the command a remote sends to it (e.g. "a") and flirc passes it through to the android device (like an ouya). The app acts as a "man in the middle" and "translates" the "a" key to "vol up"!?

It's not easy to find a remote, which gives you full functionality for both devices without 1. to be a universal remote or 2. overlaps functionality and interfere the second device You can look for a dvd/ bd sony remote, which offers also tv functionality or vice versa. In both ways you will probalby not have full functionality for the second device on the remote (tv or dvd/bd) in most cases I know, that some older sony vcr remotes have some kind of mechanical switch to change the profile between vcr and tv, but they often are missing the navigation buttons (arrows) So the best solution for you seems to be an universal remote. There are cheap fancy ones, like one4all, which will grant you the best remote experience. As long as you have both devices in sight, using the same remote, you will always control these both devices with buttons/command related to both devices. There is no way to avoid this. In my case, i use a silver ATV remote to control my xbmc. Small, sleek design and functional. For enhanced commands like info, context menu, zoom etc. i'm using unused buttons from my tv remote, as long, as the long press feature is not implemented yet.

do you guys have sleep detect enabled in the GUI? Also, make sure you haven't recorded any noise. use the commandline, flirc_util settings. Look for duplicates. Delete all duplicates and re-record those keys. When receiving a signal, flirc will send a character to the machine. Regardless of the state of the machine. Sleep detect tells flirc to check if the computer is sleeping. If it is sleeping, do not send any keys unless it's the 'wake-up' command. Further, if you don't have sleep detect, and have recorded erroneous noise, then the machine will see noise as a false signal, and send a command to the computer. ** EDIT ** TLDR; enable sleep detect in the gui

Hi, There are several buttons I can't pair with a remote command. I always get a report 'button already exist' Even when i clear setiings via File -> Clear Configuration. or choose 'Redo' or clear button I try to setup Flirc with Windows Media (for Raspberry Pi) with a Harmony 700 The harmony is already set up. I'm using GUI 1.2.2 Based on Qt. 4.8.0T. and latest Firmware (2.3)

So you're using a wmc (ir6) compliant profile with your harmony? Did you mapped every button twice? this is necessary,due to the wmc protocol sends a second command on every second keypress.

Yes it's possible with either the GUI and the command line. It's under the file menu in the GUI.

I found 2 old remotes saved from bin few years ago. Both have Play and Pause buttons separately. Both have the same behaviour; - Play with the first press Play button and play again from beginning with the second press. - Toggle file view/play list with Pause button - Stop paying with Stop button When a button is recorded with the xbmc profile then we con go to the keyboard profile and press recorded remote buttons, then key turn green according to the remote button pressed. So Play button sends p key Pause sends space bar Stop sends x key sudo ./flirc_util keys allows to check that as well. ($ sudo ./flirc_util settings as well) Could you run it and post please? I don't have a USB keyboard to compare when press p or space bar. BTW: I just note that my request in the other thread " Keyboard key (action) mapped to more than 1 remote key" is implemented. If you have more than 1 remote or 1 remote with more than 1 profile, you don't need to delete the previous record for one button to record a new button code to the same key (action). Not easy to explain. For example, you record Play button from the remote 1 with the xbmx profile, > is green. You can record the Play button from the remote 2 with the xbmc profile, > will be green as well. Look at the CLI command: $ sudo ./flirc_util keys Recorded Keys: Index hash key ----- --------- --- 1 9D6C74B0 tab 2 5F5A4B9D home 3 5B1B6912 escape 4 5B06EC4E x 5 9DC159A3 c 6 5B68E519 up 7 1917DA7B left 8 99BE5F32 right 9 5729038F down 10 5BAC361F return 11 99298E70 backspace 12 5F7C2097 , 13 5F386CE9 . 14 9D7D089E pageup 15 9D7D6728 pagedown 16 1D89F0E4 i 17 5BF9F14B / 18 5FF41AE4 p 19 8096252F p 20 862411 space 21 6104EE71 p 22 61C0603E space 23 61040FBF x I have 3 p keys, 2 space and 2 x. This is what I was saying in the other thread.

Sorry for abcence, was busy. You're right. The behaviour depends only on the app. So as long as the app reacts on common keyboard commands, it will also respond to flirc, as long as the command is related to the corresponding keystroke.

Hi, This is an idea, not very important for me right now but could be convenient. Let say you have a usual remote for some devices. At the top of the remote you have few keys to choose the device to send the beam: TV, DVD, SAT, PLAYER, AUX... First you press the device key and then press the action key to the selected device. What is the purpose of the play, pause, fast forward, etc when you select TV? Nothing. When you select PLAYEUR key the above keys are used to the right action for the player and mapped. Note the codes are not the same when device selected is TV or PLAYER. It could be usefull to map the play, pause, fast forward, etc to command the player with the both selected devices TV and PLAYER for example. So, to be able to map 2 or (more ?) remote keys (different codes) to 1 keyboard key (action). What do you think?

I've temporarily adopted a solution... Since i know a little about C# programming, i've written a simple application. It basically runs at startup and looks for XMBC windows instances to automatically change send the keyboard layout change command to XBMC. It's not the perfect solution, but since we don't have the possibility to change Flirc's keyb. layout, it works fine for me. I hope the programmer will include features like this in future releases, it would be cool! :)

This wont work for me... I using Xbmcbuntu.. after "sudo ./Flirc" I got this message "sudo: ./Flric: command not found" is ther no other way?? tried it as root or with chmod but nothing work... as root "bash: ./Flirc: Permission denied" thanks for helping

In order to program Flirc from a debian Linux OS such as Ubuntu, you must do so as a privileged user. try "sudo Flirc" from command line in your terminal and the status should show as connected and there is no need to use a second computer. If you are advanced with Linux configuration, you can configure your user account to have "root" privileges but that decreases system security. TO ADMINISTRATOR: As a fellow Linux developer, I would recommend that the Flirc binary ask for administrator password and run as root automatically to make programming Flirc seamless on ANY Linux OS where sudo is allowed. Have a great day everyone! - Double T - doublet30@hotmail.com

Wow, thanks! Using the Media Keys keyboard got the Skip Back (Previous) and Skip Forward (Next Track) working! Any suggestions for the Info command (Ctrl+D)? Also known as the "Shortcut Menu" in WMC.

Flirc basically acts as a keyboard. So it depends on your mapping, how it acts with programs and system. E.g. if you map it with standard wmc commands, you will be able to control all programs/ apps, using these commands like WMC, DVD/BD-Software, VLC etc. The same goes to any other keyboard related command and its function within the used system and its programs.

I think one of the key ones missing: The "Green Button" command = Windows Key+Alt+Enter Live TV = Ctrl+T Recorded TV = Ctrl+O I programmed them in the Full Keyboard layout, but if you look into adding to the Windows Media keyboard those would be helpful.

Previously I used Flirc v 1.2.2 which installed with FW v-16.-1 bottom left corner. when I tried force upgrade it said v 2.3 was available but crashed every time I tried to upgrade. I redownloaded the exe and reinstalled, and it showed FW v2.3 bottom left corner. Then today it has somehow reverted back to v-16.-1 and nothing works. The dongle does not see remote clicks, and I cannot erase learned commands, so I redownloaded the exe and installed but no joy. It would be nice if I could just download the latest FW, but it seems to be either unavailable or too hard to find. There must be some way to fix this, I really don't want to clear the config because It's almost there except for a couple of lagging keys, and I'm also worried that It won't work at all after clear command. Oh, using Windows 8.1 with corei7 and buckets of DDR

Hi, below is the solution for your problem: You will need to use the command line. You should know how to navigate through your file system and call programs using the command line. ---Theory:--- For the OS, the numpad keys are different keys than the main field number-keys. The operating system maps the same symbol (the number) to both keys. To get your mouse emulation, you need to map the low level keypad values, instead of the main key field keys. The Flirc GUI can map the main field keys only, but not the numpad keys. ---Obtaining the needed values:--- To program the numpad keys, you need the raw USB-HID values as decimal numbers, and program them with the command line tool and the tool’s record_api function. You can get the raw values from here: http://www.freebsddiary.org/APC/usb_hid_usages I’ve quoted the relevant part below: For reference, this is the main keyboard that the GUI programs into Flirc: using a Hex to decimal number converter (like this online one: http://www.statman.info/conversions/hexadecimal.html), you can convert those to decimal numbers. This is range 30-39 decimal. But you will need those: the Keypad numbers 1-0 have decimal values of 89 to 98. You can calculate the other values (+, -, / keys, etc), if needed, by simply counting down from 89. --- Programming Flirc:--- First, unlearn all the keys you want to use for the mouse emulation (with the GUI or command line tool). (For linux, the command line tool we will use is called flirc_util. For windows it *might* be called flirc_util.exe. I don’t know, as I don’t use windows, look in the program’s install folder) Now you use the command line tool to program the Keypad keys, by using the program’s record_api function: Quote from the program’s internal help: You don’t want any modifiers, so the first argument is 0 and the command is: flirc_util record_api 0 <arg> or flirc_util.exe record_api 0 <arg>, where <arg> is a number between 89 and 98. eg.: flirc_util record_api 0 89 to program the keypad 1, flirc_util record_api 0 90 to program the keypad 2, etc… so you start the program with the proper arguments for the key you want to program, then the program waits until you press a key on your remote, programs it and exits. you redo that for every key you want to map, entering the correct value as a start parameter. BTW: note for windows users: you cannot simply click a command-line program, that won’t work. You have to start the command line from the menu, navigate to the exe’s folder (use cd command) and then type the program name and its parameters. <Tab> can be used for auto-completion, <Arrow up> and <Arrow down> to recall the last entered commands (so you don’t need to retype the command 10 times, but can use <Arrow up> and edit the last command.) I hope that helps

@burke, I understand your 'unified logic' idea but this doesn't ALWAYS apply in software. Even you say it 'has pretty unified logic'. That implies that it may not be the same throughout. My comment on that is derived from the '101 on keymaps' section of the official XBMC forum asking the user to download a complete 'keyboard.xml' file. I took this to mean a user needed to download a complete one in order to change something. Fortunately, that is not the case. Creating a 'keyboard.xml' file and changing one function does nothing to the rest of XBMC's built in mapped keys. Your mention of my future "how to" is for XBMC users in general. Flirc is not a requirement. A keyboard is not actually required for this but at least some input device that could send keyboard commands to edit the 'keyboard.xml' file: ie. an on-screen keyboard (Android, iOS). Editing the 'keyboard.xml' file is to change the default keys to function with different keys. For instance, the MCE Remote sends the keyboard equivalent (CTRL + SHIFT + P) to play a video. You could edit the default XBMC key of 'P' to be the same as WMC's and now your remote can control XBMC and WMC's 'Play' function with the same remote control keypress (since they are mapped to the same key combination). If you use "standard ir", as you say, there is no difference. The 'ir' device sends some signal that is interpreted by the receiver as a key press function. If you determine what that key combination is, you could edit the 'keyboard.xml' file of XBMC to match this command and now your remote is controlling XBMC. It doesn't matter if you buy a $12 remote/receiver combination, or are using a custom LIRC script, it will work. In this case, the device sending the keystrokes is Flirc. There is a great little bit of code called 'ShowOff' that will display the keys hit (or sent by any ir device) by way of an onscreen display. Very tiny and no installation required. I may check out the 'addon' but I'm not a fan of additional software to do something I will probably only need to do once. I'm the 'tinkerer' type. Have fun...

Ok, I've only been using Flirc for about 3 hours so far with my Harmony One. After initial setup I also noticed that some of the buttons on the Harmony remote weren't doing anything, but instead of trying to map them in Flirc I instead added some mappings in 'Activities' (not the 'Devices') tab of the Harmony Remote software. I edited the new activity I'd just set up (called XBMC) by clicking Customize Buttons. The top button (for example) is 'Menu' which I set using the dropdown to Device = Media Center PC and Command = ContextMenu. I'm not running any beta software and I've not installed an add-on in XBMC. What might be confusing the issue is that the Harmony remote uses it's own setup software that adds an extra bit of confusion to the whole thing. Fullscreen for example is a touchscreen button on my Harmony One and is not mapped to a specific hardware button.

Ed - I understand the frustration all too well trust me ;) I completed all of my changes on the command line, so I can guide you through the changes in that manner. First can you SSH into your device? I ask because you need to check if the add-on you installed in fact installed and dropped the correct files into the proper location. Also you will need to be able to add a udev rule to your device if you are running a Linux based machine (where the actual Flirc device will plug into). The udev rule you need to add is made to auto mount the usb for read and write access and this is just a work around. The udev rule is simply a file that the Linux system looks at while loaded the OS and applies the "rules" each file describes. You can see the actual code from the github repo here: https://github.com/flirc/flirc-xbmc-plugin if you look in the folder marked linux you will see the file that has the generic udev rule you need to create. Its one line of code: SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", MODE="0666", GROUP="pi" You put that in a file in the /etc/edev/rules.d directory and then reboot your XMBC device and you should be all set. You may have to reselect the Windows MC contoller, but I only say this becasue this is what is selected for mine. This was my missing piece to get the whole thing up and running. You will need to do this step to get your RaspBMC device to see the Flirc usb. Once you add this on you next reboot you should see it as "connected". If you installed the add-on by adding it as a source and saw the gui for the Flirc device on reboot then you may already be up and running after adding the udev rule. Once I added the udev rule the gui popped up for me on my RaspBMC and wanted me to prgram a device as well. I happily followed the on screen setup and programed the arrows, a back key and enter key. This is not needed and I realized that when it then asked me to save my configuration. If you have the add-on you do not need to physically program the device, if you can get back to that gui on your XBMC unit on the left menu you can "load a configuration" this is what you want. The add-on has a pre-programmed config file and when I selected the load option I was only presented with one option, once selected I closed the Flirc gui and have been good to go. Let me know if this helps, or sounds "unclear". I have been writing this as I have been working on some code between tests ;)

For several weeks I'm now trying to get my Flirc to work with my Ouya, but without luck. I followed and tried various other things, but can't get a single remote command to work when Flirc is connected to the Ouya. I can safely assume that the USB port on the Ouya is working, as any memory stick, USB mouse or cable based USB keyboard works - any USB device I connect works on the Ouya. My Harmony One works with all other devices and send proper IR commands. I used the profile "Flirc > XBMC" for my activity I program the Flirc through a Mac. Using flirc_util, I get following output after a "fresh" install of the flirc: sh-3.2# ./flirc_util version Flirc Version v1.2.2 [v1.2.2] 2.3 01-25-2014 [0x3DB4D4F3] sh-3.2# ./flirc_util settings Settings: sleep detection: Disabled noise canceler: Disabled inter-key delay: 6 state: 0 builtin profiles: Enable Memory Info: keys recorded: 13 keys remaining: 156 memory used: 8% Recorded Keys: Index hash key ----- --------- --- 0 46AB894B escape 1 6576B811 F3 2 869FAF61 F4 3 6FF9C61 F5 4 C633C63C F6 5 C6E38398 F7 6 A5E38398 F8 7 A5FA9C61 F9 8 86BF9B4B home 9 86B71F14 left 10 25B31F14 right 11 65BF9B4B down 12 460CD99A up When I take the flirc and connect to a PC for example, it works. I can control a slide show and do other simple things using my Harmony. When I connect the flirc to my Ouya, nothing works. And whenever I had it connected to the Ouya, it seems to "loose its memory": When I connect it back to my Mac the flirc_util now shows: sh-3.2# ./flirc_util settings Settings: sleep detection: NA noise canceler: NA inter-key delay: NA state: 0 builtin profiles: NA Device currently in bootloader I tried this a few times, and can reproduce it consistently... Starting the flirc software on my Mac will re-program the flirc with fresh firmware and proper profile. Plug it into Ouya - everything gets lost... Does this sound like a hardware problem of my Flirc?

I just bought a Flirc to use with my Harmony 700 and XBMC on a Win 8.1 x64 machine and I'm having similar issues with XBMC (and now nothing else) getting any commands from the Flirc. I installed the Flirc profile on my Harmony 700, but could never get any keys in XBMC to work. I was able to do the minimalist command recording to verify the Flirc was working. Based on the advice in another thread, I forced a firmware update to v2.2. But now the Flirc doesn't seem to be working at all with any remote (or on another computer), let alone with XBMC. And now when I load up the GUI, the firmware version always displays as "v-16.-16" Trying to force update the firmware again locks up the GUI. And if I read correctly there's no other way for me to change the firmware now?

"Builtin Profiles" is ticked. I guess I could disable and enable it, but it's that it's not working, it does work after sending another command.