jason

You just need a launcher, and you need to pair the launcher keys with your remote, and you should be good to go

Logitech has a known problem. They are going to fix it but it's taken a bit of time. I'm working on some experimental firmware to handle repeats on my device, but I need another week or so. Can you hang in there Nick? I'll make an announcement on my blog and on the forums beta section.

does it work outside of kodi? If you fire up a text editor, does it work?

Okay, I sent you a message back, I'm just catching up. We'll set up a team viewer session. I think the drivers are not installed correctly.

in advanced configuration, do you have sequence modifiers enabled or disabled?

I think you're definitely right, as always.

Thanks so much for following up. I really appreciate it and am certainly surprised by the solution. Can I get a little bit more information bout the hardware that was preventing it from sleeping from logitech? Do you have a link? Thanks again.

I think it's the remote profile. Since that's a universal remote, can you change to a panasonic or samsung remote to control flirc?

Okay, how about this: http://cl.ly/2j3g3V2D0a0q I found some duplicates, play and pause. Please re-record that. I also found the wake key, which is strange, as that's now the only button that should be able to wake your machine. I deleted that, just in case it was an accident. Re-record it if it wasn't. I've also disabled built in profiles, in case noise was matching those signals. Give that a shot and let me know if it works. If it doesn't, try going to advanced, and enabling the noise filter.

can you share your configuration?

Yeah, sorry for the delay. If you have a harmony, the integration is seamless. Their profiles are built into the device.

Yeah, I got mine and it's not working. It looks like a standard 38khz frequency, but I'm going to say the wavelength of the light is funny. It's just not working and it's going to take me time to figure out why. Sorry, guys, not something I'm going to be able to get too right away, I have a ton on my plate.

No, I don't believe so. I would need to pick one of those up, but the result is probably going to be frustrating. I do plan on being able to support that in the future, but I have a ton on my plate at the moment.

I'm really sorry you are having trouble. But there is no reason for name calling. I do this on my own, and to fundraise for cancer research. Without anything constructive, I can't fix the problem. If you could please help by describing the problem a bit more, I can try to address it. Or better yet, we can connect on skype and go back and forth with questions. But please give me the opportunity to try to help. I understand you are frustrated. I'm sorry about that.

I know what the problem is. I've had a really hard time these past few weeks. I'm going to release an update over the weekend that allows people to change this setting before I figure out how to do it on the fly. Hang in there and watch the beta forums. I'm sorry for your frustration. What firmware were you at previously?

does the repeat start happening after you press a button, or is it triggered randomly by the environment?

I'm going to put a method to downgrade soon. I'm fucking swamped. Shoot me an email: flirc.tv/contact I'll get you the older firmware and come up with a fix for this. I know what the problem is.

Is it always the same key it's spamming? Or is it random?

and thank you for following up and letting us know.

Glad you got it working.

While the sensitivity is pretty high, the idea is you are sitting at your computer while doing the recording and right next to the device. So you bounce it off the wall and get a much more realistic signal. Then when you sit on the couch, you are much farther away, and therefore can point it directly at the direction of the device. With the bouncing off the wall for recording method, do you have better luck with it working in notepad, etc?

Eric - Publicly saying I'm sorry. I responded to your email and my suggestion was making sure both devices are not set to use libusbk. Try removing the driver for both, rebooting and seeing what drivers get loaded for each. Thanks Eric for the patience, and again, I'm sorry for the trouble. Sincerely, Jason

I picked one up, let me track down my testing results.

Hooo Rah! Awesome. Thanks for letting me know. I had a funny feeling I fixed this.

How about what you showed but with and without sequence modifiers checked?