Oli.K

Oh, I didn't know that my request is already possible? Please also note that I do *not* want to use the usual keyboard function in this case as it would mess with focused applications. The detection of IR codes via HID messages shall be discrete and only my software shall receive the codes at will. Will *all* received IR codes be sent via HID? And which HID device would that be? I already tried listening to the flirc.tv HID devices for raw data but none of them was sending any data. Must they be initialized before any data can be received? I did not define any controller setup because as said I do not want to use the virtual keyboard function of FLIRC. So what does the API look like (where do I get headers, definitions etc.) and how can I receive the (raw) IR codes? Thanks a ton.

Hi there, FLIRC has a great way of doing its things (being a keyboard) and I really like that! Its unique and well done. As I am developing my own automation software I am however looking for another use of the cool FLIRC USB dongles. For that use case I would like to flash a yet to be packaged custom FLIRC firmware with much reduced functionality to get access to the IR codes. The access to the IR codes would allow me to be MUCH more flexible when performing actions in my custom automation. This is what the reduced firmware would do: - receive all supported IR codes from all supported remotes - convert any received IR code to a HID message - directly transmit the HID message to be processed by whoever is listening This functionality is quite the same as what Home Electronics Tira-4 already does. The IR codes are immediately sent as HID message and can be then used in you own custom setup to feed automation or whatever. I ask for something like this because I think all the no-longer-used FLIRCS that are around could then get another life. I also have several FLIRCS currently lying around without any use. They WOULD be used again if you could flash them to be a raw HID IR code receiver. This firmware should hopefully not be that much work and could use everything you already have until the point where the hash for a IR code is generated. Instead of generating that hash code a HID message with the IR code data would be sent. Eventually this is even doable as part of the normal firmware? So that when the raw IR code is available it is always sent as raw HID message to a special dedicated HID device for that purpose. Even if the code is NOT assigned to anything. So FLIRC would expose another HID device for this raw IR data use case. Everything else would stay the same. You could then use the normal FLIRC way OR attach to the raw data HID device for low level IR codes. Hope this gets some love as I would breathe life into my unused FLIRCS :) Thanks a lot!