Jump to content
Flirc Forums


  • Posts

  • Joined

  • Last visited

Posts posted by Hotwire

  1. Only the Flirc SE (SE = Streacom Edition) can do cold booting, because you can only do cold booting by sending a signal to the power button header on your motherboard, the header for which only the Flirc SE has got a connector for. Also your motherboard has to support keeping an internal USB header powered, because the Flirc SE needs to be connected to one, and the Flirc SE needs to remain powered to work as it hasn't got a battery.

  2. Is there any v2 version of the Flirc SE planned? I'm very intrigued about:


    Assign two functions to one button. Press the button for one function, hold down the button for the other function. Now possible with our new powerful arm processor.


    Want to run a number of commands on a key press? With the new flirc, you can store over 500 keys, and have more than one keypress per individual remote button.









    P.S. if there will be one released: please make the PCB black so that it can match the rest of my systems' internals. :)



  3. I've got the first iteration of the non-SE Flirc dongle, but I've got an issue that it wakes my HTPC from Hibernate at every IR signal it picks up. Now, I want to buy the Flirc-SE so that I can wake my HTPC with my remote from cold shutdown as well. Can the Flirc-SE be programmed in some way to only wake the HTPC with only one specific IR signal?

  4. That may be anecdotal for you but is not an inherent flaw. I use WiFi integration with a hub and one of my Shields and have no issues with latency whatsoever. A lot of factors can cause latency issues.

    Not anecdotal. Controlling an IR device via my Harmony Hub (phone-WiFi->hub->receiver) has got more noticeable input lag than using the physical remote of the Harmony set (remote->hub->receiver). But it entirely depends on how you use it. The increase in input lag is far less noticeable if you don't need to spam commands. For me it is too slow. It might be less slow when taking the hub out of the equation (phone->WiFi->receiver), but it'll never be as responsive as remote->receiver. Even it would in be as fast, a virtual remote is still a massive pain the rear. 

  5. Imagine if, back in the day when IR got traction, all the different manufacturers implemented it, used their own codes, and refused to share them. And if there was no way to easily intercept and decipher said codes. 

    That's more or less what you have with BT today. BT also has limitations and as for how "fast" it is that is entirely up to how well it is implemented. Logitech worked directly with Sony on their PS4 implementation, for example. 

    Doing the same thing for example with a HTPC is an entirely different problem. 

    If anything, I see wifi remote control becoming more common. The Shield and a few other devices already offer it (the Harmony can control the Shield over Wifi today) and virtually every device including TVs today have wifi, whereas BT isn't as common.

    The FLIRC is an excellent supplement to devices like these. For example, having full keyboard shortcuts mapped to IR makes the Shield far more functional with apps like Kodi that support keyboard shortcuts. 

    The thing about RC over WiFi, is that latency is quite high. Also not having physical buttons for RC is not really desirable imo.

  6. List of BT devices supported by Harmony: https://support.myharmony.com/en-us/how-to-pair-over-bluetooth-usb-receiver-or-wi-fi

    You wouldn't add BT to Flirc for PS4, but to control Flirc with a BT remote. The benefits are:

    • Removing line of sight issues in regards to device placement, and a far greater signal range.
    • Reduction in relay devices to bridge devices that are in different rooms. Currently you'd have to purchase either a Logitech Harmony Companion (which uses a hub as RF>IR relay), or/and those IR pyramid devices which do IR>RF>IR. This is much less efficient, as well as being a disaster if you'd want to control multiple devices in different rooms from a single room (you'd have to buy a whole bunch of relay equipment to bridge each room). BT would remove the necessity for relay devices, as range is greater, allowing for direct communication.
    • BT support would allow many more users to install the Flirc Streacom Edition in non-Streacom enclosures. The FLIRC-SE is a much cleaner solution than the Flirc dongle, because it is an internal device. It's also the only solution that allows users to remotely boot from S5 power state. If users want to install a FLIRC-SE now, they'd have to mod their case (drill a hole in it to receive IR) if it is not a Streacom. BT would avoid having to do enclosure modifications.
    • And lastly is reduction of input lag. Takes this with a grain of salt, it might be my imagination, but last time I tested it felt like commanding with my Harmony via BT to my PS4 was faster, than it was with my Harmony via IR to my STB. It felt like there was less overall input lag between Harmony and PS4 via BT. But I'll leave this one in the middle before I've tested some more.
  7. Both remotes have some issues with the Flirc software. Here's a summary of what I've found so far:

    Remote of the Harmony Companion

    Buttons that are read as duplicates: Exit and Back/Previous Channel. Guide and OK (button in center of D-pad).

    Buttons that don't get read: Menu, Source, E, DVR and Record.


    Buttons of the Harmony 650

    Buttons that are read as duplicates: Guide and OK (button in center of D-pad).

    Buttons that don't get read: Back/Previous Channel, Menu, Source, E, and Record.


    I've found a workaround for these issues though. I'm currently using my telecom provider's TV remote (but any random remote will most likely work as well), and go through all the commands to see which get picked up by the Flirc software. I then teach the commands that work to my Harmony remotes, and bind the learned commands to the buttons that had an unrecognized signal.


    Still, I have to express this: as Flirc company states that...

    We don’t want to just make great media center products, we want to make great media center solutions. Which is why we’ve partnered with Logitech. Logitech has a number of custom flirc profiles that allow you to easily control your favorite media center hardware or favorite application. No flirc programming necessary, support is built in.

    ...my solution in this context is not a pretty one. Having such flaws is excusable if it were pertaining to any random X brand remote, but considering my issues are in regards to remotes of a company that Flirc have been partners with for quite a while, this is definitely not. I'd kindly like to suggest to refine the support of at least the 650 and Companion (I say at least, as I don't know if other Harmony remotes suffer from the same issues). The suggestions for refinement are:

    • Let the software be able to recognize all buttons from these remotes (not just the ones that you've pre-programmed), and make sure that each button is read as unique.
    • Talk to Logitech to expand support on their side as well. Their button layout is not a carbon copy of your Kodi layout. For instance: 'Home' is called 'Back' in the Harmony software (goes for both remotes, as well as well as the virtual remote in the Harmony app). And some buttons are missing: for example there's no button present in the Harmony software that represents the functionality of the 'Go Back' button in the Kodi layout.



  • Create New...