Jump to content
Flirc Forums


  • Content count

  • Joined

  • Last visited

  • Days Won


Everything posted by yawor

  1. Flirc Case compatibility

    It should be also possible to use thermal paste, but not too much. Just a tiny bean on the center of the CPU. No need to smear it over the CPU, it'll get squished by the case. I'd use just a tiny drop of good, silver based paste like Arctic Silver 5. Another possibility is an elastomeric thermal pad, which is used on many box CPU heatsinks (a gray rubber-like pad). Something like that: https://www.3m.com/3M/en_US/company-us/all-3m-products/~/3M-Thermally-Conductive-Silicone-Interface-Pad-5519/?N=5002385+3294001841&rt=rud
  2. @grkblood13 you're using wrong URL for downloading the deb package manually. Try wget --content-disposition https://packagecloud.io/Flirc/repo/packages/ubuntu/xenial/flirc_3.9.12_amd64.deb/download.deb The packages are all the same so the one for xenial should still work. To fix the apt source, check /etc/apt/sources.list.d. One of the files there should contain a deb source added by the script. Edit that file and change the release code (artful) to xenial. Then run apt-get update and apt-install flirc again.
  3. Well, Flirc can't compete with EventGhost feature-wise, that's for sure. EG is far superior for complex scenarios. But it's also a Windows only solution and requires a software install and a lot of playing with configuration to achieve acceptable controlling scheme. On the other hand, Flirc can work without any supporting software on the host system. All that's needed is support for USB keyboards so it works with probably any operation system. It's also portable as the configuration is stored on the device itself. There's nothing stopping you from using EG with Flirc. You can use Flirc native keyboard capabilities and just augment it with EG for some more advanced features. Then the basic features would still work even when the EG exit due to some error.
  4. Alternate key presses fail.

    Let me first clarify the issue from your first post. If I understand correctly, for example the P key (for play/pause) works every second press of the button. At least that's what I've understood from "alternate key presses". If I misunderstood this then could you elaborate what exactly the issue is? If I understood this correctly, then recording the button twice should work. Did you clear the configuration before testing recording pause twice?
  5. Flirc SE - Gen 1 or Gen 2?

    Flirc SE is a gen1 device.
  6. Alternate key presses fail.

    With MCE remote you need to record each button twice, because the signal alternates between button presses.
  7. Disable LED on Flirc SE?

    Unfortunately there's not. It's directly connected to the USB port's power pins. You can use an electrical tape for example, to dampen the LED's brightness. Cut out a square and tape it over the LED. You can also use multiple layers to make it even dimmer.
  8. It's updated on the fly. The save/load configuration options are for backing up and restoring the config from a file.
  9. I'm not 100% sure but I think that the default play button for the built-in Kodi profile uses multimedia Play key, not the P key. That's why you don't see it. You can safely reprogram it to use the P key instead. Set up your Harmony to use the Flirc/Kodi profile and then open up the Flirc GUI, go to the Full keyboard controller and click on the P in the app. When asked, press the Play/Pause button on your remote. The logic is that the user configuration overwrites the built-in profiles, so you can reassign single or multiple buttons from the provided Flirc/* profiles.
  10. I think you've misunderstood how does the Flirc work. It doesn't need a "p" IR signal. Besides the few built-in profiles which are predefined for a quick start with Kodi or FireTV, Flirc doesn't make any assumptions regarding the IR signals. It doesn't care if you're using Harmony, some other universal remote or some dedicated remote for some device. It's up to you to teach it what it has to do with the IR signals sent by your remote. So, for example, if you want Flirc to "press" the letter "p", then you need to launch the Flirc software, go to Controllers menu and select Full keyboard. Then on the keyboard in the GUI, you press the key with P. It should start blinking and you should see a prompt at the bottom to press a button on the remote. So press the button on the remote you want to be associated with letter P. It (mostly) doesn't matter which device profile you configured on the remote. As long as you use the same after recording it should work. You don't press anything on your physical keyboard connected to the PC. The other issue is the fact, that the Flirc/Kodi profile doesn't fully work for you. Is it only a problem with Play/Pause? Do other keys work? Or maybe it doesn't work at all? Do you run Kodi on your PC or some Android box with USB port?
  11. There's no full keyboard profile for the Harmony remotes. If you need to use specific keyboard key or key combination you need to install Flirc software on your PC or Mac and use it to program your Flirc. Programming involves two steps. First step is to select a key (or key combination with ctrl/alt/shift etc) in the GUI. The second step is to press a remote button on the remote when you're asked to by the program. This operation associates the remote button you've pressed to the key combination you've selected in the first step. As for the manufacturer/device on your Harmony, you can select almost anything. Some combinations work better than others. For example, I'm successfully using some Samsung TV profile with my Flirc, but LG or Panasonic should also work well. You can play around and test which one works best for you. Just select a profile for a hardware you don't actually have (for example, if you have an LG TV then don't use LG TV profile for Flirc).
  12. Kodi+Desktop simultaneously

    Hi, You've explained it well enough the first time. And I stay by what written above. If you use a remote access method which interferes with the local access then you should look into separating local access into "seats". That way it should be possible to use Kodi with Flirc on one "seat", and whatever you want to use remotely on second "seat". Or you can change the remote access method to something that doesn't interfere with local access. For example, a VNC or TeamViewer would interfere with local access, but NX or X server over SSH wouldn't. You could also try playing with triggerhappy daemon for example. It can capture input from selected sources (like a specific USB keyboard) and then somehow redirect it directly to Kodi so it doesn't matter whether it has focus or not. You probably could use the remote call API in Kodi. The same which is used by the mobile apps to control Kodi from a phone.
  13. Flirc with Nvidia Shield 2017

    Hi, Let's clear some things out first: 1. I don't think the Nvidia Shield doesn't have any IR output. I think (but I may be wrong) latest version (2017) doesn't even have the IR receiver anymore (older ones had it). 2. Flirc is a fully configurable device, which acts as an USB keyboard. So any hardware which can be controlled with a keyboard, can be controlled with Flirc. You use it by first programming it in Flirc software: you map functions available in the software to buttons on your remote (select function in Flirc software and when asked press a button on the remote). This means you don't need to have any specific remote control at all, because you teach your Flirc device to work with your remote (there are some remotes that work better than others though). I'll skip the RF part of the question as Flirc doesn't have anything to do with RF. As for how well Flirc works with Shield, you need to look around the forum. You should even see one of the Shield threads just few ones below yours.
  14. Kodi+Desktop simultaneously

    Hi, How do you use your system remotely? If you use local X server and connect over SSH then there shouldn't be any interference. The same would be with older NX server/client. If you use something like TeamViewer for remote access then it would certainly behave like you've described. I think you should look into multiseat scenarios in Linux. Basically one system can be used by multiple seats at the same time. Each seat has its own, separated inputs (mouse, keyboard) and environment (no focus stealing). I'm not very familiar with such setups though so I won't be able to help you with implementing it. You can also look into other types of remote access, which don't emulate local inputs.
  15. Flirc2 setup problem

    Hi, Can you do the following? 1. In Flirc GUI, save the configuration to a file and attach it here. 2. In Flirc GUI in File menu, there's a Device Log option. It should open a log window in which you should see a checkbox named Enable IR debugging. Check it and then press some buttons on your Harmony remote (using the profile on the remote you're using with old Flirc and try to program new to). You don't need to start recording. Just press some buttons. You can try pressing each multiple times and also hold them for a moment. Then save the log to the file and attach it here.
  16. Send keyboard long press / not remote long press

    Then maybe you could use everything except power off through Flirc, but use only the power off from the original remote. I don't have the Harmony so I'm not 100%, but AFAIK it should be possible to do.
  17. Send keyboard long press / not remote long press

    Is there a reason why you're not using the ir receiver built into the dreambox?
  18. Send keyboard long press / not remote long press

    Unfortunately this is not possible. At least not right now. What exactly are you trying to use Flirc with?
  19. Send keyboard long press / not remote long press

    As long as you hold the remote button pressed, Flirc should also keep the keyboard key pressed.
  20. Search button from keyboard on Flirc

    @foto808 well, it's not that easy. It's not enough to send a hid report with specific hid usage, the device needs to first send a hid descriptor telling the host system what it is and what it does. If you send gamepad usage codes without first telling host system that you're a gamepad, the system won't know what to do with that report. Also many hid codes have extra payload like the X/Y axis position.
  21. NEC is slow because it's quite sparse timing-wise. The whole single frame is 108 ms long (when lead-out is included). This means that the signal is repeated every 108 ms when a button is being held down. With recent firmware versions you can try playing with Sony20 protocol. It's frame is only 45 ms long with lead-out. RC5 is not really that fast. Its frame is 114 ms long with the lead-out, so it's even slower than NEC. RC6 (and MCE which is in RC6 family) frame is 107 ms long with lead-out.
  22. NO_PUBKEY 3F0B7E963CBA18E3

    This repository is no longer in use. Please check https://flirc.tv/downloads for instructions how to add a new repository to your installation.
  23. Next gen flirc?

    Well, the wake up went through some significant changes, but I can't tell you with 100% certainty that 2nd gen is going to work better or worse in your case. The ability to wake the system up depends on many different components like motherboard, BIOS type and version, USB controller, power being delivered or not to USB ports on suspend/hibernate, the operating system, drivers and also other hardware being connected. If you search through the forum you'll see that after 2nd gen has been introduced and the wake up functionality has been added in one of the firmware updates, there were a lot of problems with it, where the 1st gen worked properly. And the implementation followed USB guidelines for wake up. Also in some situations, on the same hardware, it worked under Linux but had issues under Windows. Fortunately these issues have been resolved. I would say that if it doesn't work now (after all the work that went into that function), it's a high possibility that it's some issue with the computer or its configuration rather than the Flirc itself.
  24. Next gen flirc?

    There are few reasons why would you want to upgrade: Because of the hardware limitations of 1st gen, all new features will be only introduced to 2nd gen. Recently added support for long press and macros. Built-in IR LED which allows to send IR signals to other devices using command line util or through a released API. It's smaller and better looking :).
  25. Which Flirc model do you have? If it's 2nd gen one, then you can create macros using a command line tool (not yet supported in the GUI). But there's already a wake/suspend function you can use. It's in the GUI in Media keys controller.