jason

Yes, you are basically correct. Sleep Detect tells flirc to make sure the computer is not sleeping, if the computer is sleeping all keys will be ignored. You must use the 'wake' key to wake the key from suspend (that's the only key that will do this), and then once the computer is on, flirc will detect this, and operate as expected. I don't have the ability to suspend the machine (yet).

Try upgrading to the latest firmware. http://forum.flirc.tv/index.php?/forum/70-v100-rc4/ Just download the package, open the GUI, your firmware will automatically be updated. Once updated, you can enable a sleep detection feature to help prevent automatically waking up the computer. It's in the GUI, File->Advanced. But, you must also pair a wake up key, which will tell the machine to wake up as all other buttons will be ignored while the computer is sleeping. The wake key is on the keyboard view of the GUI. Let me know if that helps. I believe it should do the trick.

Hey Nordertom, a copy of the driver is actually in the installation directory. Program Files\flirc\driver Let us know if that helps.

Yup, still going to put it in. I need enough feedback no the current feature-set before implementing more. I really haven't gotten that much feedback and what I have gotten has been mixed being hard to distinguish if these were new problems, or problems people are now reporting on the beta.

I built Flirc out of my frustration with LIRC..... I think we both know. :)

Send me an email at flirc.tv/support, I'll get you an RMA and I'd like to take a look at this unit. Really sorry for the delay.

If this happened on the original firmware, something else is wrong. Let's get you a replacement, shoot me an email. http://flirc.tv/support/ I'd also like to take a look at this one. Your config looks perfectly fine, like everything is operating correctly.

Can you post your flirc configuration? I'm trying to reproduce this, I can't... I'm pretty annoyed because I'm sure I can fix it pretty easily. This doesn't happen on the original firmware, correct? Here is another thread on the topic:

Try the latest release: http://forum.flirc.tv/index.php?/forum/69-v100-rc3/ The latest firmware should fix this, no one has posted any results regarding this issue, so those with the repeat issue, please try that release. Your firmware will automatically be upgraded to the latest release candidate.

Would love to see a picture of this. Thanks so much for sharing and helping others.

I'm trying to get one more thing into the GUI, almost there.

Sorry I've been mia. If this is a universal remote, the arrow keys may be activating a different device on the remote (tv) instead of VCR if that's what it's set to. There is no reason that keyboard arrow keys would give you a harder time numeric buttons. It's a remote issue. Can you post your configuration?

I got my forum bugs messed up. Have you guys tried the beta? I have a fix for this. You have to enable the feature in the CLI. The next GUI release will be able to manipulate these settings from within the app. No more commandline.

This looks fine. I'll push an update soon that hopefully addresses this. @timmeh, are you using harmony too? The harmony flirc profile? Which harmony do you have?

I will post an update tonight for you to try.

The XBMC Shortcuts are probably not the same. You'll have to do this manually with the keyboard controller view. Look up the plex keyboard shortcuts here: http://wiki.plexapp.com/index.php/Keyboard Let us know if that does the trick.

Yes of course

This is a planned feature.

Yes it's because these remotes send out two different keys for the same button. Just record each button twice. I'm working on how to solve this right now. Can you list the models of your remote?

I'll clean up the downloads page. The latest, or 0.96 windows version is the same exact version, with a different installer for the signed drivers. Flirc.exe [ 0.96 ] Or, you can install the beta, which is very stable. Both work on windows 8.

Thank you so much for the post and the gratitude. I tell everyone that takes the time to give positive feedback, it really makes the hard work worth it.

re-run as sudo Or, you'll need a udev rule, create a file called 51-flirc.rules put the following in the file: SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", MODE="0666" That is a bit extreme, every USB device becomes read/write accessible to all users, but honestly, it's absolutely stupid that you need root privileges to write to a usb device.

Does this happen on another machine? If you use another remote, does it go away? Can you post your configuration? Do the keys only repeat after pressing a remote button? How quickly are you repeating keys when pressing your remote. This shouldn't be a problem, could need a replacement.

Full time Job + Flirc + newborn baby = 0 time :( I'm forever sorry for the delay, this was absolutely not intentional. I finally had time to merge this into the branch, add the appropriate settings, and get this into the release candidate fw v1.1.0 The firmware is bundled with the GUI: You have to enable this feature!! Please read the instructions: Instructions to give this a try: 1) Download the 2) Launch the GUI, the gui will detect you don't have the latest supported firmware, and automatically upgrade for you 3) Launch the CLI bundled with the GUI and run: flirc_util noise_canceler enable Verify! The below output shows me noise canceling is enabled. flirc_util settings Settings: sleep detection: Disabled noise canceler: Enabled inter-key delay: 6 keys recorded: 0 keys remaining: 169 memory used: 0% No Keys Found You should not have to re-record buttons. If you do record buttons with this enabled, you will get less spurious noise recorded. (hopefully none). Provide feedback regarding this issue in here: http://forum.flirc.tv/index.php?/forum/58-v110-rc/ Otherwise, it's very easy for me to loose track of issues and which firmware/gui/cli version they correspond too. I'm going to get better about that as well as tracking known problems, and providing feedback of implementation schedules.

are you both using a harmony?