jason

sorry, I have a lot on my plate and I jump in and out. I missed the subject. You can record over any key in the profile so you can remap it. It searches through the personal profile before searching rom. Does that make sense or answer your question?

I'm sorry, what is this in reference too?

The 3.0 firmware doesn't have support for built in profiles yet. It's actually done, I just need to push it. For now, you're doing it correctly, just map them manually. I'll try to push it soon, it's missing a few keys at the moment. The algorith has been improved a bit too.

yeah, I know what you mean, just watched. Those logitech harmony software guys are a bunch of idiots. What are they thinking?

I'll see if I can get in touch with someone to fix that. Sorry = (

No problem. I'm trying to decide if I should keep it right now or have it so any key wakes the machine. I'm struggling with this a bit as I see too many people accidentally waking their machine. Sorry for the trouble and I'm sorry this wasn't more obvious.

no, it's a modifier key and can't be sent by itself. What about just an unmapped key combination? ctrl+shift+alt+h Something arbitrary should work that doesn't disturb xbmc, no?

shoot me an email, I'll take care of it.

why not pair the power button for your TV on your remote with some arbitrary button like space bar?

try this: https://flirc.zendesk.com/hc/en-us/articles/200904676-Getting-flirc-to-wake-up-your-computer

Try the new beta firmware:

Fixed. Got a new algorithm that puts that to rest: http://forum.flirc.tv/index.php?/forum/73-firmware-30/ Still some missing features, but I'm working on it.

or 3.0 rc6. I'll make note of what each features in the release notes.

Hey Brad - I've got a new firmware image that's in the beta release section of the firmware. While the easiest work-around is just to record every button twice sequently, with my new algorithm I will be able to at least detect this kind of remote and prompt the user until I figure out a way to determine what the second press is without the user pressing it.

It's not implemented yet. I re-wrote everything. Hang in there, I'm just about done wrapping up built in profiles. I'll try my best to finish that one before the weekend. If you want to revert, let me know by pm.

http://forum.flirc.tv/index.php?/forum/73-firmware-30/

it's covered in this great tutorial:

keep the interkey delay at 3. What remote control are you using, I'll take a look. i do have some improvements I will push soon.

I'll try and build a 64 bit version later tonight, what distro are you using?

Try the latest beta release.

shoot me an email at support at flirc.tv, thanks yawor for letting me know about this thread.

what do you mean it's not repeating commands? It's not forwarding button pressses or it's not detecting when you hold the button down?

Yes, please make sure you're on the 3.0 firmware version, and you clear your configuration and start over. After that, please let me know.

Hey Summers, I appreciate the analysis and detailed information. Really helps. I would love to be able to replicate this, I have my scope so I would be able to see it. There was an account of another user posting some information on not having his media equipment on an earth ground, which caused strange misbehavior. This is definitely pointing to a noise issue, however, I'm not sure what the potential fix would be. There are three issues and causes. Raspberry pi problems with power supplies. - Shitty power supplies are causing flirc to get stuck in the bootloader requiring them to be taken to a computer and fixed with the gui. Bootloaders have been updated with a workaround in later versions of the device. Light problems. There are several accounts that lights are causing indefinite key strokes, repeating and noise problems. I've released an updated firmware version to address this: EMI interference (could be related to what you've described). When I have my laptop power chord by my flirc, I see this issue. False triggers and indefinite key presses. The firmware image released above should help with this too. This problem described by you. I can't add any more filtering, any more capacitance on my device and the raspberry pi will actually reboot because I triggered an inrush current limiter. This is going to require investigation and take time. Not sure how I reproduce this Thanks so much for the information, this should help and I'll meet with my buddy to go over possible ways of reproducing this.

Check the beta thread I have the third version of the release candidate up. Please please let me know if it helps solve this.