Jump to content
Flirc Forums


  • Posts

  • Joined

  • Last visited

  • Days Won


Posts posted by yawor

  1. Hi

    For Flirc to execute any function in Kodi, the function first needs to be assigned to some keyboard key or key combination in the Kodi itself. If you already have keyboard shortcuts assigned to the audio profile switching operations, then configuring this in Flirc is as easy as mapping direction keys for example (just use Flirc GUI to assign your remote's buttons to the keyboard shortcuts).

    As for the Kodi keyboard configuration and ability to even assign keyboard shortcuts to Audio Profile add-on, this is really not in the scope of this forum. You need to consult forums dedicated to Kodi (for example the official Kodi forum). You should look for instructions on how to add your shortcuts to keyboard.xml file and maybe ask the add-on authors to give some hints on what you need to call from the keyboard.xml file to switch the profile.

    After you learn how to modify the Kodi the way you want, just select 2 keyboard shortcuts that are not yet used by it and assign them to specific audio profiles and use Flirc GUI to assign the same keyboard shortcuts to your remote's buttons.

  2. @Cayprol in my opinion it's more an issue with OS than with Flirc itself. Flirc just sends a key press according to a HID standard. It's up to the system to interpret it and act on it. Maybe there's some setting in the Mac OS itself you need to change.

    I don't know Mac OS. Maybe @jason will know something, but he's currently heavily preoccupied with his family matters (mostly by new baby).

  3. If the hardware itself supports waking by USB devices then it should work out of the box. The feature is also software controlled so OS also needs to properly configure the motherboard when going into suspend to allow waking from USB (this usually happens by default unless there's some incompatibility between operating system and the motherboard hardware).

    You can test if the wake up function does work at all by connecting an USB keyboard and going to suspend mode. You should be able to wake your PC by pressing a key on the keyboard. If this doesn't work for you then Flirc also won't be able to do that. There may be an option in the BIOS/UEFI you need to enable.

    If you are able to wake your PC using USB keyboard then it also should work with Flirc.

    The old Flirc (the clear plastic one) may need some configuration. Open Flirc GUI and go to File menu and Advanced. Make sure that the Sleep Detection is checked. When it's checked then there are two modes of operation. By default Flirc will wake the PC upon pressing any remote key known to it (like I've mentioned in my previous post - this means any key that is recorded and recognised by Flirc). You can change that by going to Full Keyboard controller in Flirc GUI and recording the WAKE key. When the WAKE key is recorded, only that key will wake the PC.

    At this moment, the new Flirc (the metal one) has wake function enabled by default and supports only waking up by any known key. The WAKE key feature is going to be implemented but I can't tell you any time frame when will that happen.

  4. You can keep your HTPC in a suspend mode. Either suspend to RAM (sleep) or suspend to disk. Any Flirc is able to wake your PC from suspend modes. It's up to you to set your OS to properly use suspend modes.

    USB by default doesn't support turning the PC on from full shutdown (there are some exceptions but this depends on the manufacturer, I don't know if NUC supports this). Flirc-SE has additional connections (besides the USB) to the motherboard's power switch connector and is able to emulate pressing on the physical power button. That's why it is able to do this on any motherboard.

  5. I don't think so. Which Flirc do you have and which remote control? If it's an universal remote, then what device profile are you trying to use?

    It's important to know, that Flirc's IR receiver is really sensitive and you should not point your remote directly at it from a short distance during recording, because the receiver may receive overdriven signal which can be misinterpreted. You should either record your buttons from some distance or point the remote in a different direction (for example at the ceiling). The signal will bounce off a ceiling or walls and will go back to the receiver with much less power.

  6. There was never a sensitivity setting. You're probably referring to interkey delay setting. It's still supported for Flirc v1 (or 1st gen: Flirc USB in plastic cover and Flirc SE). For Flirc v2 (or 2nd gen) it's not supported anymore as the key repeat detection algorithm has been changed so that setting isn't needed.

  7. Since Kodi 16, Context menu is accessible by long pressing the Enter/OK key. Also it's not that hard to record the C key on the full keyboard controller in the GUI.

    As this issue wasn't critical in any way it probably got lost between other, more pressing issues. Anyway, I'll ask @jason if he could look into it.

  8. One more post to clear some things. There's no "software keyboard" mode in Flirc. What you're referring to is probably that you've selected the Full Keyboard controller in Flirc GUI. Switching controllers in the GUI doesn't do anything besides changing the view in the GUI. Controllers are just different views. Both Full Keyboard and Multimedia keys controllers give you access to all the keys. All other controllers (with some small exceptions) are just something like wrappers on full keyboard and multimedia controllers. They just provide preconfigured key combinations for specific applications or hardware. But they are still sending keyboard keystrokes. You can switch and mix keys from different controllers anyway you like.

    I think the issue you have is with the "Power Off" key. You've probably set your "Watch a Movie" activity in a way that when you exit that activity the remote sends the power off command. Maybe it's also being sent on entering other activities which causes your PC to turn on (as explained earlier, right now any code recognised by Flirc will wake the PC). So when the PC is up, the power off will turn it off, but when it's already off the power off key right now will turn it on.

  9. @GregL you need to give more information on your setup. What Harmony profile do you use with Flirc? Do you use one of the Flirc/* profiles on Harmony or something else? Did you use Flirc GUI to record the remote?

    I see that you are little confused when it comes to how Flirc operates.

    First of all, Flirc is a device which emulates an USB Keyboard. It maps signals from remote controls to key or key combination (key + one or more modifiers like alt, shift etc) presses. You use Flirc software to record the signals a remote sends and map them to specific keyboard keys.

    Flirc has some built-in profiles which are hardcoded and they work out of the box with Harmony remotes. To use a built-in profile you need to select one of the Flirc profiles in your Harmony (for example Flirc/Kodi). This means that there's some amount of predefined IR signals which are known by Flirc and they are translated to specific keyboard key presses.

    If you don't use one of the Flirc/* profiles in Harmony, then you need to use Flirc software to map your remote to specific keyboard keys.

    Now to answer your questions:

    Flirc is not classified as a mouse, so this is not something you should worry about right now. Every action Flirc does IS a keyboard keystroke. Flirc doesn't do anything else at this moment. So for any signal that Flirc recognises (one of the built-in or recorded ones) it sends a key press to the system.

    Like @jason has already said, the option to limit keys which are allowed to wake will eventually be available, so you need to wait until then. For now make sure you don't send any signals that are known to Flirc if you don't want to wake/turn on your PC. So don't record a signal that is sent when you press Watch Movie activity. Flirc won't turn on your PC if you send a signal that is not recorded in it.

  10. Both RC5 (used for example in MCE remotes) and RC6 protocols use something called a toggle bit. It's a single bit in the data frame which is toggled between key presses. For example when you press "up" the first time, the bit is equal 0. Then you release the button and press it again, the bit is set to 1.

    Like @jason mentioned, it's for detection whether or not the user really pressed the button again.

    A dedicated hardware (like IR receiver in the TV or DVD) which understands a specific protocol, knows how to decode the signal and properly retrieve command which is being sent. The toggle bit doesn't change the command itself.

    On the other hand, Flirc is more like a generic IR receiver in a sense, that it doesn't decode the signal (doesn't retrieve the command), but analyses the signal itself. Changing only a single bit causes the signal timings to be slightly different, which is recognised by Flirc as a different signal. It's like that because Flirc needs to work universally with any IR protocol.

  11. Correct me if I understand this incorrectly.

    You want to use Flirc to automate your process of installing your software by connecting multiple Flircs with exactly the same configuration to multiple firesticks and do the same action on all of them at the same time by controlling them from a single remote.

    If above is correct, then I think it's possible to do that. But there are some things you need to be sure for this to work:

    1. You need to be able to connect Flirc to firestick. As it doesn't have an USB type A port you need an OTG Y cable for each of your sticks. You also need the ADB USB debugging to be turned off (turning it on disabled the USB host functionality in firestick). This may be a problem if you need ADB to be enabled for some reason (I don't know if firestick has USB debugging turned on or off by default).
    2. You need to be sure, that every firestick is at exactly the same state after powering on (the same menu item should be selected) or some way to synchronise them. I don't know firetv/firestick at all, but maybe there's some key you can send that always selects first menu position or something like that. This would allow you to sync all devices before starting your installation procedure.
    3. Flirc is generally a very sensitive IR receiver (I have mine behind the TV without the direct line of sight and it still works 100%) so it shouldn't be any problem, but for a setup like that you would probably want every Flirc to be equally exposed to the IR signal from the remote to be sure that every key press is properly received.

    In the end, it's up to you to test all of this as I'm not aware of anyone using Flirc in that way :).

  12. It won't help in case of Flirc. It's not the issue of the IR signal but the USB interface communication with the device. As I've mentioned in my previous post Flirc is basically an USB keyboard (it acts as one). It would need to emulate a different device type (a gamepad) to be able to send HID codes associated with gamepads and be understood by the Shield.

  13. @drloser Flirc acts as an USB Keyboard. Keyboards don't have Shield gamepad bumpers. Unless you know the key combination on Shield that emulates bumpers then there's nothing Flirc can do right now. I'm not saying that it's totally not possible, but would not hold my breadth waiting for such support, because it would require a quite a few changes in the firmware.

  14. Yeah, I know. The documentation is lacking in a lot of areas. But @jason (the single guy behind creating and working on Flirc) has to split his time between his family and Flirc and I'm just helping here on the forum in my free time. I'm thinking about starting making some more robust documentation but this requires a lot of time to do it well. Also, I don't have edit access to the support articles (also not much time at the moment to edit them anyway). There was another guy (@Chris!) who helped a lot here on the forum and sorted a lot of support articles but he's not been active for quite some time now :(.

    You should be able to add comments on the support articles, so you're free to do so. This also helps.

  • Create New...