jason

This happens occasionally. It’s a false positive. Everything is written from the ground up or open source. I would never do something like thIs. Thanks for letting us know.

Version issue should be fixed. If you update to the latest. @yawor is correct, I believe it's an MCE issue. Go to advanced, and disable the Windows MCE profile, see if that helps the keys being 'too' sensitive. Please let me know if that works.

Very happy to hear that. Thanks so much for letting me know.

Yes sorry, unfortunately I don't know if I can do apt link forwarding. I'm giving up on hosting a repo. It was a shit ton of work, every distro is different, and each version of the distro is different. Packaging cloud is a service where you send them a package, they sign it, and host it in compliance. Brilliant, sorry I didn't think of it. You'll need to update that. No 32 bit binary at the moment unfortunately, can't figure out how to get Travis to build one yet without doing a docker.

Yeah. Here is what you need to do. You need to hook up Flirc to your PC. Flirc is going to become an IR transmitter. You're going to put the B&O remote's receiver facing the flirc, right up against it, and put it in learning mode. NVIDIA's profile has 7 buttons, attached a pic. Up, Down, Left, Right, Enter, Back, Home. You need to output the IR waveforms for these buttons. I've attached a text file: nvidia.txt In this text file, it shows the 'command number' :: 'waveform' for example, the first line: 0x0 :: 0,4900,4900,840,1680,840,1680,840,1680,840,840,840,1680,840,1680,840,1680,840,6580,840,840,840,1680,840,840,1680,840,840,840,840,840,840,840,840,840,840,840,840,840,840 0 is the command up (as noted in the screenshot attached). the waveform follows after the '::' So we want to put your B&O into learning mode for the 'up' button. Then emit this waveform from flirc using my commandline application. Not sure which OS you're using, but you can use my documentation to find the commandline app: https://flirc.gitbooks.io/flirc-instructions/content/command-line-interface-guide.html To get Flirc to send that particular code, you'd issue the following command: flirc_util send_ir_raw 0,4900,4900,840,1680,840,1680,840,1680,840,840,840,1680,840,1680,840,1680,840,6580,840,840,840,1680,840,840,1680,840,840,840,840,840,840,840,840,840,840,840,840,840,840 If you were on windows, you'd need: flirc_util.exe send_ir_raw 0,4900,4900,840,1680,840,1680,840,1680,840,840,840,1680,840,1680,840,1680,840,6580,840,840,840,1680,840,840,1680,840,840,840,840,840,840,840,840,840,840,840,840,840,840 Then you'd repeat the process for all of the keys. The transmitter in flirc isn't great. It's about 1mm wide. So remember, you have to have the B&O very close, line of sight. Let me know if that makes sense. Sorry for the delay, traveling.

Yea, Flirc needs to output the NVIDIA IR protocol for bang to capture it so it can later repeat it. What OS are you on? Can you run a commandline command?

Uncheck the built-in profiles, let me know if that does anything. Also, what version of firmware are you on?

Can you post a screenshot?

I'm sorry for the delay guys. Something will come before the end of the year. I'm going to get back to firmware very shortly. I had a ton of stuff I had to finish outside of this. I'll post a blog update soon. Long story short, I scoured the internet, and found this project: https://blog.gimx.fr I reached out to him and asked him to possibly port some of his firmware to libopencm3, where I use just the USB stack. He was extremely nice, ported that over, and now I've got to work on integrating that into the rest of my firmware. I need some more time before I can get to this specifically, but it'll be completed before christmas.

Yeah, definitely possible. We just need to figure out what the key mappings are.

hint: http://blog.flirc.tv/index.php/2017/09/06/new-product-up-and-running/ Everything is working, but packaging/tooling/etc, will be a 2018 release unfortunately. Moving as fast as I can.

It wont work with the firetv stick through hdmi. I'm working on a product to address this.

Sorry, you're feeding me bits of information. Could have been the device upgrade too. Do you remember when this happened? When did you get it, when did you do the upgrade? If you put flirc into a computer, open up wordpad, textpad, then press the activity button on your remote, are any keys sent to the pc? Can you describe the activity a bit? Did you use my software to pair your flirc with your logitech remote? If you did, you don't need to, since the keys are built in. If you go to file->advanced, you'll see there are a bunch of built in profiles. It's possible that something in your activity is in the built in rom table, or a recorded key. Flirc wont wake up the machine if a signal is received that's not recorded.

before what upgrade?

Can you elaborate, what's the issue you are having?