yawor

You are mixing key codes with HID codes. You are able to map arbitrary key to F13 but it happens in much higher layer in the system. What I've said before is that the HID keyboard filter driver (which works at very low level) does not recognize HID code for F13 it receives from Flirc. It may be so because there are no keyboards right now with physical keys F13-F24 so maybe Microsoft decided to just drop their support in the HID keyboard filter driver. Because of that the driver does not emit key code for F13 to the system. The HID keyboard filter driver converts HID codes received from the keyboard into key codes according to selected keyboard layout. HID codes are not assigned to specific key functions or letters but the key physical position on the keyboard (the tables which can be found on the Internet describing HID standard are just based on the keyboard with US QWERTY layout for convenience). For example when US QWERTY layout is selected then HID code 0x1C is translated into key code 0x59 which is letter Y. But when you select german QWERTZ layout then the same HID code 0x1C will be translated into keycode 0x5A which is letter Z. So if you are able to edit keyboard layout definitions then there should be possible to just add an entry for HID code 0x68 (F13) to be translated into correct key code for F13 (I think it's 0x7C). But I still think that if you are going to use EG or AHK anyway then using Flirc as a HID input device instead of keyboard (at least for some buttons - you can mix both modes) is better way because you skip the HID keyboard filter driver entirely.

It doesn't work because Windows' keyboard filter driver does not support such a key. The filter driver doesn't know how to map the HID code to a key code so it just silently drops it.

Hi, Please take a look here:

Different manufacturers are using different IR protocols. Many protocols are using some very complex encoding schemes (the way the digital data is encoded in IR light pulses). Universal remotes need to emulate those protocols precisely if they want to be recognized by the intended receiver hardware. So short answer is yes, programming does affect the way the remote sends the codes. Also the remote can send signals with different base frequency and Flirc works best with ones which use frequencies around 38 kHz. Is this Philips remote a full universal remote? Can you set it for example to a different TV manufacturer? If yes please try setting it for some newer LG or Samsung TV. I'm using my universal remote with a Samsung TV setup code and I can program every single button on the remote. Both LG and Samsung newer TV receivers (at least some of them) are using a NEC1 IR protocol which is simple enough that Flirc has no problems at all working with it.

Are you pointing the remote directly at Flirc from short distance when recording? Because you shouldn't do that. Flirc is very sensitive and when the signal is too strong then strange things can happen. Try pointing the remote in different direction (for example at the ceiling) or keep the remote at least 1-2 meters (3-6 feet) away. When you press the record button does the software wait for you to press a key or maybe it sometimes records something by itself? Flirc can be sensitive to IR noise from different sources like Plasma TV or certain types of lights. Please write more about all remotes you've tried.

Hi, I've already talked with Jason about properly showing custom HID codes in CLI and he said he'll fix this. I'll send a message to remind him about this issue. Key repeating in "HID mode" is not a Flirc issue. This is an issue with original EG HID plugin. EG has two types of events: normal (single shot) and enduring. Original HID plugin trigger only normal events so every new HID event received will trigger new EG event. My change adds ability to trigger enduring event. Enduring event ends only when different key is pressed or previous key is released. Thanks to that you can use long press triggers in EG.

Hi. There's no problem with assigning the same keyboard keys or shortcuts to more than one button on the remote.

@rockgatherer97: Good work :). Just to be precise: the HID plugin for EG is not developed by me. I've only modified the original HID plugin which is already provided in the standard EG install.

Hi, Something in your home is generating IR noise which is being received by Flirc. There can be many different sources or IR noise like Plasma TVs or certain types of lighting. You can try turning on noise cancellation in advanced options. If you have a Plasma TV then try programming Flirc with TV off or hide Flirc behind the TV.

Hi, There are at least two or three threads on the forum where Pi Case compatibility with Pi 2 has been discussed. I think there is no need to start a new one. Short answer is that the current case is mostly compatible with new Pi 2 (the only difference is that the CPU is not exactly where it has been on Pi B+).

I'm wondering what Microsoft programmers are doing that there are so much issues with WMC. If the application changes the key recognition mechanisms depending on the mode there may never be a 100% working solution with Flirc (I still hope Jason will somehow find a way). I think that if even the EventGhost has issues with WMC then the problem is the WMC itself.

Hi, Unfortunately you can't record or retrieve original raw signal data with Flirc because it is not preserved. The original signal is reduced into an irreversible hash value which is then stored on the device. As for the Python API, it is used in the XBMC/Kodi plugin but I don't think it can be considered a separate product right now. I know that the info on the homepage may misleading and I've reported it myself not that long ago.

Hi, There are two Flirc models available: - A classic Flirc in the form of USB stick: this one allows you to wake the PC from the sleep or hibernation states (S3 and S4). Some changes to power management configuration may be required in the system. - A Flirc-SE (Streacom Edition): this has different form factor than classic one as it is a board that can be installed internally into a HTPC case. It has all the abilities of the classic model but also has extra pins which can be connected to the motherboard power switch input. It can then simulate power switch press and has ability to power on the PC from full shutdown (S5 power state). It still needs to get 5v either from internal USB port or directly from the PSU if the motherboard disables power to the USB in S5.

Can you save your Flirc config to a file and upload it here? I don't know if the forum upload is fixed now so if you can't upload it here then put it on Dropbox or somewhere else that allows to share a file and paste a link here.

You shouldn't need to install anything for Flirc to work. It is recognized as an USB keyboard. Actually Flirc is recognized as 2 separate devices. One is for the keyboard interface and the other is for programming. If you don't want to install Flirc software on that PC then you can just ignore the warning that Windows can't find drivers for device. Flirc only needs USB Keyboard driver installed for it to work if it's already programmed. Unless the copy of Windows you are using for your HTPC isn't somehow modified (like for example most drivers removed from the install) then it must have an USB Keyboard driver built-in.

Hi bipolarbear, Are you 100% sure that the power switch pins on Flirc-SE are properly connected to the motherboard?

Hi, The long press is not supported yet and I would not hold my breath for it being implemented anytime soon. As for the menu button behavior, it's not related to Flirc itself in any way. You need to change it yourself in the Kodi keymap file: http://kodi.wiki/view/Keymap. Kodi allows you to map keys differently for different modes - fullscreenplayer is the one you should be interested in. All required info should be in Kodi wiki.

@Jason, maybe this is the same issue with HID keyboard filter driver in Windows I've described to you via PM. @MediaCenterOwner, after uninstalling the Flirc software can you plug Flirc to a different USB port and test it then?

Do you mean the Simple TV (URC-6410) model? It is also nice. Too bad OFA/UEI added key backlight only to Simple 4 models (URC-6440 and OARUSB04G).

You can also do this on these models. You can switch device type on all device buttons to the same type (for example I have a TV type device on PVR on URC-6440) and then use the same code on all of them. A nice thing with these remotes is that when you press any button you actually see to which device a remote is actually sending the signal because the selected device button itself lights up.

Hi Look at OneForAll URC-6440 or OARUSB04G. These are almost the same. The former is for European market and the latter is for US market. These are also made by UEI.

Using Kodi keymaps and python scripts is also a nice idea. It may depend on Kodi being running correctly but it also gives ability to change keymaps depending on current app state: for example you can run different scripts (or with different arguments) for fullscreen player and different for main menu. Every method is good as long as it does what it needs to do :).

Hi, You should take a look at triggerhappy daemon. It can take any input event (keyboard included) and the run any script or executable you want.

Yes, Flirc can send multimedia keys. To be sure maybe get somewhere (maybe you can borrow from someone) another keyboard with volume keys and do another test. It is possible, that volume control in the HU may not be under Android control.

Hi, First of all you don't need software for Flirc to work. The software is used for programming Flirc (recording buttons, changing settings etc). You can install software on your PC, program it there and then just plug it into whatever you want :). You should first check if you can control the HU with a normal USB keyboard plugged into one of the USB ports. This is important because Flirc emulates an USB keyboard. If HU can be controlled with the keyboard then it should also work with Flirc. You should also look for AndroidTV threads here on the forum. Other things to consider: Inside of a car can become hot or very cold in different weather conditions and seasons. I don't know how much heat or cold can Flirc withstand. In winter you probably should somehow insulate the Flirc so there is no moisture in it because the water vapor in the air can condensate inside Flirc case and short the circuit.