jason

Sorry this is a bit hard for me to trouble shoot. Nothing in the system seems to be saying there are any problems. Let me push an update out that lets you debug the IR. Give me until the end of the day. Also, I unofficially don't support the first generation anymore. I'll push updates every once in a while, but I'm not going to spend any time adding new features. It was a shit show working on that microcontroller and waisted too much of my time doing optimization because of the lack of USB hardware in the processor.

glad it's up and running and working. Thanks for the patience.

@yawor is correct. There are a list of tables built into flirc. They don't ever get deleted. If you disable them, they get passed over when searching for a stored command. You can record 'over' them basically by re-assigning these keys into the user area. If the key exists in the user area, it uses this over the built in table. Yes, I need to work with logitech to add stuff. They are pretty good if something is missing or needs correcting.

Have you tried the sleep/suspend keys in the "Media Keys" controller section of my GUI?

And what do you pair that too in my app?

Okay, all good news. You have to record every key twice, that particular remote sends out two distinct alternating keys for every press. So Up has two keys associated with it. It's so the TV can detect if someone walked in front of the remote, or you lifted your finger and pressed the button again. So for example, open the GUI, record the up button, press up on your remote. Record the up button again, press the up on your remote again. No idea how it was working before, kinda a miracle, and unexplainable.

Okay, here is a config with that deleted. updated.fcfg

You have two keys assigned to pause: http://cl.flirc.io/m3tx Not sure why, you want me to delete those so you can re-record them? There is another button you could use which is the following: http://cl.flirc.io/m3mD But uses a second button. Would need a firmware update to solve that.

Your configuration isn't responding to my remote. Very strange. I just pushed an update yesterday. What could be going on is that your remote is a windows media center remote, and is also responding to the built in windows media center profile. Disable it: http://cl.flirc.io/m3zC Let me know if that helps. If it doesn't, remote might need a new battery.

looks like you have an original flirc. Is that right? With this version, any key that has previously been recorded, will wake your machine up. Unless you record a 'wake' key which can be found in the GUI on the keyboard controller. If you don't want to wake the computer up at all, you can disable this in the advanced settings.

okay, couple more things. After this happens, can you open the gui, go to device log, click to enable ir debug, and then press and hold a button. Save that and post that here. Also, paste the output of dmesg.

Can you post your configuration?

That's not available on this version, I have to implement that. I'll see if I can get it in on this next release.

Can you wait for this to happen again and do the following in a terminal: flirc_util device_log Paste the output here, let's see if the device gives us any clues, I believe I log when we detect sleep. What profile are you using on your harmony?

Which model flirc do you have

Okay guys, took much longer than expected. We filed a provisional patent for this early this morning, I can release the feature now. Should be up in the next day or so.

I have this, I'll give this a shot in a couple days when I get back home.

@apfelcast This is a different problem, which remote are you using?

Looks like I can confirm it. I built these on 17.1 of ubuntu, it's probably too new. The static binary is posted and has instructions. I don't know what to do. Do I build mint versions? Do I just build on an older version of ubuntu? This is getting a bit stupid.

What version of the firmware are you on?

I'm on the road traveling right now. Sorry for my delayed response Did you by any chance use zadig?

Okay, glad it fixed it. Basically, in the new version of flirc, I record more information about the IR pattern, including the space between frames. On the old version of the config, I never stored this information. When you load a configuration from an old device to a new device, I made up a generous number. This translates to erratic behavior on the new flirc if the time between frames is less than what's been stored in your configuration (the made up value). I use this information to figure out if you're pressing the button a bunch. So the space between frames is 32 (as an example), but I stored 150, my firmware thinks you let go and hit the button again because the time in between frames should always be equal. I've disabled trying to determine if you are hitting the button repeatedly if the value is the generous default I use if we never recorded the data. So you should use the configrutaion I created for you. Basically what I did, is had you record a key, where the new firmware captured and recorded this value in between frames, and then I replaced all the default numbers with the new number. This is going to translate to a more natural feeling with your remote, where it should detect fairly well if you are pressing buttons quickly. Hope that made sense.

Alright mate, give it another go. Pushed an update, try and get the latest, upgrade your firmware, and reload the original config. I'd like to fix this for everyone, I believe I got it.

What kind of flirc do you have? A metal or plastic version? You did everything right, however, you actually don't need to pair anything. Once you add the flirc - kodi profile to your harmony, flirc should work with it without any additional pairing. It's built in. But it should still work the way you did it as well. Can you tell me what's not working?

Completely my mistake. I pushed another update for windows. So to summarize, get that, upgrade your firmware, load your old config, let me know if that works. Once it does/doesn't, let me know what happened, and then load my config that I fixed for your normal use.