Search the Community

Can you describe this a bit more. Do you mean you recorded the command with flirc and my software?

Hi I just bought a Flirc v2 I have successfully mapped an IR remote button to keyboard functions using the GUI app This is the device log: Wed Aug 18 2021 16:34:58 Flirc GUI Version v3.25.3-15-gc366d26+ Operating System: Windows *** Device Disconnected *** *** Device Connected *** Firmware Version: v4.9.3 SKU: Flirc 2.0 [dori] Git Hash: 0xcb185bde I want to record some macros, but I'm getting errors with the flirc_util.exe I did these steps: Format the Flirc (to clear all settings) Attempt to record a key "h", but I get an error before I had time to press any IR remote buttons I then ran the "settings" command and got what appears to be multiple errors I need to know if my unit is faulty (so should be exchanged), or if there is another problem (and solution). My system is windows7 I have posted the CMD prompt info below - note the commands were issued one after the other Cheers Steve C:\Program Files (x86)\Flirc>flirc_util.exe format Formatting Device, please wait... Done! C:\Program Files (x86)\Flirc>flirc_util.exe record h Press any button on the remote to link it with 'h' [E] lib/libtransport/transport.c _dev_send_cmd(223): Wrong response: 'getversion' Error, button exists C:\Program Files (x86)\Flirc> C:\Program Files (x86)\Flirc>flirc_util.exe settings 3.25.3-16-g28e8a01+ FW Version: v4.9.3 [E] lib/libtransport/transport.c _dev_send_cmd(223): Wrong response: 'getversion' [E] lib/libflirc/firmware/fw_4.0.c fl_ver4_header_peek(50): invalid address you idiot [E] lib/libtransport/transport.c _dev_send_cmd(223): Wrong response: 'getversion' [E] lib/libflirc/firmware/fw_4.0.c fl_ver4_header_peek(50): invalid address you idiot [E] lib/libtransport/hid.c hid_recv_packet(167): hid_recv_packet: wrong report id [E] lib/libtransport/hid.c hid_recv_packet(168): hidapi: (null) [E] lib/libtransport/transport.c _recv_packet(126): _recv_packet: recv packet error = -1 [E] lib/libtransport/transport.c _dev_send_cmd(201): recv timeout [E] lib/libflirc/firmware/fw_4.0.c fl_ver4_header_peek(50): invalid address you idiot SKU: Flirc 2.0 [dori] [E] lib/libtransport/hid.c hid_recv_packet(167): hid_recv_packet: wrong report id [E] lib/libtransport/hid.c hid_recv_packet(168): hidapi: (null) [E] lib/libtransport/transport.c _recv_packet(126): _recv_packet: recv packet error = -1 [E] lib/libtransport/transport.c _dev_send_cmd(201): recv timeout [E] lib/libtransport/transport.c _dev_send_cmd(223): Wrong response: 'h_peek' [E] lib/libtransport/hid.c hid_recv_packet(167): hid_recv_packet: wrong report id [E] lib/libtransport/hid.c hid_recv_packet(168): hidapi: (null) [E] lib/libtransport/transport.c _recv_packet(126): _recv_packet: recv packet error = -1 [E] lib/libtransport/transport.c _dev_send_cmd(201): recv timeout Hash: 0x00000001 Settings: sleep detection: always enabled noise canceler: always enabled inter-key delay: N/A for current firmware variant: Flirc builtin profiles: NA Memory Info: NA [E] lib/libtransport/transport.c _dev_send_cmd(223): Wrong response: 'getversion' [E] lib/libflirc/firmware/fw_4.0.c fl_ver4_header_peek(50): invalid address you idiot [E] lib/libtransport/transport.c _dev_send_cmd(223): Wrong response: 'ir_state' [E] lib/libflirc/firmware/fw_4.0.c fl_ver4_header_peek(50): invalid address you idiot not a valid image product sku: NA [E] lib/libtransport/transport.c _dev_send_cmd(223): Wrong response: 'h_peek' [E] lib/libflirc/firmware/fw_4.0.c get_config(101): command error [E] lib/libflirc/firmware/fw_4.0.c fl_ver4_display_config(960): couldn't get config Records: NA

It was on both. I've connected it directly to a USB port on the PC. Still no joy. Very flakey . My application is a web accessible remote remote. I've got a little web page with a pile o' buttons that wrappers flirc_util in shell mode to "sendir" commands to control my cable box. Here's an interesting observation, manually running the send_ir commands it turns out it works much better if the GUI isn't running, See below. ########## GUI not running ##################### <5,521,2160,516,2165,520,2160,516,2165,520,4408,525,2155,520,4408,524,2157,518 Transmitting IR Pattern...Done! <5,521,2160,516,2165,520,2160,516,2165,520,4408,525,2155,520,4408,524,2157,518 Transmitting IR Pattern...Done! <5,521,2160,516,2165,520,2160,516,2165,520,4408,525,2155,520,4408,524,2157,518 Transmitting IR Pattern...Done! ############ Turned on GUI ################# <5,521,2160,516,2165,520,2160,516,2165,520,4408,525,2155,520,4408,524,2157,518 Transmitting IR Pattern...[E] lib/libtransport/hid.c hid_recv_packet(167): hid_recv_packet: wrong report id [E] lib/libtransport/hid.c hid_recv_packet(168): hidapi: The parameter is incorrect. [E] lib/libtransport/transport.c _recv_packet(126): _recv_packet: recv packet error = -1 [E] lib/libtransport/transport.c _dev_send_cmd(201): recv timeout [E] util/flirc_util/src/cmds/ir_transmit.c sendir(112): Error: could not transmit data Done! flirc_sudo.exe $ I'll try to do some more debugging. In the meantime can you tell me how to find the Flirc device in Device Manager so I can verify the proper driver is being used?

I'm having an identical problem. Interesting this is it "WAS" working fine. I'm at a lose to determine what has changed. I've unistalled and reinstalled a couple of times and reloaded the flirc firmware. WIndows 10. The device disconnects and reconnects after every yril cmd. :\Program Files (x86)\Flirc>flirc_util.exe settings 3.26.0 FW Version: v4.9.3 [E] lib/libtransport/transport.c _dev_send_cmd(223): Wrong response: 'getversion' [E] lib/libflirc/firmware/fw_4.0.c fl_ver4_header_peek(50): invalid address you idiot [E] lib/libtransport/transport.c _dev_send_cmd(223): Wrong response: 'getversion' [E] lib/libflirc/firmware/fw_4.0.c fl_ver4_header_peek(50): invalid address you idiot [E] lib/libtransport/hid.c hid_recv_packet(167): hid_recv_packet: wrong report id [E] lib/libtransport/hid.c hid_recv_packet(168): hidapi: The parameter is incorrect. [E] lib/libtransport/transport.c _recv_packet(126): _recv_packet: recv packet error = -1 [E] lib/libtransport/transport.c _dev_send_cmd(201): recv timeout [E] lib/libflirc/firmware/fw_4.0.c fl_ver4_header_peek(50): invalid address you idiot [E] lib/libtransport/transport.c _dev_send_cmd(223): Wrong response: 'ir_state' [E] lib/libflirc/firmware/fw_4.0.c fl_ver4_header_peek(50): invalid address you idiot SKU: Flirc 2.0 [dori] Branch: master Config: release Hash: 0xCB185BDE Settings: sleep detection: always enabled noise canceler: always enabled inter-key delay: N/A for current firmware variant: Flirc builtin profiles: NA Memory Info: NA product sku: Flirc 2.0 [dori] C:\Program Files (x86)\Flirc>flirc_util.exe unit_test [E] lib/libtransport/transport.c _dev_send_cmd(223): Wrong response: 'ir_state' [E] lib/libflirc/firmware/fw_4.9.c fl_ver4_set_record_api(108): command error [E] lib/libtransport/hid.c hid_recv_packet(167): hid_recv_packet: wrong report id [E] lib/libtransport/hid.c hid_recv_packet(168): hidapi: The parameter is incorrect. [E] lib/libtransport/transport.c _recv_packet(126): _recv_packet: recv packet error = -1 [E] lib/libtransport/transport.c _dev_send_cmd(201): recv timeout [E] lib/libtransport/hid.c hid_recv_packet(167): hid_recv_packet: wrong report id [E] lib/libtransport/hid.c hid_recv_packet(168): hidapi: The parameter is incorrect. [E] lib/libtransport/transport.c _recv_packet(126): _recv_packet: recv packet error = -1 [E] lib/libtransport/transport.c _dev_send_cmd(201): recv timeout [E] lib/libflirc/firmware/fw_4.2.c _fl_unit_test(141): error recording Flirc Not Okay [E] lib/libtransport/transport.c _dev_send_cmd(223): Wrong response: 'ir_state' *** Device Connected *** Firmware Version: v4.9.3 SKU: Flirc 2.0 [dori] Git Hash: 0xcb185bde *** Device Disconnected *** *** Device Connected *** Firmware Version: v4.9.3 SKU: Flirc 2.0 [dori] Git Hash: 0xcb185bde *** Device Disconnected *** *** Device Connected *** Firmware Version: v4.9.3 SKU: Flirc 2.0 [dori] Git Hash: 0xcb185bde <3>report_callback(227): pkt recv err <3>report_callback(227): pkt recv err

Terminal output: $ DEBUG=true /Applications/Flirc.app/Contents/MacOS/Flirc dyld: Library not loaded: @executable_path/../Frameworks/libusb-1.0.0.dylib Referenced from: /Applications/Flirc.app/Contents/MacOS/Flirc Reason: no suitable image found. Did find: /Applications/Flirc.app/Contents/MacOS/../Frameworks/libusb-1.0.0.dylib: cannot load 'libusb-1.0.0.dylib' (load command 0x80000034 is unknown) /Applications/Flirc.app/Contents/MacOS/../Frameworks/libusb-1.0.0.dylib: stat() failed with errno=1 /Applications/Flirc.app/Contents/MacOS/../Frameworks/libusb-1.0.0.dylib: cannot load 'libusb-1.0.0.dylib' (load command 0x80000034 is unknown) /Applications/Flirc.app/Contents/MacOS/../Frameworks/libusb-1.0.0.dylib: stat() failed with errno=1 Abort trap: 6 What timezone are you in? GMT-7?

Trying to figure out how to use the flirc to send IR commands is pretty daunting. For starters, the blog post won't load: http://blog.flirc.tv/index.php/2017/08/06/sdk-release-linux-rpi-ir-transmit-support/ I've tried to cobble together various ways to do it, but I have seen three different flirc_util commands mentioned that don't work, finally finding the one that currently works with software version 3.25.3, which is the "sendir" command. My use case I would think is common, I want to use a remote to control a device the remote doesn't support, so I want Flirc to receive one command and transmit another. I'll program my remote to control some arbitrary device it supports, then have the Flirc send a different command that controls my actual device. In my case it's my LG TV remote that I want to use to control the volume on an amplifier, but the LG remote doesn't support it nor does it have a learning function to control arbitrary devices. To get started on a proof of concept, I can use the GUI device log to capture the IR sequence I want to transmit. I press a button on my remote and the device log will show something like: :e:17031 0,9008,4393,614,475,615,470,615,470,615,1584,615,474,615,470,615,470,615,1584,619,1584,614,1584,619,1584,614,470,615,1588,614,1584,614,1589,614,479,605,470,615,1584,618,1584,615,470,614,474,615,480,605,1583,615,474,616,1583,617,472,610,474,615,1584,614,1588,625,1573,615,474,615,1584,615 :e:40 0,9007,2157,614 The long string there is the IR code I guess (I really don't know what I'm doing here). I can then transmit this code by doing something like: flirc_util.exe sendir --ik=23000 --repeat=3 --pattern="0,9003,4390,619,470,614,470,614,470,614,1588,614,470,614,474,614,470,614,1588,614,1582,614,1588,614,1587,614,470,614,1588,614,1583,614,1587,615,469,615,474,610,1587,615,1587,615,469,615,470,614,474,615,1583,614,474,614,1583,614,474,610,474,614,1584,614,1587,615,1587,614,470,614,1583,618" This is enough for me to write a simple script that can be triggered with a keyboard press, but I suspect it will be slow and I'll need to dust off my ancient or now non-existent C skills and see what I can do. What would be end game for me is if I could flash the flirc with my own custom firmware and then connect the flirc to power and use it standalone without any PC. Is something like this possible? Assuming it's not possible, I have a Raspberry Pi Zero W on the way to control the flirc instead. I'll report back when I've got my setup in production, but hopefully the above will save someone some time.

Is setting sensitivity still supported in the command line? flirc_util.exe help doesn't list anything related to sensitivity. Thanks in advance!

It's the same product as the black magic probe, which is 70 dollars. I wanted something cost effective, and shared it. If you can't figure this out, you wont figure theirs out, because it's literally running the same firmware. A 55 dollar difference. Here is the correct command: dfu-util --device ,1d50:6017 -s 0x00002000:leave -D blackmagic.bin Please be kind on my forums.

I have been using Flirc for my application for almost 2 yrs now, and I have have no issues with both Flirc devices to receiving commands from my remote controls. I wanted to try sending an IR command and the device doesn't seem to send anything. I have 2 Flirc devices with the latest release (Firmware Version: v4.9.3, SKU: Flirc 2.0 [dori]). (BTW, I am working on Windows 10) When I execute the command line: flirc_util.exe sendir --pattern="0,1,2,3,4,5" --repeat=3 (the content of the pattern is irrelevant) Output is : "Transmitting IR Pattern...Done!" The GUI log states: *** Device Connected *** Firmware Version: v4.9.3 SKU: Flirc 2.0 [dori] Git Hash: 0xcb185bde <3>ir_transmit_set(140): error, ik delay: 0 < 13000. Defaulting to 40000 The outcome is the same whether I have "enable IR Debugging" set or not. Since I have 2 Flirc devices, I connected them to 2 different computers and positions the flirc devices within inches of one another. I started the Flirc GUI on the second machine, and the log view never displays anything when the above command line is executed from the first computer (regardless of whether "enable IR Debugging" is set or not.) When I point any remote control directly at either Flirc devices, then there is an output generated in the log (when "enable IR Debugging" is set). Therefore, I seems that my devices are clearly able to receive input, but don't appear to be transmitting. Is there suppose to be any visual indicator when a Flirc is transmitting? Is there any other permission or setting I need to set? Perhaps, the version of the devices that I have don't support IR send? Any advice? Thank you

I have just received my new (metal) flirc. I still have my old (plastic) flirc. The windows (V2.02) software works with both, but I'm using the flirc on a RPi zero, and it's missing the odd key press from my remote. Previously (when I had this issue with the plastic flirc) I added key presses in-situ using the flirc_util cli. I have downloaded the latest Linux_util.zip, but it's still v1.4.4 and doesn't work with the new flirc (this is the statically compiled rpi version). Any idea when the rpi versions will be updated to V2?

Hi Jason, spent about 2 hours trying to program the "Power ON" command: NO GO The command worked only for "Power OFF" but not for "power ON" when I programmed the button under Shield G.2 or media Keys controllers. Interestingly, that the list of IR Hex codes for MiBox contains a Hex code for discrete "Power OFF" that works every time on MX-780 but the Hex code for "Power ON" does not work well at all- it may work one time in 10-20 tries... Too bad - the MiBox ticks all my boxes otherwise.

Is there away to program a power off button with the SE? Looking to have a separate power on and off button. Sorry if this has been asked before, did a search didn't find anything.

I am having trouble using the command line in OS X (Mac) I found flirt util at /Applications/Flirc.app/Contents/Resources/flirc_util Within that directory, tried flirc_util record pause command not found

This command does not work because the proper command is. flirc_util record print_screen The help page for record however states the proper term is printscreen. [kodi@kodi-bedroom ~]$ flirc_util help record Help for `record' command: usage: record '<keyboard key>' examples: flirc record a flirc record space valid commands: a-z <any single letter> return, enter, escape, backspace, delete, tab, space, F[1-12], printscreen, scroll, pause, insert, home, pageup, pagedown, end, right, left, down, up, Media Keys: wake, eject, vol_up, vol_down, mute, play/pause, stop rewind, fast_forward, next_track, prev_track System Keys: suspend Other: toggle [enbables/disables] flirc This is the version information, running on Manjaro via the flirc-bin git on arch AUR. Which I believe is just a repackage of the Debian/Ubuntu files. Version: flirc_util.release.v3.25.3 FW Version: v4.9.3 SKU: Flirc 2.0 [dori] Should be easy to fix. Either change the help text (also is wrong on the error page if you use the printscreen keyword) or have your case statement handle both terms. Not sure what it says in the manual, it may need to be changed in there as well. Hope this helps. Karl

Hi For debugging purposes, is there anyway to send IR presses to flirc (from a remote) and have it output the raw value it's receiving? (or hash of it) Kinda like a 'monitor' mode? Thanks

I was hoping to use the Flirc USB IR receiver as a way of adding a remote into my music server setup. I'm currently using Daphile as the platform for my server. It supports keybindings for player functions and I've tested it with a number of usb keyboards and it recognizes them all. Daphile recognizes the Flirc USB receiver as: "flirc.tv flirc Keyboard [usb-0000:00:13.0-1.3/input 1] " "flirc.tv flirc Consumer Control [usb-0000:00:13.0-1.3/input 1] " "flirc.tv flirc System Control [usb-0000:00:13.0-1.3/input 1] " however it won't capture key presses with any of these selected. What's strange is I was even able to control the local UI of Daphile with Flirc and a remote with buttons mapped to arrow and enter keys.... I believe Daphile is built on Gentoo Linux. I also tried using the Linux command line flirc_util options (enabling/disabling USB modes, etc.) but nothing seemed to change. Any help/suggestions/other firmware or configuration recommendations would be appreciated! Thanks!

Finally found a work-around. Apparently the first section of the command line is disregarded and not interpreted as a command if and only if it equals flirc_util.exe. I was using flirc_util <command>, not flirc_util.exe <command>. Everything works exactly as expected when including the .exe extension. Maybe this could eventually be adjusted to handle both cases (with and without the .exe extension)? Just a suggestion.

Just bought a Gen 2, and after installing the software I tried to use the command line utility and found that there seems to be a bug in how the command line is parsed. Every time I try to use the utility, no matter what I put after the executable name I receive the same error message: [E] lib/libcmds/cmds.c run_cmd(275): could not find command 'flirc_util' Looks like it is considering the name of the executable as the parameter. I double-checked by renaming the executable to 'help.exe', and sure enough I got the output I would have expected from 'flirc_util help'. I renamed it to 'version.exe' and I appear to have version 3.25.3-16-g28e8a01+. I'm running Windows 10. Is this something that can be looked at for the next software release? Alternatively, am I being very thick-headed and doing something amazingly wrong? Thanks!

I am using a Harmony 650 with a Flirc to control RasPlex. My TV is a Panasonic ST60 (TC-P60ST60) which has some Smart TV features. I typically leave my RasPlex sitting on the movies screen. When i do this, I noticed whenever i have the Harmony change activities that RasPlex is receiving a delete file command. When I switch activities to the RasPlex, if it was on the movie wall, I have a confirmation window sitting there asking if I want to delete these files. By running help on the remote, i was able to track down the offending command to "Panasonic TV Viera SmartMENU set to OFF". This command is not shown anywhere within the Harmony software. I put the Flirc into my PC and ran the GUI to see if it would pick up which key was being pressed but no matter which profile i picked in the GUI, it didn't show a keypress when I forced the SmartMENU set to OFF command. I clicked erase in the GUI and sent the SmartMENU set to OFF command but that didn't help. Additionally, after the SmartMENU set to OFF command is sent, a second command called "Panasonic TV HomeScreen set to OFF" is sent which appears to trigger the enter/OK key on RasPlex. Like the other command, the Flirc GUI doesn't register a keypress when i send the command with the Flirc plugged into the PC. I tried changing the Inter-Key Delay on both the Flirc and the Harmony as well as setting repeat command to 0 on the Harmony. None of these has helped. I'm not able to find either the SmartMENU or HomeScreen set to OFF commands anywhere within the Harmony software to remove it from being sent. The only place i am able to actually see these commands is while running through the help on the remote. What should I look at next?

Sure, no problem. First of all, just for future reference, the FLIRC command-line utility has built-in reference for all commands it supports. To view a list of all supported commands, use the "help" command: flirc_util.exe help Please note that I am on Windows, hence the ".exe" part. You may not need it if you are on macOS or Linux. To view reference for a specific command, use the same "help" command, but after it specify the command you need reference for, like this (without the <> brackets): flirc_util.exe help <command> So, when you run: flirc_util.exe help sendir here's what you get: Help for 'sendir' command: usage: sendir <opts> sendir --pattern=0,153,1231,131 --repeat=3 --ik=32000 OPTIONS: -i, --ik set the interkey delay between rep. frames -r, --repeat number of times to repeat pattern -k, --kill kill any currently running transmission -p, --pattern send the comma delimited pattern Which means the correct way of sending out your code, provided that you only need to repeat it once, would be as follows: flirc_util.exe sendir --pattern=0,8978,4384,608,469,608,1592,608,469,608,464,613,1592,608,469,608,464,612,478,608,469,608,464,612,1589,612,465,612,1592,608,1593,612,464,613,473,612,1588,612,465,612,464,612,465,612,465,612,464,608,465,612,477,613,464,608,1592,612,1588,612,1588,612,1588,612,1589,612,1592,612,1592,612 --repeat=1

I am wondering the same. Would have been nice to share your solution once you figured. I am always getting "Error: must specify an option" when I am trying to send the ir signal using e.g. based on the above log file the following command: flirc_util sendir 0,8978,4384,608,469,608,1592,608,469,608,464,613,1592,608,469,608,464,612,478,608,469,608,464,612,1589,612,465,612,1592,608,1593,612,464,613,473,612,1588,612,465,612,464,612,465,612,465,612,464,608,465,612,477,613,464,608,1592,612,1588,612,1588,612,1588,612,1589,612,1592,612,1592,612 What am I doing wrong?

Android TV was launched last year and there will be more device coming using this platform. Flirc will gain alot of popularity on Android TV by adding many additional commands that factory devices do not provide. Unfortunately, Flirc is missing an important command that all Android TV devices use: Media Home key. Android TV uses this key to exit and go back to home screen from any apps. There is workaround (esc+tab) but it is not true Home key. any plans to add this command?

There are a number of situations where you may want to configure/control flirc from the command line rather than the GUI. For example, XBMCbuntu is made to boot directly to XBMC without ever displaying a desktop environment. You may also like to be able to modify your flirc configuration via ssh without interrupting an XBMC session. In this tutorial I'll cover some basic steps for getting started with flirc from a command line. INSTALLATION First, we'll install the flirc software. To do this, you need to add flirc to your apt-get sources. You can do this with any text editor. Easiest is probably nano: sudo nano /etc/apt/sources.list Scroll all the way to the bottom of the file (Ctrl+V is page down) and add these lines: # flirc deb http://apt.flirc.tv/arch/i386 binary/ Save your changes (Ctrl+X exits nano, prompting you to save. Hit Y for yes, and enter to save without changing the file name). Then update apt-get to include your new source: sudo apt-get update Now you can install the flirc software: sudo apt-get install flirc Now it's possible to run all flirc commands from the command line, including programming the device, backing up your configuration, firmare installs, etc. For a list of flirc commands, you can just type 'flirc' and press enter, or 'flirc help'. For help with a specific flirc command, use 'flirc help <command>'. FIRMWARE You'll want a place for storing flirc firmware and config files. Here's how I do it: Go to your home directory if you aren't there already (in Linux, the tilde (~) represents your home directory, so if you're using XBMCbuntu and logged in as the xbmc user, 'cd ~' will take you to your home directory). If you're using another computer to do all of this via ssh, your ssh sessions will start in your home directory anyway by default. Make a folder called .flirc: mkdir .flirc Go to your new folder: cd .flirc To pull down firmware 1.0: wget http://downloads.flirc.tv/fw/fw_1.0.bin (Optional) Linux tip: If you use 'ls' you will see that there's now a file called fw_1.0.bin in your ~/.flirc/ folder. I use 'ls -al' (or just 'll' on most Linux builds), as that will also show hidden files and folders (like the ones with dots (.) in front of them) and the list is formatted nicer and provides much more info than ls alone. To install the firmware, make sure your flirc is connected and run: flirc upgrade fw_1.0.bin I don't know direct addresses for beta firmware. I'm not sure if Jason wants those to be public anyway. If he does he can add them to this thread. Either way, I'll add a post about copying files to and from an XBMCbuntu box soon. Also, since the flirc software is now installed, you can get to the GUI if you really need to as well, by exiting XBMC and logging into xbmcbuntu from the log in window, using the same account/password as your xbmc account. Flirc will most likely be one of very few apps installed so it's not hard to find, and it looks the same on Linux as is does on Windows or Mac, but I really like using flirc from the command line honestly. It's really easy to use 'flirc delete' and 'flirc record <key>' to change buttons on the fly without interrupting your xbmc sessions.

I use a Harmony Hub remote. I have a PC running Windows 8.1 and it has Kodi and Plex and other programs on it. It has an FLIRC plugged in. The remote controls other media players, an ATV, Mac Mini and a NUC PC also running Win8.1 with an MCE receiver. I used the XBMC profile in the My Harmony app ( manufacturer FLIRC). The problem is I would like to add some commands that are not in the XBMC profile. I know how to reassign button commands. For example, suppose I wanted to assign the Command (Windows) key to a button. Somehow I would have to get that button learned. I assume this would be done both by the Harmony and by the FLIRC software? Can the built in profiles in the FLIRC firmware be modified and saved as a different profile ( so as not to wreck the built in profiles)? How? Can I use the Windows command from an MCE Remote to teach FLIRC that command? If I then use it will there be a conflict with the FLIRC computer and the MCE NUC? Thanks...philip

I recently got a Shield TV Pro (2019) and bought a Flirc USB so that I could use my Harmony 950 remote to work with the Shield with IR commands. I do not have the Harmony Hub. I updated the Flirc firmware on my PC, then followed these instructions to add Flirc+Shield TV as a Harmony device. This gets the arrow keys, Select, Back, and Home buttons to work, however several other buttons from the Shield remote don't work, even though they show up in the Harmony software as options: Power, Menu, Play, and Netflix. I can work around or ignore most of those, but I need the Menu button to work for Flirc to be of use for me. Is there something I missed? Or did anyone get their Harmony remote to pass the same command as the Shield TV remote's Menu button?