Jump to content
Flirc Forums

Search the Community

Showing results for 'SendIR command'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Flirc forums
    • Flirc Gen1 Sticky
    • Getting Started with Flirc
    • Remote Buddy 2
    • General Questions
    • How To
    • Show Off
    • Remote Controls
    • Ideas and Suggestions
    • Bugs

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Location


Interests

  1. i dont understand (just to be clear).. Unplug the device, Push the button, Plug it in while holding the button. continue holding the button while executing the command?
  2. I am trying to build the SDK on an M1 MacMini 2020 adn here is the results I am getting: xx@tvs-Mac-mini cli % make flirc_util [BUILDING] flirc_util.debug [CC] src/main.c [CC] src/prepost.c [CC] lib/logging.c [CC] lib/getline.c [CC] lib/dict.c [CC] lib/cmds.c [CC] lib/cmds_script.c [CC] lib/cmds_shell.c [CC] src/cmds/version.c [CC] src/cmds/flirc_cmds.c [CC] src/cmds/ir_transmit.c [LINK] buildresults/Darwin_arm64/cc/flirc_util/debug/flirc_util ld: warning: directory not found for option '-L../libs/Darwin_arm64/' ld: library not found for -lflirc clang: error: linker command failed with exit code 1 (use -v to see invocation) make[2]: *** [buildresults/Darwin_arm64/cc/flirc_util/debug/flirc_util] Error 1 make[1]: *** [debug] Error 2 make: *** [flirc_util] Error 2 I guess the Darwin_arm64 version of the library doesn't exist. I was wondering if there are any work arounds for this.
  3. Use this guide to derive the HID page and key code of an HID event device or original remote connected e.g. via USB, I2C or Bluetooth to a Linux PC, or to verify that your Flirc actually sends the events you expect. HID page and key code can be grabbed under Linux following these steps: 1. Find the event devices associated with your HID devices using "udevadm info -a <device>" with <device> walking through /dev/input/event*. There might be multiple devices for a single hardware component, e.g. for a Harmony Hub there is one for HID mouse events, one for HID keyboard events, one for HID consumer control events, one for HID system control events, ... 2. Monitor the desired event devices (usually requires root) using "sudo evtest [--grab<] <device>" for each device required. The optional parameter "--grab" is essential if you want to stop the recorded events to be forwarded to and interpreted by the system, like I did to stop my system going into standby whenever I sent the sleep event that I wanted to record. If you want to use "--grab" on your local keyboard or such, you might want to either attach a second keyboard or run the command over the network via SSH, so you can abort the monitoring by sending Ctrl+C. 3. Perform the key presses on the device you want to record. Each key press will emit 2 events, one for key down (press), one for key up (release), example output for the "0" key: Event: time 1593381762.020128, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70027 Event: time 1593381762.020128, type 1 (EV_KEY), code 11 (KEY_0), value 1 Event: time 1593381762.020128, -------------- SYN_REPORT ------------ Event: time 1593381762.020198, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70027 Event: time 1593381762.020198, type 1 (EV_KEY), code 11 (KEY_0), value 0 Event: time 1593381762.020198, -------------- SYN_REPORT ------------ 4. Interpret the output; you are interested in the value of the MSC_SCAN (scancode) of EV_MSC (miscellaneous) events. The value is hexadecimal and for HID devices with the last 4 digits being the HID key code (0x0027) and leading digit(s) the HID page (0x07). 5. HID page 0x07 events (HID keyboard) can be programmed using "flirc_util record_api <modifiers> <key code>", where <key code> is the decimal representation of the HID key code you fetched above (e.g. 0x27 = 39), and <modifier> is a logical or-ed list of modifier keys to be held down while <key code> is sent (see "flirc_util help record_api"). I ran into an intentional limitation of flirc_util, limiting <key code> to values <= 101. Unfortunately, flirc_util silently programs the key anyway without a warning, leaving a key that is never sent. This cost me a lot of time while trying to send the correct codes to my hardware, being the Flirc the culprit by never sending the programmed keys. Jason is currently checking whether the limitation will be removed.
  4. Hello dear authors of Flirc, I have just purchased the Flirc IR receiver and using it in conjunction with Remote Buddy 2 on macOS Mojave on a Mac Pro 5,1 and a Pioneer VSX909RDS receiver. Pretty old, but very good devices. Now I found the Remote Buddy IR signal recoding function to sometimes not record the right command, but after a couple of tries it usually works. But there is one command on the remote of the Pioneer that for some reason after recoding in RB2 and attempting to play it back hangs the Flirc. Attaching a Log file from Flirc GUI so you can see. Pioneer VSX909RDS Stereo Direct toggled many times.txt
  5. Hi all, I am trying to program URC MX-780 to power up/wake up my original MiBox (manually downgraded back to Android 8.0). After initial Xiaomi faulty upgrade of their MiBoxes (that made the box unstable and often unresponsive), I went back to using Roku which the MX-780 controls just fine. However, there is one custom app that cannot be loaded on Roku (Russian TV service that my mother watches). I was going to throw away the MiBox but found the tutorial on downgrading it back to original FW which worked and now I have fully functioning MiBox. I managed to upload Xiaomi Hex codes on the MX-780 and the remote controls the box just fine EXCEPT for the "power" command. The "Power Off" Hex code works just fine but I was unable to get "power ON" command to work. The same command ("Power ON") works 100 % of the time from the original BT remote. So I bought a USB Flirc hoping that I will be able to program it to reliably turn On the MiBox. Unfortunately, it was not the case: I tried programming under Kodi, Shield, Windows (wake command)- nothing worked so far. Have anyone managed to program gen.1 (original) MiBox to turn On/Off reliably using Flirc? If yes, what did you do? Thanks
  6. Hey All, Noob here, trying out new things. I am attempting to set up a magic mirror and would like to use my HomeBridge Broadlink IR blaster to shutdown my raspberry pi when I leave the house. If I set up the broadlink to send just the simple power command, if the pi is already off, the broadlink will turn the pi on when I leave the house- which defeats the purpose of trying to save energy. Before I buy it, can I program a Flirc USB IR Receiver to just send a shutdown command? and is there a guide that anyone can link to me please? Thanks!
  7. **** EDIT **** Hey guys, Jason here. Be sure to check out the bottom of this post for additional information that I made *************** **** DOUBLE EDIT **** Official Amazon firetv support added to the latest release candidate. It's very stable, and will probably go public: Is now in the stable firmware ********************************* Using Flirc with Amazon's fireTV. After finding bits and pieces of helpful info in various threads, I thought it might be helpful to start a new thread that combines what I've learned with a place for others to share their experiences. First, you wouldn't be here if you weren't frustrated with fireTV's Bluetooth remote control. The fact that they omitted an IR path to remote control is a major omission for AV enthusiasts who have labored to combine control of all their devices into one remote control. Enter Flirc. This little device is amazing. By using the Flirc and its software, it basically take whatever IR command your remote sends it and uses it as a trigger to send out whatever command you associated with it. For example: You could program it to send an Up command whenever you push the "1" button on your remote. Or you could program it to send a play command whenever you push the guide button on your remote. Of course it makes much more sense to program remote bottons that correspond to the actual command desired, but Flirc doesn't care! I’m using a Windows 8.1 desktop machine. I have no knowledge or access to a Mac or Linux. I have a URC MX980 remote. When I added a device for fireTV, I told the remote that it was a Panasonic DVD player and assigned commands from the Panasonic Remote to my MX980's keys. It really makes no difference what device you assign as long as your remote sends an IR signal when the desired key is pressed. Those signals become the trigger signals for Flirc. As it turned out, whenever I pressed up, down, left, or right, I got double key pushes on the fireTV. I tried changing the inter-key delay from the Flirc GUI - File > Advanced, but that didn’t help. So I assigned the arrow keys from an Apple TV remote to my MX980 and that fixed the problem. So far I have almost everything working. Obviously, the voice command feature isn’t a player. I still haven’t found a Home Key in the Flirc GUI that performs the Home function of the fireTV remote. The best that I have been able to do is a back command. From what I can tell, the play button alternates between play and pause. Separate pause and stop commands don’t work. I haven’t been able to test the skip+ and skip- commands so the jury is still out. Programming the menu key requires use of the windows command line program. There seems to be some confusion in the forums about reference to the command line app. It is not part of Flirc or the Flirc GUI, but part of windows. Now my level of knowledge pales in comparison to many of the members here, but this is what I was able to decipher. I found this page to help me learn about the command line commands: http://www.pcstats.com/articleview.cfm?articleid=1723&page=2 As I mentioned, the command line program cmd.exe Is part of Windows. You can get to it and number of ways depending on your version of Windows. Use it to navigate to: C:\Program Files (x86)\Flirc for 64 bit OS or C:\Program Files\Flirc for 32 bit OS then type: flirc_util.exe record_api 0 101 It will then ask you to point the remote and press the button you want mapped just like the GUI. Once you do that it will tell you that you were successful. Here is how I mapped my remote to the Flirc commands. The Controllers column refers to the Controllers menu in the Flirc GUI. There are several choices there and you will need 3 of them to duplicate what I have done. I don’t know if there is a difference between similar keys in the Media Center and Media Keys layouts. I did not take the time to test it. Maybe someone can post that info if they know. If they are the same, it would simplify things. Thanks to the other members who’s posts led me down this path to success If I missed something or made a typo, pls feel free to correct it! **** EDIT **** Hey guys, it's Jason hijacking Tony's post. The select button marked as 'enter' above which is in the GUI, is actually not correct. It must be 'return'. Do this with the commandline: flirc_util record return Just a heads up that I'm going to make life so much easier, I'm going to update the GUI with an official FireTV window. Hopefully I can do this by the weekend. Attached an image. ****************
  8. I’m a newbie to Flirc. Purchased it so I could control a 2019 Nvidia Shield Pro with my URC RF20 remote which controls equipment in a cabinet. Setup the Flirc on my iMac for the Gen 2 Shield remote and used an older, no longer used, Roku IR remote to record the key presses. Success! Then I discovered that the universal Samsung TV remotes Menu command also caused the Shields System Menu to open. And the Up, Down, Left, Right and Select commands as well. So I found a very old TDK CD Recorder remote and used its Display button to record the Shields System Menu command to see if I was on the right track. That didn’t work. I’m clearly not getting it so I’m asking for some guidance.
  9. Can you describe this a bit more. Do you mean you recorded the command with flirc and my software?
  10. Steve H

    Steve H

    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
  11. GerryD

    Steve H

    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?
  12. GerryD

    Steve H

    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
  13. 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?
  14. Unfortunately the documentation and support is rather lacking on this feature possibly due to lack of dev cycles anyway here is a "how to" of the " SendIR waveform function" from latest git as of feb 8 2021 on Ubuntu 20 x64: ( this guide assumes basic Linux know how, and may be invalidated over time due to updates to git) Side note: There exists other devices I bought like USB-UIRT which do a better job but have their own issues, flirc however I find a little easier to capture IR waveforms so has some uses the issue is the transceiver its not going to work unless your literally sitting the usb unit in front of the device you want to control. Objective: What is Send IR, its a way to remotely send Infrared signals directly outbound, as opposed to what Flirc was designed for which is mainly inbound device control. 1. You will need Ubuntu 20 or equivalent 2. You will need V2 of the Flirc Steps: a. install flirc using the known methods namely: Debian [64], Redhat [64bit], or Raspberry Pi Debian curl apt.flirc.tv/install.sh | sudo bash b. get git, sudo apt install git c. Make a directory and install and compile the sdk Commands from your home directory: cd ~ mkdir buildsdk cd buildsdk git clone https://github.com/flirc/sdk.git cd sdk cd cli sudo apt-get install libusb-1.0-0-dev libreadline-dev libhidapi-dev make all now your tool will be compiled in: ~/buildsdk/sdk/cli/buildresults/Linux_x86_64/x86_64_linux_gnu_gcc_10/flirc_util/debug/ And it is called flirc_util (latest version from git) d. Capture IR command signal Open the traditional Flic setup and control tool, my tool which was installed in step (a) is Flirc v3.25.3 it says connected as my flirc is inserted in the computer, if you cannot find it refer to installation again in step (a). open the app, goto File, drop down: click device log, click on the checkmark (x) Enable IR debugging. This will record all IR signals being sent to the flirc you will need this to create your IR commands. So Example: Mon. Feb. 8 2021 01:51:26 Flirc GUI Version v3.25.3 Operating System: Linux *** Device Disconnected *** *** Device Connected *** So lets say I want to record the power off, power on button for my heater; When I press power on/off button while pointed towards the flirc the waveform command is, captured and immediately shows up in the debugging window as: 0,9073,4414,618,1595,622,470,618,469,649,443,618,470,622,465,623,469,622,466,622,470,617,1596,622,1595,622,1595,618,1595,622,1595,622,1595,622,1594,618,1599,618,1594,622,470,618,1595,626,465,622,466,622,469,618,470,622,470,617,470,621,1595,618,469,622,1595,621,1595,622,1591,622,1595,622 Now you have successfully captured the IR signal. e. Send IR command signal in step C, you created the flirc_util from git so, Point the USB flirc at whatever device you want to control in my case heater now from command prompt goto ~/buildsdk/sdk/cli/buildresults/Linux_x86_64/x86_64_linux_gnu_gcc_10/flirc_util/debug/ and run this command: flirc_util sendir 0,9073,4414,618,1595,622,470,618,469,649,443,618,470,622,465,623,469,622,466,622,470,617,1596,622,1595,622,1595,618,1595,622,1595,622,1595,622,1594,618,1599,618,1594,622,470,618,1595,626,465,622,466,622,469,618,470,622,470,617,470,621,1595,618,469,622,1595,621,1595,622,1591,622,1595,622 Now in my case the heater if turned on turns off, and if the heater is off turns on, You have successfully transmitted the IR signal by the computer. Main use cases would be remote ( ie not even home) control of appliances and some robotics applications. Where you can remote into your computer from away and run scripts to control things, I guess use your imagination. Good luck
  15. 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.
  16. I found a way to do sort of do this in case you are comfortable using the CLI. (I'm also surprised this is not a native feature!) First, go to Flirc GUI and there go to File > Device Log. Turn on the Enable IR debugging checkbox and press a key on your remote against the Flirc receiver. There will be a number of new lines. Ignore the ones starting with a colon and look for a line with a long sequence of numbers separated by commas. Note that this line will most likely be wrapped around into multiple lines and it usually (maybe always?) starts with a zero - the zero is the first number of that sequence but the line will likely break right after it. Cope the whole sequence into your keyboard. Next up, find where the Flirc CLI is on your system, on macOS it is in /Applications/Flirc.app/Contents/Resources. Use your terminal to enter this directory and in it, run this command substituting your actual pattern from the Flirc GUI: ./flirc_util sendir --pattern="0,…" This will replay the recorded sequence using the IR transmitter in Flirc. I was able to verify this works by using a remote-controlled LED strip and recording one of the color buttons and then changing the color to something else with the remote and replaying the original color IR sequence using Flirc CLI and the LED strip consistently switched back to the recorded color. Hope this helps anyone! And also hope Flirc will kick the support up a notch, it almost seems like the product is abandoned :/ Which is a shame, because it is genuinely great.
  17. Hi all, Sorry if this was asked before- I searched but did not find anything to help me. I "managed" to program the Flirc USB to operate Fire TV stick, using Roku commands programmed into my Universal Remote MX-780. Everything works as it should. The Fire TV came with a basic remote, without "Netflix" or "YouTube" buttons. However, I see that Amazon now sells Fire TV remotes that have those buttons. For now, I programmed the "YouTube" command as a macro that has all power commands for my equipment and then calls for "1 sec. delay, home, Right x 3, enter", because the app is located first in the front row. However, this is a long command, so I would to have more "elegant" solution ...if at all possible. Thanks
  18. Hello, I just got the firc and an nVidia Shield. I have the activity for watching the plex to have the Sony TV, Marantz prepro and the nVidia Game Console (nVidia Shield). I programmed the FLIRC for Shield 2 and updated the firmware. When start the activity, it starts all the devices and the buttons work fine. I have a power toggle in the screen part of my harmony that works if for any reason I wasn't aiming in the right direction when I started the activity. When I power the activity down, it does power off the TV and the Prepro but it doesn't put the shield in standby or power it off. If I go to the activity, Customize activity, at the bottom there are activity shutdown commands. I select it and try to add a step for the device nvidia game console (I can't add an action, just a command) but for command there are no power or standby options. Anyone know a way around this (short of power toggling it manually before shutting down the activity?)
  19. I have been trying to get my FLIRC working with an MCE remote to interface to an older (non-MCE) app and have found the following. I go into the GUI, clear the configuration and uncheck all of the Build in Profiles (Side note: After exiting and restarting the GUI I sometimes find some or all of the Built in Profiles are now checked. Multiple retries will finally get them all unchecked). I then confirm using Notepad that none of the numeric keys on the remote are sending any commands. I return to the GUI and using the Full Keyboard controller, I map the "a" key to the "1" button, "b" key to the "2" button ...... "j" key to the "0" button. I return to Notepad to confirm operation and find I must press a numeric button twice to get a single letter. I simply want to send an "a" each time I press the "1" button and so on. How do I get that to work? Thanks, Bill Windows 10 Home Version 1909 (OS Build 18363.836) FLIRC GUI Version 3.25.3 Firmware v4.9.3
  20. 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.
  21. 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
  22. mostm

    Flirc and Daphile

    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!
  23. Hi, I've configured a One For All remote with Flirc to replace an Nvidia Shield 2019 remote. My problem is that I configured a button in the remote using the long press option and now, if I leave the button pressed too long, it sends the command twice. So in the end, I need to release the button the moment I see the Shield react to the command to avoid this issue. I've also tested with Kodi and it does the same thing. Is this a known bug? Thanks.
  24. Hello All, I got my first flirc (first two) in the mail today. The first one is for my HTPC (Windoze 7 Pro SP1). I'm running NextPVR and didn't have a working IR input for my Hauppauge 45 button remote. It was no problem to set up, the software works well (although a little time consuming). It seems that all the remote keys are working as I programmed them, to replicate the keystrokes used by NPVR. The trouble is it's only passing every-other remote command through to NPVR. I have to hit every remote button twice to get the response of one from the software. At first I thought I was pressing the remote buttons to fast, but I tried waiting over 10 seconds between presses, it didn't matter, it was still only sending every-other button press. My actual keyboard works fine with NPVR (how I have been using it so far). I saved my config and created a simple Minimalist config with the same remote that I tested with Win-dohs Media Center, which yielded the same every-other result. I've attached my files for both the NPVR config and the minimialist config, if that helps. Any thoughts? Thanks, -Brad H45_minimalist_flirc_config.fcfg H45_NPVR_flirc_config.fcfg
  25. I have a Flirc V2 running on a raspberry pi headless. Using the device log when I press the increase temperature button I get this (I just press the button one time but get what looks like to me to be two outputs): :e:0 371,454,375,454,372,453,372,453,372,423,406,424,405,424,406,484,354,454,375,454,371,454,376,454,371,454,1226,484,353,454,1226,454,371,458,371,454 :e:0 376,454,371,449,380,458,371,429,396,453,372,453,371,450,384,454,371,454,375,454,371,454,371,454,371,424,1264,454,371,454,1230,450,379,454,376,423 I am now trying to use the sendir command like this: flirc_util sendir --pattern="371,454,375,454,372,453,372,453,372,423,406,424,405,424,406,484,354,454,375,454,371,454,376,454,371,454,1226,484,353,454,1226,454,371,458,371,454" --repeat=1 --ik=40000 and I get this error: [E] util/flirc_util/src/cmds/ir_transmit.c sendir(101): Error: buffer should lead with zero But if I add a zero at the beginning like this, I get a different error: flirc_util sendir --pattern="0,371,454,375,454,372,453,372,453,372,423,406,424,405,424,406,484,354,454,375,454,371,454,376,454,371,454,1226,484,353,454,1226,454,371,458,371,454" --repeat=1 --ik=40000 [E] util/flirc_util/src/cmds/ir_transmit.c sendir(96): Error: invalid length, must be even I also tried recording the on/off button with similar results. I noticed the codes are always a little bit different everytime. Do you have any suggestions? Is controlling a minisplit something the Flirc can do? Thanks for the help!
×
×
  • Create New...