Jump to content
Flirc Forums


  • Content count

  • Joined

  • Last visited

  • Days Won


yawor last won the day on July 6

yawor had the most liked content!

Community Reputation

57 Excellent


About yawor

Profile Information

  • Gender
  • Location
    Warsaw, Poland

Recent Profile Visitors

4,471 profile views
  1. Hi, Ctrl and Win keys are modifiers. You can add them to any non-modifier key. Open Flirc GUI and go to Full Keyboard controller. In the app, click on the Ctrl key, then click on the Win key and then click on either left or right arrow key. Key sequences (or macros) are coming sometime in the future for 2nd gen Flirc and will allow sequencing multiple keys (for example it will allow writing a predefined word with a single button press).
  2. Disable Blue LED

    Hi, No, it's not possible to disable the LED as it's not controlled by the chip but it's connected directly to the USB power line. You can cover it with a piece of some tape. I think few layers of an electrical isolation tape should be able to block it effectively. I'm using that method on some other hardware which also has bright LEDs without the ability to disable them.
  3. To fully analyse the signal you need non-demodulating IR receiver so the analysing software is able to also detect carrier frequency and duty cycle of the signal. I'm not sure if RPi is able to do that given that the Linux running on it is not a real time operating system. Look at the AGirs project. It's a firmware for Atmel's Atmega microprocessors which supports both demodulating and non-demodulating IR sensors and is compatible with IrScrutinizer. I think it's the cheapest way of getting a receiver for signal analysis.
  4. Flirc doesn't keep original IR data. It calculates a hash value from an IR signal and stores it. The hash value is not reversible. You could use IR debug if you have newer Flirc (the metal one, 2nd generation). In Flirc GUI there's a log window where you can enable IR debug. It will print out signal timings as a series of comma separated numbers. Each number is a time in microseconds and it's high and low signals interleaved (first 0 is low, then high, low, high, etc). You would still need to find some tool to detect and decode protocol used. You could try using IrScruntinizer but it doesn't accept format IR debug uses so you'd need to somehow convert the IR debug format into one accepted by the software.
  5. ideas

    Flirc doesn't use neither pronto nor any other standard IR codes. It calculates a hash value from a signal using a proprietary algorithm, which is optimised for receiving and quickly recognising the signal, in opposition to pronto hex (or possibly other) which are primarily for generating and sending one.
  6. Kodi + Full Keyboard Controller+ Volume

    Yes, you've understood it correctly. Flirc only saves the keys you're recording, nothing else. By long press do you mean key repeat? So when you hold down the remote button, the function is being repeated? Or do you mean assigning a different function to the same remote's button when you hold it down longer?
  7. Kodi + Full Keyboard Controller+ Volume

    It's a fairly common misunderstanding of what the controllers are and how Flirc works. You don't need to stick to specific controller in the GUI. The controller you select is not stored anywhere in the Flirc itself. So you can have keys recorded from Full Keyboard one and then you can go to Media Keys like @jason said and record volume keys there. BTW I've moved the thread to correct forum section and removed the duplicate.
  8. If you want to know if Flirc is able to control your TV, connect an USB keyboard (can be either wired or wireless - but not bluetooth) and try controlling the TV with it. The keyboard should have multimedia keys - at least volume control ones, so you can check if you are able to control the volume. As for the LeEco remote, if it's an IR remote, there's fairly big chance that would work. But both Flirc and TV will get the signal at the same time so both will control the volume at the same time which may (or not) cause some issues.
  9. So - no FW update past 3.9 for Flirc SE?

    There's no v4 firmware for Flirc Gen1, as v4 is focused on features and fixes for Gen2. Latest firmware for Gen1 is 3.9.
  10. So - no FW update past 3.9 for Flirc SE?

    It means that Flirc SE (Flirc Gen1) doesn't support log output. It's only available on Flirc Gen2.
  11. Launching applications

    There are some solutions. For example, in Windows, you can assign a key combination to an application shortcut: https://www.cnet.com/how-to/open-programs-with-keyboard-shortcuts-in-windows-10/ Then you can record the combination you've assigned using Flirc GUI to some button on your remote. I've had mixed results with that method though. You can also use additional software like EventGhost or AutoHotKey. I think @jason is also working on some cross-platform application launcher, but I don't know the details.
  12. No S5 Mode whis FlircSE (Intel Mainboard)

    Please check if you've connected the power button cables in a correct order. Maybe you've swapped connections to the button and to the motherboard. Flirc SE emulates pressing the power button so there's no reason why wouldn't it work with some hardware.
  13. Show button mappings?

    Now I'm sorry, I'm not that familiar with Mac to help you with that issue. Maybe @jason will be able to provide some support.
  14. Show button mappings?

    You need to first open the terminal window and change the directory to the one where flirc_util is installed. When you are in that directory, then you can execute it by calling: ./flirc_util keys You could also modify your PATH so that you wouldn't need to change directory but call it in the terminal from any location (without ./ like above). Here's an example how to do it: https://coolestguidesontheplanet.com/add-shell-path-osx/. Of course you need to replace mysql path with the Flirc one.
  15. Show button mappings?

    @Park City Ken Flirc doesn't keep the information about the controller used when recording a button. Most controllers are just layers on top of the full keyboard controller - keys on them are just predefined keyboard shortcuts. For example, on Kodi controller, the Info key is just the "i" key on the keyboard. So most of the time, only information that can be displayed is a keyboard key combination assigned, not a specific controller function. The hex codes which are used by Flirc won't tell you anything useful. They are generated from IR signal using a proprietary hashing algorithm and are Flirc specific. You wouldn't be able to copy IR hex codes from some remote control related forums or websites and enter them into Flirc without having actual remote. Also at this moment there's no option to add a key with IR hash manually at all. You need the remote to do it. Regarding the flirc_util, to run specific command you call it like this: flirc_util keys