Jump to content
Flirc Forums


  • Posts

  • Joined

  • Last visited

  • Days Won


Posts posted by yawor

  1. Have you programmed the wake key on the gen1? If you didn't then any known key is going to wake the PC. Still it's probably a bug that it also wakes it up upon receiving a signal from Flirc/Kodi profile when the built-in profiles are disabled. Try recording a wake button for gen1 so that only that single button wakes your basement PC.

  2. Do you want to transfer some data from your dive computer to the PC? If yes, then Flirc is not what you want, because it's not a generic IR receiver. Flirc is a specialised IR receiver which translates IR commands from a remote control to keyboard key presses. It doesn't allow access to RAW IR signal.

    If you mean something else than data transfer then please describe it in more details. I'm not familiar with this kind of equipment.

  3. Try using something different then. At least to try find the cause.

    If you don't have a Samsung TV, create a profile for some newer model in your Harmony and record few keys (especially the ones that you have problems with like direction keys). Samsung uses NECx2 protocol which works really well with Flirc. You can also try using LG or Panasonic TV profile.

  4. You can have multiple remote buttons assigned to the same key/function in Flirc. Just record the same key in the GUI multiple times pressing different remote button each time.

    So in your example, click on the Q key in the GUI, the software will ask you to press a button on the remote. Press the back arrow on the remote. The click the Q key in the GUI once again and when asked, press the circular arrow on the remote.

    When the keyboard key/remote button pair is saved into the Flirc, only the remote button must be unique. If it's not unique (it's been already assigned to some keyboard key) then you'll get an error that the button is already in use.

  5. You can only assign a single key combination per each individual remote button. A key combination is a normal key + optional modifier keys (shift, ctrl, meta/win, alt). There's a feature planned that will allow to create key sequences: one press of a remote button will execute a user predefined sequence of key presses, but it's not yet implemented.

    Why would you want to assign multiple keys anyway? Can you describe in more details what do you want to achieve?


  6. I'm not familiar with URC remotes and their software, so I can't help you with details, but like I've mentioned in my previous reply, just program the remote to control any device you don't actually have. As Flirc is a programmable device itself you don't need to program your remote in very specific way. For example, if you don't have a Samung TV, then add a Samsung TV to your remote. If the remote allows you to set every detail like a protocol used etc (instead of selecting a concrete hardware) then use a NECx1 or NECx2 protocol with some random device id value and add as many buttons you need with different function codes (again sorry, I'm not familiar with URC software so I don't know the capabilities of the remote).

    After you set up your remote, connect Flirc to your PC or Mac, install Flirc software if you didn't do this yet and open Flirc application.

    In the Flirc app you have a main menu with Controllers position. In that submenu, you have multiple controllers available. One of them is a Fire TV controller. To program Flirc, you press a button representation in the app and the app will ask you to press a button on the remote you want to have assigned to the function you've selected. You go through all the functions and that's it. You can also mix controllers in any way you want (the controller selection is not stored anywhere - it's just a view in the app). So after recording all the buttons on Fire TV controller you can for example go to Full Keyboard or Multimedia and record more buttons if you want or need. Every button you record is saved in the Flirc's memory, so you don't need to save anything.

    When you record your buttons in Flirc software, don't point your remote directly at Flirc from a short distance. It has a very sensitive sensor and doing that you'll cause your recorded signal to be malformed and may not work reliably in normal operation (when connected to Fire TV). One of the best ways to properly record a button is to point the remote in a different direction (for example at the ceiling), so the Flirc receives a signal that bounced off something instead of a direct one. In normal operation Flirc should be able to see the remote's signals even without a direct line of sight (mine is behind a TV hanging on a wall).

  7. Hi,

    You can only assign a single keystroke (key + optional modifiers) to a remote button. It's up to you and the software you're using what that keystroke is going to do.

    Looking at what you want to do I think I can assume that you're trying to do that in Kodi. You should check on the Kodi wiki, which key combinations are not yet used and then assign them to the red and yellow buttons on your remote using Flirc GUI software. You should use full keyboard controller in the GUI.

    Next you need to tell your Kodi installation to start a specific playlist when a key combination is "pressed". But to do that, you need to go to the Kodi wiki pages and research that yourself. You should definitely learn about keyboard.xml - it's a file that configures your Kodi keyboard mapping.

  8. You can set up almost any remote to control it. Just set up your remote to some device you don't have physically (so it doesn't interfere with other hardware you own). It can be some PVR or TV. For example, my remote is set up for some Samsung TV. Then you connect Flirc to the PC or Mac and use Flirc GUI software to map buttons on the remote to functions you need. There's a Fire TV controller in the app (in the controllers menu).

  9. 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).

  10. 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.

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

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

  13. 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.

  14. 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.

  15. 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.

  16. There are some solutions. For example, in Windows, you can assign a key combination to an application shortcut:
    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.

  • Create New...