Search the Community

Hi, I run flirc on debian with an harmony remote, but Flirc does run only one on two events. I used a macbook to program the Flirc with the latest app. By the way, it tells me there is a new version, but if i update, i still have 3.0.29 instead of 3.1.0. If i download the 3.1.0 from the website and install it, it's still a 3.0.29 version. My harmony remote is set to sent maximum events. If i dump events with thd, each event is repeated fastly by the remote : example : EV_KEY KEY_C 1 /dev/input/event0 # KEY_C 1 command EV_KEY KEY_C 2 /dev/input/event0 # KEY_C 2 command EV_KEY KEY_C 2 /dev/input/event0 # KEY_C 2 command EV_KEY KEY_C 0 /dev/input/event0 # KEY_C 0 command but, if i click on a button of my remote multiple times (not fastly, with many seconds between clicks), it does take only one click, but not the second, ok for the third, not the next one, etc.... I did check on my mac (with a text editor) and it does exactly the same as on my linux config: one key on two. Could you help me ? (my config is attached if it can help my_flirc_config.fcfg

Dear all I have the same wish to add Netflix and perhaps the propper back button on my harmony companion (with Hub). But I have no clue how I can add, change or even touch the great config file that was posted here, many thnaks for that, much apprciated!!! So I assume that you need some addtional app in order to touch and define your own command lines in the GUI right? I am not an IT person at all. Thats why I have these questions. I would like to learn if possible. Can someone guide me through here? But I have a problem since a few days. The direction button sends a command twice. So it jumps two steps instead of one step. I have delete the config file a installed again. But nothing happend. Can someone imagine why this is the case. Same with up and down. Press once it jumps two steps. I checked with other devices and everything works fine. Happens only in combination between Flirc and the Sunrise UHD Box. Many thanks in advance for anyone who can help me with the above topics. Nabil

I've installed the FLIRC drivers on a Windows 10 system (1903) and plugged in the device. I am attempting to use an RTI RP6 to send it infrared commands. The learning mode works fine. I bring up the keyboard controller, tell it I want to program the spacebar, press a button on the remote, that triggers the RP6 to send infrared to the FLIRC, and yes it has recorded. Nothing I do, however, seems to make it play back that space key press. It seems to me that I should be able to go into any textbox (a browser address box, for example, or a command prompt), press the remote key, and see a space typed there. Is that a valid test? And of course it does not strike the spacebar in Windows Media Player (which should jump to the next song). I have tried both JVC infrared commands and Samsung TV commands, but the record-but-don't-play issue persists. From reading other support on this issue it seems the usual recommendation is to just keep trying different sets of infrared commands from different possible remotes until it finally works. I guess I could do that, but it seems a bit too trial-and-error and I've already had two failures. Is there anything else to try besides that?

version 3.22.4 [3.22.4] Firmware Detected Version: v4.6.3v4.6.3 SKU: Flirc 2.0 [dori] Branch: master Config: release Hash: 0x93A109D3 I have two FLIRC's, I am recording on one and transmitting on the other. When I send this command, flirc_util.exe send_ir_raw 0,9012,4424,592,491,588,491,592,1607,588,491,592,486,592,491,587,491,592,487,592,1607,588,1608,591,491,588,1607,592,1607,592,1602,592,1607,592,1607,591,487,591,1608,587,491,592,490,588,491,587,491,592,486,592,490,588,1607,592,491,587,1607,592,1607,592,1603,592,1607,592,1607,592,1602,592 Nothing shows up on the Record FLIRC. I even tried looking at the IR Debug Logs, there is absolutely nothing. We are evaluating the devices for a substantial order, Could anyone look into this? Thanks!

So I am posting here since I don't really know where else to post. I am looking for a way to have my raspberry turn my old tcl tv on via IR commands. I heard a rumor that FLIRC has the ability to send commands on reddit, and would like to clarify this before I order one. My tv for lack of better words is a dumb TV, it does not support cec, auto power on when it gets power, wake on lan, ect. Ideally, I would like to program the pi to send a command to turn the tv on/off upon waking or going to sleep. I am not exactly interested in using a tv remote, and would much rather just use my cellphone to control this.

I just bought the Flirc and am trying to use flirc_util.exe send_ir_raw and it does not seem to be transmitting. Flirc can receive my TV remote key presses and the mapping is working perfectly, but when I try to transmit the codes back nothing happens. My phone camera can see the TV remote flash but not the Flirc. I also have a Pi set up with an IR receiver and transmitter. The Pi can see my TV remote transmit but not the Flirc transmission even if the devices are pointed directly at each other a few inches away. The software I am running is 3.22.4 and the firmware is 4.6.3. I am on Windows 10. I'm not sure if it matters if I have the GUI open or not while I do this so I tried it both ways. I'm getting errors in the debug in the GUI. The command I am running is flirc_util.exe send_ir_raw 0,9012,4424,592,491,588,491,592,1607,588,491,592,486,592,491,587,491,592,487,592,1607,588,1608,591,491,588,1607,592,1607,592,1602,592,1607,592,1607,591,487,591,1608,587,491,592,490,588,491,587,491,592,486,592,490,588,1607,592,491,587,1607,592,1607,592,1603,592,1607,592,1607,592,1602,592 Errors in the GUI: Wed May 8 2019 21:42:21 Flirc GUI Version v3.22.4 Operating System: Windows *** Device Disconnected *** *** Device Connected *** Firmware Version: v4.6.3 SKU: Flirc 2.0 [dori] Git Hash: 0x93a109d3 <3>ir_transmit_push(131): invalid timer value: 0 <3>ir_transmit_push(131): invalid timer value: 0 Errors on the command line (these errors aren't there when the GUI is closed): [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(208): recv timeout [E] lib/libflirc/firmware/fw_4.2.c _fl_transmit_raw(69): error sending data, ceck device log [E] util/flirc_util/src/ir_transmit.c send_ir_raw(85): error sending IR pattern Is there something I am doing wrong? Is there something different I should try? Thank you

I have the exact same issue, and it's the remote unfortunately. I've bought a Flirc 2 recently (the metal one) and I can see in the logs that it sends keys slowly. I see in the logs that there is 490-500ms wait time before presses. But on my remote the power button is blinking in red when I press a button and its way faster. It's a magic remote I got for my 49UK7550MLA TV. @yawor Can I do something about this? I can attach logs if it helps. I've tried to set inter key delay via the command line tool but it's not available for this firmware.

In my case, I program the FLIRC from a Win7 laptop so I plug it in while the PC is already up and running so that works fine. Once I plug it in my linux PC, when I power it up while the FLIRC is already plugged in (such as after a reboot), it is not seen at all, as evidenced by the total absence of the device in the dmesg log and even after, when using the lsusb command, it's exactly like the FLIRC was not plugged in. If I pull it out then and plug it back in, then it is recognized normally and works just fine. When I suspend the computer (which I do most of the time), it recovers nicely from that state. I could try powering up the laptop with the FLIRC already plugged in to see what happens, I haven't tried that yet. Thanks, Daniel, **Update: ok, I tried plugging into Win7 laptop first and then powering up and going into GUI. It was recognized. I also tried plugging the FLIRC back into the linux computer while it was in sleep, and it was not recognized after waking up the computer. That test may not be relevant but I still tried it out of curiosity.

I just got a flirc 2. Using it on a PI 3 running Kodi 18. I have successfully mapped buttons that are working in Raspbian Pixel desktop. They also seem to work in Kodi—except ENTER. Nothing I map to ENTER in the FLIRC GUI will send an ENTER command to Kodi correctly. it is crazy because I can see ENTER working fine in a terminal window. I open a command prompt, press my enter key on my remote, FLIRC receives this and lo and behold, I see the command prompt go to a new line. By that account it seems to work. So I launch Kodi and my other nav buttons work, but ENTER does not. Yet, I know Kodi is ready for ENTER because I have a physical keyboard connected for testing and I can press enter on it and it works in Kodi. i have tried disabling the built in profiles in the GUI, I have remapped other remote buttons to enter, tried it on the full keyboard module, I even tried loading the Kodi key mapper add-on to attempt a workaround, but even this does not work. I can map the button press with Kodi key mapper (it registers receiving it) but it does not work when I try to use it. I am stuck. What is going on with the ENTER key in Kodi 18 on the Pi? This is useless if I cannot get ENTER to work. Other than that, it is really cool! <EDIT> Well, I think I may have solved my own problem here. The IR command I was issuing for the ENTER key was getting sent as a 3x repeat. FLIRC must have been recording this in some odd manner and when issuing the ENTER, it would sometimes rapid-fire a string of them, four in a row for example. Changing the IR repeat to 1, re-recording/learning the command seems to have fixed the problem. At least I am able to generate ENTER commands in Kodi now. I have some reconfiguring as a decide how to orient IR blasters etc, but I think my issue was the multiple sends, the recorded result, and further multiplying the effect when re-sending the command once learned (Kodi was often getting a contextual menu "c" command instead of enter, but BASH would show four enters in a row most cases).

hello i finally understand how to do it, so i will post here so people that dont usually use the flirc_util.exe can do the same. To enable and disable flirc on your PC go to start, execute/run/search (depends on your windows version) and write CMD it will open command prompt window, then write cd your-flirc-directory - in my example i write cd C:\Program Files (x86)\Flirc and press ENTER then you write flirc_util.exe record toggle - at this moment flirc is waiting for you to press a button on your remote, choose the button you want to enable and disable flirc, and voilaaa, you can now enable and disable flirc by pressing your selected remote button

Just got hold of one of these - great little device. The issue I'm having initially is that I when I power on or select my Shield activity, it brings up the inbuilt Android menu on my TV. I think this might be related to the fact that pressing 'Menu' on my Harmony remote has the same affect. Maybe 'Home' is the command being sent to wake up the Shield, and my TV understands the same command? Has anyone else come across this? Is there a workaround?

Setup: Flirc SE, Logitech Harmony 650, Windows 10 I'm trying to perform initial programming of the Flirc SE. The only command that seems to work is the one that doesn't use USB (i.e., the power switch). I've tried to program a few other keys on the full keyboard profile and none seem to do anything. What's strange is that the programming step appears to work just fine. For instance, I use Flirc software to program the J key with my desired remote command. Flirc software gives the recorded successfully status. I try to use the J command afterwards and it doesn't work. Tried several keys, all the same effect. The key appears to program, but doesn't do anything afterwards. Closing Flirc software and/or rebooting PC has no effect. I also tried installing Flirc again. It seemed to reinstall without issue. Edit: Just tried Passmark Keytest to check the raw key presses. Nothing registers. At this point, my assumption is that I'm doing something wrong, possibly stupid. Please advise.

I purchased my mother a FireTv and I need 2 simple codes which are not on the fireTv profile. All she does is use it to watch cable. The whole FireTv interface is too much for her to learn all at once. The TV is plugged in to hdmi1. I've set the TV up so it always goes directly to the last input it was on. So whenever she turns it on, it will always go to cable unless someone else left it on another input. Right now she has to use 2 remotes. Her "universal" remote for cable and the firetv remote to turn the stupid thing on and off, and to adjust the volume. So I just need 3 codes. The 2 most import are volume up and down. Nice to have would be the following more complex codes: One to turn the tv on and off[I don't care if it is actually off or in "sleep" mode. It just needs to make the screen turn OFF.] Really nice to have would be a macro command to make it switch to the primary hdmi input.

The Back Command works as Exit. If I press it, the whole menu closes. I need the correct Back command to go one step back in the menu, not closing it. Can anyone help?

Just to reiterate, my understanding is that currently there is no way to initiate Voice Search using the current version of flirc_util (3.20.4) and flirc firmware (4.4.2 in Flirc 2.0). There are conflicting reports of what HID commands need to be issued for that to work. One article mentioned Windows key (0x65 on the keyboard), but that didn't work. Earlier in this thread it was mentioned that Shield uses command 0x221 from HID Consumer Table, but as expected, `flirc_util record_api 0 545` did not work as well. If anybody is wondering why you would want to click the Voice Search button on a remote without the mic, the answer is that this is not really a real issue - Shield TV supports generic USB mics, and you can also put the Shield Controller somewhere next to you (it has a mic; I have not confirmed if it's on all the time, but something is draining the battery like crazy). Also, if you are wondering why not just say "Hey Google" (current Shield TV firmware supports this as Experimental/Beta feature), my personal answer is that in this case at least a pair of Home Minis and multiple google pixels all wake up and try to help with the request, and while phones and Home Minis don't duplicate an attempt and record something like "responded on another device", they do not really communicate the same way to the Shield, so typically 2 devices (including Shield) simultaneously responds with drastically different results from different parts of the room and start acting as voice input to each other and then apologizing for not getting what I want to do. :) It's very fun to hear, but impossible to use. @jason Let me know if I am saying something wrong, and also if the functionality becomes possible at some point, would it be possible to make a reply here since this thread comes up in search a lot. It would be greatly appreciated, same all all the great work of your team!

Thanks... it looks like my posts are now visible to other users. To clarify, I'm active on another Universal Remote forum and have a media center project based around a win8.1 computer with Media Center Edition installed. My recent quest has been to find and test widely available USB IR dongles that can be used with programmable remote controls and post those findings to the above forum so that others with the same needs can locate and purchase the best option for use with PC's. In addition, part of my search is for an IR input dongle that does not require special software. It appears that while the Flirc and a couple of other brands are good options for that need, I'm finding, as with all other IR input options, there are confusions. The one HUGE asset that Flirc default driver has is it's ability to bring a PC out of a <sleep> state where the Microsoft "eHome" IR dongle drivers do not. Without installing any Flirc software or drivers, your Flirc receives and correctly inputs (apparently via generic HID) a number of the keys on Microsoft MCE remotes... specifically the numeric, cursor and "transport" buttons on those remotes. I was hoping that the Flirc could receive native HID keyboard keys sent with the MCE IR protocols such as the <space> key but that doesn't seem to be possible without installing and mapping the keys using the Flirc software (which I have done, tested and currently using) Again, the goal is to look for a "lowest common denominator" option. The Microsoft MCE remotes that I have all include a "PC" button that transmits the windows <sleep> key found on many PC keyboards. That command is not on your "MCE remote" nor on your "Full Keyboard" templates. (I was able to create it by programming <Ctrl-Alt-S> which triggers a shortcut to the windows command line for sleep) The other commands that I was hoping were natively available MCE commands such as <space> are available to be mapped using your "Full Keyboard" template. Thanks for the response and setting my profile free ;-) Beverly Howard

fwiw, the microsoft USB eHome IR dongle (for the windows MCE Media Center Edition) has the ability to transmit IR commands from windows. The better part of a decade ago, I successfully experimented sending IR signals with the eHome dongle using HIP software and tools from a site in Australia. http://www.byremote.com.au/HIP/Default.htmI Can't remember the details, but it was pretty straight forward to output IR commands to the dongle, so, I wonder if this software might be able to access the ir transmitter in the Gen2 Flirc. My goal at the time was to see if I could build a locally served html page with mapped images of remotes so that when a button on the image was tapped, the link associated with that button would trigger HIP to issue the IR command for that button to the eHome dongle which would then control the device associated with that remote image. Unfortunately, my low level programming skills were not up to the task and could not find anyone with the skills and the interest to help. Sound interesting to anyone here? Beverly Howard

On this HP PCI Express remote, the PLAY/PAUSE key is triggering the WindowsKey+P command on windows with my flirc set to default. I've been searching the forums to find a way to reprogram it with no dice. Any help would be greatly appreciated This is the error i keep getting when i try to program the Play/Pause Key with anything...

Hi, Just wanted to share my problems getting Flirc to work with a Harmony Elite and hub/blasters. Maybe it can save someone from countless hours of fiddling, which is what I had to do. Setup: - Windows 10 Pro - Flirc Streacom edition - Streacom case in a cupboard - Harmony Elite with hub and blasters - Flirc/Kodi profile in the Harmony software Problem: First, I checked the mapping of the Harmony keys in the Harmony software (they keys were based on Flirc Media Player). Out of the box the Flirc software didn't respond to the Harmony key presses so I had to record the keys. This is odd in itself, I believe. It then turned out that the Harmony sent multiple (and I mean up to four!) different signals for each key. I tried recording the second (and third and fourth) presses in the Flirc software, but that didn't work as the signals got mixed up (e.g. pause was space three times and P the fourth). However, in the command line (flirc_utils keys) all key presses had different codes. I tried noise cancellation on and off, a different profile in the Harmony software (media center PC) and other remotes (MCE, TV) with no success. As the Flirc is built into the case, it was too much of a hassle to try it with another PC. I also assigned the particular blaster to the activity in the Harmony software, didn't work either and even tried it with the cupboard open. Solution: Yet another remote (OPPO bluray) proved the solution. Using the full keyboard in Flirc, I programmed the buttons with the OPPO remote and I then proceeded to teach the keypresses of the OPPO to the Harmony using the Harmony software. Setting the Inter Key Delay in the Flirc software to 2 or 3 made navigation run smoothly. It's a ridiculously complicated procedure, which I'm convinced is due to the Harmony or blaster as Flirc is now running fine.

Hi, Please can anyone help me? I also own Flirc with the Sunrise UHD Box and I can not configure the buttons for the menu and the tv guide. I tried everything except the command lines but I do not understand how. When I try from my Mac, I always have a command response HELP :)

So if I get my codes from Global Cache library, can I just use your command prompt to insert them into my FLIRC?

This is great. Thank you so much Crack for the research and documentation. I've got it up and running, now tweaking and this saved me a ton of time. One small possible correction. In your PDF under the final section, step 6 says "In the FLIRC software, select Controllers, select Fire TV..." I presume you meant "Select Shield TV." Just checking in case there was really some command we are getting from the Fire.

I own the Shield TV 16GB 2nd Gen and the Shield TV Pro 2nd Gen (I'm not using the Flirc with the Pro as it has a built-in IR receiver). I struggled for some time to properly set up the Flirc and Harmony 650 but have found a solution that has worked for me. This is what works for me: Run the MyHarmony app. Add the device: Manufacturer: Nvidia Model: Shield The MyHarmony app will ask if it is the NVIDIA SHIELD TV. Tell it "Yes" and you should see a full array of options for the buttons. Program the MyHarmony remote's activities and buttons as desired. Adjust the Shield TV's "start" activity to include: Shield TV Home command Adjust the Shield TV's "stop" activity to include: Shield TV Back command Shield TV Home command Run the Flirc program in connect the Flirc to be programmed. Under "Controllers" select NVIDIA Shield: Program each of the functions. Under "Controllers" select Kodi: Program all functions other than the Shield functions programmed earlier.

Hi all, I am using my Flirc SE on an easyvdr distribution which is based on a Ubuntu 14.04.3 LTS. Installation is a no-brainer, and the command line works fine. The only thing is that there is no menue bar on the GUI. Please see the attached screenshot. Any good Idea on how to get the menu bar back again? I have no issues on any of my other, newer Ubuntu PC's. This appears when I start Flirc from console [W] gui/Flirc/src/main.cpp log_setup(131): flirc.ini not in the default location[E] gui/Flirc/src/device_log.cpp update_fields(139): updating fields, present: 0 [E] lib/libflirc/bootloader/bl_2.0.c fl_ver2_product_type(526): unknown or unsupported variant: 144 [E] gui/Flirc/src/device_log.cpp update_fields(139): updating fields, present: 1 Thanks, Hermann

Hi, Ad 1) It should. But you need to have that remote to first teach your Flirc to respond to its buttons. Keep in mind that there are some remotes which don't work well with Flirc, so first do some tests to be sure that the remote itself works correctly before configuring your Alexa device. Ad 2) You can use as many Flircs as you want with a single PC (or at least as many as the number of USB ports :)). These behave just like standard USB keyboard and you can use multiple keyboards without issues. Things to remember: - If you're using Harmony remote and built-in profiles, then make sure that only a single Flirc has built-in profiles enabled (in GUI in Advanced settings). 1st generation of Flirc (original USB one in clear plastic and Flirc SE) can only turn on/off all built-in profiles at once. 2nd generation Flirc can enable/disable specific profiles. If you don't use harmony, then just turn off all built-in profiles in all Flircs you use just to be sure. - You can't have multiple Flircs connected during programming/configuration (GUI or command line tool). To program each of your Flircs you should disconnect all other on that PC. - When programming your Flircs, be sure not to program the same buttons on the remote to multiple ones. If you do that, then all (programmed) Flircs will react to the button press and may send conflicting key presses to the system.