---> note: I reference a couple of posts from different threads here which are related to my suggestion:
KenJs: Any insight as to when this will be available? I bought the device after seeing that it had a transmitter, so its a bit disappointing not to be able to use the transmitter...
yawor: unfortunately there's no timeline yet on when that feature will be implemented. There's still no consensus on how the blaster will be accessible to the OS and apps/scripts.
Let me give you an example use case, and explain how I think the IR blaster should be supported :
In the FLIRC configurator app, create a new tab or mode switch gadget that enables scripting the IR blaster. When the user flips the switch:
FLIRC configurator says: "press the key that you want to script on your primary remote"
press the Power key on your primary remote (the one that you use to control your media center PC)
FLIRC configurator says: "On any remote, press the key(s) that you want FLIRC to broadcast"
press Power button on your TV remote
press Power button on your Sound Bar remote
select END RECORDING in the FLIRC configurator app
Result: When you press the power button on your media center remote, FLIRC will hear this and broadcast the IR codes to turn on the TV and sound bar. Now you only need one remote to control your media center (instead of three.) You dont even need a media center PC if you just plug FLIRC into a USB power supply on (or near) the TV. So FLIRC now appeals to a much wider audience:
I could program a FLIRC device and give it to the client. There is no need to buy a big scripting remote that will intimidate them with its cost & complexity. If my clients have a remote control which they know and love, and they do not want to replace it, FLIRC can add the extra functionality which it needs to support power switching on multiple devices. (In most cases, that is all my clients want.)
yawor: There's no built-in automation for transmitting. The Flirc's main focus is still on controlling the PC (or other USB Host hardware) to which the Flirc is connected. This means that you can't configure the IR signal to be automatically transmitted by the Flirc itself in response to a different IR signal.
---> I think it is time to implement this feature, since it would resolve 95% of my clients complaints, and significantly expand the number of applications where FLIRC could be useful.
yawor: The IR control is prone to interference if more than one IR transmitter is sending control signals at the same time.
In the scenario which I just described, where the essential TV/Sound Bar/Kodi functions that you would use on a daily basis are all integrated into one remote, interference from other remotes should not be an issue.
The IR transmitter in FLIRC could also be programmed to wait about 1/4 or 1/2 second after the last IR reception before broadcasting an IR macro. Also bear in mind that it takes about 5 or 10 seconds for the TV to boot. So the user wont typically be mashing any other keys on his IR remote while he waits for an HDMI signal to appear on the screen. For this reason, I really think that broadcasting IR power commands will work just fine in most applications, and it solves the most common complaint that I get as a home automation consultant.
---> Even if your media center PC is on a shelf below the TV, and the TV cannot see the FLIRC IR broadcast, you could use an IR repeater to expand FLIRC's broadcast coverage. For example:
BlastIR 8 Best Remote Extenders
You can even buy an IR extender that piggybacks IR signals on the HDMI cable, so both components of the extender can be placed within your media cabinet where they are less likely to be disturbed by family or pets.