jason

Can you format the device and post the configuration? It's possible. Don't worry. I'd get you a new one.

Which version of the firmware are you using? It could be your remote losing battery life. Flirc is so timing sensitive, as the signals drift over time, that would trigger re-learning. Save the configuration in a known working state, then when it breaks, save it again and post both files. What's your firmware version?

Okay, how about just doing the following in the terminal: /Applications/Flirc.app/Contents/MacOS/Flirc I'm still trying to get the previous versions...

I'm going to get 10.7 and 10.6. Seems to be fine on 10.8. I'll get to the bottom of this after I reproduce it. Could I trouble you to launch the app through the terminal: ./Flirc.app/Contents/MacOS/Flirc This will spit out a bunch of logging information. Thanks so much for all the help Loop.

I released an update, could you guys let me know if that worked? Until I get a machine running the previous OSX, I can't know for certain, but I had a mistake that was fairly obvious and I'm nearly certain this will fix it. Please let me know.

As soon as I get all these v1.0.0 bug fixes out, I will return to firmware. I'll have a blog post on the newer features that will be implemented.

Okay, next release has been posted, v1.0.2 This will auto-update your device to the correct image. ** EDIT ** It will only auto-update should it see that you are on one of the latest release candidates.

Thanks so much for the acknowledgment, a bit exhausted, so it means a lot. posting here as well as your original thread, anyone on the release candidate versions will automatically get updated to the correct version with the v1.0.2 release.

I had a bug in my v1.0.0 GUI on certain devices, can you guys try the latest release: Direct link: Flirc Setup.exe [ v1.0.1 ] Please let me know if that fixes it, I haven't gotten any feedback.

The windows 1.0.0 release has been publish, try that and let me know.

Hey, you caught me in the middle of trying to post an update, could I trouble you to try again?

I've fixed this but I haven't finished my packaging scripts. Just follow up with me at support@flirc.tv and I will send you a binary to fix this. I published the mac version, and will follow up with the windows and linux versions shortly.

I've released a 1.0.0 version of the mac, I'm trying to get the windows and linux versions out.

Thanks so much!

I'm going to post something tonight, hold on guys.

If you fire it up again, it should try to fix it. Close the GUI, and re-open it. If it doesn't, could you tell me what the text status bar on the bottom says? Does it give you a firmware version in the lower left?

I think you might be able to get rid of that message, there might be a diagnostic menu. It should let you, make sure it's labeled .fcfg or zip it up. I'm sure others would be thankful.

What's the remote control? I know it's a harmony, but what's the profile? Samsung? Panasonic? Flirc? Something else?

The configuration on your flirc is definitely broken. Upload the attached, and then try recording your keys again. I bet that fixes it.

can you guys post screen shots of these. I don't know what you are referring too. I need to repeat the setup.

I've got to get to the bottom of this. Can you post pictures of your harmony settings? Advanced timing settings. Also, which remote control is it? The XBMC-Flirc profile? Post your configuration details too. ** EDIT ** I mean attach your flirc.fcfg file

Thanks so much for doing this, it's great, and I'll try and add something in the GUI for PS4, shortcut keys so people don't have to do this. Follow up with me via email so I can get your info to send you a unit. Thank you again.

From what I remember, the way it works, the higher the front number 51-flirc vs 99-flirc, the higher the prescience. Unplug/Plug the device. That usually triggers a udev rule to re-trigger

Something may have failed in the install, or your distribution changed the way udev rules work. I feel like they change it every distribution release. Basically, you need a rule in /udev/rules.d/ You should see the one the installer puts there. It basically tells the system to open the USB device read and write for all users. I don't know why they would restrict it by default, always seemed stupid to me.

Capital 'F' #Prompt>: Flirc