Jump to content
Flirc Forums


Popular Content

Showing most liked content since 09/23/2017 in all areas

  1. 1 point
    Hello all, I just recently purchased a Flirc, a device I have had my eye on for a very long time, and so far I am very happy with it. It is currently connected to my Windows 10 HTPC running Plex. I wanted to share a small AHK script which will do three things to prevent me from having to grab the PC keyboard when plex is closed/minimized, the volume is muted, or I want to minimize plex when using Netflix (TV App). Launch plex if it is not already running, maximize it, then full screen it if needed (Record button on remote > CTRL+SHIFT+F1) Note: You may need to update the plex directory if yours is not "C:\Program Files\Plex\Plex Media Player\PlexMediaPlayer.exe" Unmute and set the volume 100% (Volume Up on remote > CTRL+SHIFT+F2) Minimize Plex to prevent the button pushes in Netflix from doing things in Plex (Netflix button on remote > CTRL+SHIFT+F3) I hope this helps and let me know if you have any questions! Cheers, Ned FlircAssistant.ahk
  2. 1 point
    Fn key is not a modifier key in the same sense as other modifier keys like ctrl, alt, shift. Normal modifier keys are being processed on the USB host device (your computer or other device you connect the keyboard or Flirc to). When you press for example ctrl + F, the keyboard sends hid code for key F with modifier code for ctrl. Fn key is being processed on the controller which is built into the keyboard. When you press Fn + F12, the keyboard doesn't send hid code for F12 key anymore. It sends something that's dependant on the keyboard itself (different makers and models have different Fn functions on different keys). In your case, the Fn + F12 is the media key for Play/Pause. You can find it in Flirc GUI in Media Keys controller.
  3. 1 point
    Don't use that instruction. It's not valid anymore. To get new instructions, go to https://flirc.tv/downloads, select Linux, accept terms and click on the link. It'll take you to the page with current instructions. Follow the one for Debian based system.
  4. 1 point
    Some suggestions to make more script friendly, or just to improve security or missing things. flirc_util options: - format : does not asks for confirmation. It is dangerous. Any "delete all" action should ask for confirmation, if not overridden by a force switch. - keys : does not show which HID code is tied to the key index, if it is not recognized by the default listed keys (it always shows !). It should be anyhow a good practice to show the HID code used, even if the key is recognized. Perhaps by inserting a new column between "ID" and "key" columns, as the "key" column is of variable length and should be the last one. If this is to be implemented, then it would allow to "delete_index" the index bound to the shown HID code, when delete_index would have been fixed (it is not working right now). Scripts could retrieve the list of indexes bound to HID codes that way, and act properly. It should be a good idea, to have a "play_index" or "trigger_index" option, to emulate any recorded key in a script. That way, it should be possible to play a manually recorded special HID code (with record_api), and see if it works as it should, in any application that is receiving that special HID code. And everything without the remote. Keyboard layouts in GUI, do not allow for any special HID codes to be recorded (as numpad keys, for example). So you can emulate a numpad without a numpad in scripting. Inhibit the triggering of the newly recorded key, for, let's say, 1 second (put the FLIRC to sleep?). That way the computer may not sleep itself, just after recording the sleep command, which is annoying. And helps avoiding any side effects, by triggering the key, in the "recording environment" (Alt+F4 should be annoying too, in a Windows environment, as it closes the window). May be it is a side effect, as interkey_delay is not working, and I get lots of double keypresses with FLIRC. Keep the good work going on. It really is very valuable.
  5. 1 point
    Did you use an Windows MCE remote profile on the Harmony? If yes then either don't use it (or any other RC5 or RC6 ones) or you need to record each remote button twice. RC5/6 protocols have a toggle bit which changes for each consecutive button press making the signal seen by the Flirc different.
  6. 1 point
    I found a program, keypose, that worked great. vic
  7. 1 point
    It would be nice to have the long press, but i've just got my harmony 650 working with Fire TV and Kodi, and everything is working great, so thanks a lot. I think this level of support on a 20 dollar dongle is fine to be honest. You can't be expected to support everything, and all those long press functions are available elsewhere easily enough. To be honest, I didn't even know there was a long press function until I read this thread trying to get it set up *shrugs*
  8. 1 point
    Don't believe this... but after a fresh bout of googling I've just solved it. The MSI board has bloody jumpers which, by default, disabled the Wake from USB !!! Just had to take it to pieces, reset the jumpers, and now its working fine. Hope this can help anyone else with the same issue :)
  9. 1 point
    Hello, Here a new config file with the numbers : Flirc_18.09.17.fcfg You can add the numbers without a keyboard, just by selection the Full keyboard from the Controllers Menu :
  10. 1 point
    The basics of how it all works, just in case: Start with the Harmony config since this seems to be tripping you up. You only need to pick one device for your Shield profile, and (ironically enough) you don't want to pick "Shield TV" WITH the Harmony since that profile is for models that have IR (or WiFi/BT if you have the Harmony hub) and you don't want that since you are using a FLIRC. Just pick something that has a lot of buttons available (for flexibility) and won't interfere with any other devices you have. A lot of us here us the ViewTV AT-163 profile. Pick it and name it whatever you want, like "Shield TV" :) Now your Harmony is programmed to send IR signals for all (or at least most) of it's buttons. *It doesn't matter what those signals are* as long as they are each unique and don't accidentally trigger other equipment (which is why the AT-163 is a good choice....unless of course you have one :) ). All that matters is that when you press a button, a unique IR command is blasted out. The FLIRC will do the rest. Now, the FLIRC. The FLIRC dongle takes those discreet IR signals and translates them to commands the Shield TV understands. When you program the FLIRC via its application and assign IR commands to buttons you want to make sure you use the Shield layout first, for the basics, because Jason updated the software with the correct commands the Shield needs. Specifically, the "ok" button now functions correctly cross-app. So choose that profile and manually (don't click "Go" and have it do it automatically, that will map some commands you want for Kodi later twice) click each button, then press the corresponding button on your Harmony remote to map it. Basically, the 4 directions, the "ok" button, the back button, and the home button. Pick the buttons on your Harmony you want to do those functions (should be obvious) and have at it. Once you've done that, bring up the Kodi layout. Now you can program buttons for things like Play, Pause, ff/rw, etc. If you want even more control, skip the Kodi layout and use the full keyboard layout instead. Pull up (or print) this page for reference: http://kodi.wiki/view/Keyboard_controls . That's a complete list of keyboard shortcuts for Kodi. You can assign buttons to whatever keys on the keyboard you want. Don't forget that with most Harmony's you can also create custom buttons if you want to map advanced stuff, like for subtitles. Again, it doesn't matter what IR commands are assigned to the Harmony for each button, as long as it is discreet! The FLIRC is going to take whatever IR signal you sent it and translate that to the correct keyboard command. Doing this will give you: Basic Shield remote functionality across all applications (except voice control, since there's no mic on the Harmony.) Advanced keymap control for apps that support full keyboard commands - like Kodi. Get it?
  11. 1 point
    OK. I was able to get it working by right clicking the Flirc device in the Device Manager and select Update Driver Software. Then select Browse My Computer and point it to Program Files (x86) > Flirc > Driver > usb_driver All working good now.