yawor

Yes, you need to have some extra active buttons that are not yet mapped in the built-in profile. I won't help you with that because I don't use Logitech remotes at all. If you don't need all the keys from the built-in profile then you can always turn the built-in profiles off and then map all the keys yourself the way you want them to be mapped.

Hi, You can always record new keys in Flirc GUI if you have enough space in Flirc EEPROM. It can store almost 200 keys (built-in profiles don't count into the limit). You can use built-in profile and record extra keys or you can disable built-in profiles and record all the buttons from the start. That way you have more control. I would not recommend using MCE remote for any key, not only Windows one. Also there is a problem with Windows key because you can't assign anything to just Windows key in the GUI because Windows key is a modifier and it can be only used with some other non-modifier key. You would need to use Flirc command line tool for that. I've described it sometime ago so you should be able to find it using forum search function.

The CPU may be in a halted state but other components are still drawing power so there is not much of gain in this state. The CPU in idle mode doesn't draw much power either. I just have my RPi2 always on.

Hi, GUI always defaults to the Minimalist Controller because there is no info on the Flirc about the controller. Only key codes and remote signal hashes are stored on the Flirc. I think that you're affected by a strange bug that Windows recognizes Flirc as a HID keyboard device but doesn't register HID keyboard filter properly. I've also had this problem before and it's gone after system reinstall. For me it affected only specific USB ports so some of them did work but some didn't. I haven't found any solution besides switching USB port and system reinstall in the end. But I'm not a Windows drivers expert so maybe there is some other solution to this. If you have a possibility to test Flirc operation on either different OS or PC then please just plug it in and don't install the Flirc software. It should send the keys you already have recorded. About the two interfaces it is OK. Flirc presents itself as two devices: one is an USB HID keyboard and the second one is used for device programming.

I have no problems with key repeats. I'm using OSMC on RPi2 and when I press and hold a key mapped for down arrow when I'm on some list it scrolls down until I release the key. I'm using an universal remote with some Samsung TV profile.

You need to take into consideration that Flirc is basically a one man show. There are a few people (like me) who help on the forums, but the whole hardware and software design is done by a single person. Believe me, he isn't resting on the laurels :). There's also this: http://www.flirc.tv/fundraising/

That probably can't be done. First of all those really small devices (like the thumb drive you've posted) are using dedicated controller chips. Flirc is using general purpose microprocessor and all the features are implemented in the software running on the chip. Going for dedicated hardware would probably require Flirc to be mass produced and have much larger market share to be even considerable. The costs of designing your own integrated circuits are rather high. If you don't like how a Flirc dongle sticks out then you can go for the Flirc-SE (Streacom Edition) which can be installed inside a case.

Hi, You need to contact Jason (via private message on the forum or by email - it's available on his profile) and ask him for a downgrade. He has a lot of work and maybe missed this thread.

Hi, This is a known issue when using flirc_util on the Windows. In some cases the .exe suffix is required for proper operation. It's good that you've figured it out on your own :).

This extender doesn't have any electronics for sure. I had at least two of those in the past and I've disassembled one of them to use the cable and the socket for my own needs. Possible issue here is that the cables used by the Logitech in these extenders are really thin and prone to interference if not properly shielded. Is your PC grounded properly? The ground connection is connected to the shield of the USB port and connects to the cable shielding. If not grounded properly and thin enough the cable will act as an antenna catching different RF signals. Maybe that interference is what wakes up your PC.

Hi, The Flirc software presumes that the layout is US QWERTY compatible. Don't worry, there's still a way to do this. Please read this whole thread: It is for french layout so details are different but the solution is the same. If you still have a problem after reading the thread please let me know.

Are you serving root fs for RPi using NFS from your NAS? I have Synology DS414slim and I had more issues than it was worth when using NFS on RPi 2 with OSMC. In the end I've switched back to root fs on microSD card but I keep the Kodi library in MariaDB on the NAS. It minimizes the number of writes on the microSD. I still need to set the thumbnail store redirection so it is also kept on the NAS. As for your question regarding the RemotePi board it looks like a really nice solution. It removes the responsibility of power on/off switching off Flirc entirely as it also has an IR receiver. You can even replace Flirc with this and use it as an input for LIRC and Kodi. But I personally would still prefer to use Flirc as it gives me much more flexibility. Also there is nothing in the way of using both receivers at the same time if one can do something other can't.

Either that or maybe just a button to open some on screen keyboard implemented in the TV receiver or whatever that remote is for.

There is no difference between RPi 1 and 2 in the area of power management (or rather the lack of it).

Hi, Raspberry Pi doesn't have any power management feature so you can't control the power state using USB devices only (Flirc included). There are some projects that add power management to Flirc using additional circuit boards and connection to GPIO ports for communication. You can try searching for "raspberry pi power management" or "atxraspi". Some of those projects could work with Flirc SE as it has extra pins to control power switch.

Do you have a Flirc plugin installed in your Kodi install? I don't see why it would freeze anything as Flirc is seen by the OS as a normal USB keyboard, not some generic IR receiver.

I think that the remote itself doesn't have any "SMS-type" input logic built-in and labels on the buttons are only to help when the receiver end has such ability (for example an option in TV receiver to enter some text). I've seen some remotes with such labes and they all send just the same code no matter how many times you press the buttons.

Hi, What do you mean "standard IR game controller"? The Xbox (either One or 360) game controllers don't use IR to connect to the console. They are using radio frequency (RF). As for the controlling Xbox One with Flirc I can't remember if such a subject has been already discussed on the forum or not. You can hook up a standard USB keyboard to the Xbox One and check what can you control with it. Then save your current Flirc config on the PC, record the keys you know that work on the Xbox One (that you tested with the keyboard) and plug the Flirc into the console. After you finish the test just load your saved config back into the Flirc.

Hi, How did upgrade the firmware? On the Windows? Because Flirc app 0.98 doesn't have firmware 3.6 included so it couldn't offer you to do the upgrade. The 3.6 firmware is included in the app version 1.3.6. You probably won't be able to program Flirc with firmware 3.6 using app 0.98. But you don't need the app for Flirc to work. You only need the app for programming. You can program it on Windows and then use it on OS X. PS. I'm removing your second thread as it is basically same subject.

Hi, I've recently described how to do this.

Hi, What you need to know is that Flirc acts as a keyboard in the system. So you should be able to do everything you are able to do from your normal keyboard. The configuration "pages" (they are called controllers in the GUI) are mostly shortcuts for keyboard controller. Media controller is probably the only exception as there are no media keys on the keyboard controller. If you know hotkeys for the JRiver you can use the keyboard controller very easily. Just select the combination of keys you need in the GUI (first modifiers like shift, ctrl etc if any and then specific key like a, b, c etc). Then the GUI will ask you to press some button on the remote. As for the phantom presses every few seconds try covering Flirc with your hand to check if it really receives some signal. If the presses stop then there is some infrared noise which is received by the Flirc. You need to make sure that when you record your buttons there are no other signals or noise.

Yes. It's a driver issue. I also had this on one of my computers before the Windows reinstall. For some reason Windows doesn't accept keyboard input from the Flirc even that it is correctly recognized as a USB HID keyboard. I haven't found a solution different than changing the USB port. In the end I had 2 or 3 USB ports of 8 total in my system which worked and the rest didn't. After reinstall everything works properly (I had to reinstall it anyway).

Do you have an ability to test on another PC? If yes then just plug already programmed Flirc (with the letter A test for example) into it but don't install the Flirc software there. Do a test with a notepad.

Are you testing also outside of the Flirc GUI? Please try recording something simple like letter a and then open notepad, click on it so it is in focus and try pressing recorded button. It should write the letter a in the notepad. Have you tried plugging Flirc into different USB port? If not, can you try and let us know if this changes something?

Do I understand correctly that you want to map just the Windows key to some button on the remote? You can't do that using the GUI because the Windows key is a modifier key like Shift, Ctrl and Alt keys. The GUI expects that the modifier keys are used with some non-modifier key (so you first click on the desired modifiers and then on the key you want for example ctrl + a). You need to use flirc_util (command line utility): flirc_util.exe record_api 8 0 This will record a HID code 0 (which indicates that no button has been pressed) with Left Win key as a modifier. I've tested this and it works.