jason

Thank you, this is helpful. I'll need to think this one through.

I can’t support all versions of Linux. I’m really sorry. Just not financially feasible. We target Debian but it’s a appimage*, it should work. Don’t know why it doesn’t. I have no time to set up gentoo and debug this with everything I have to do.

I don’t follow, did it get stuck?

Can you post your logs?

Pushed an update with a few more fixes

It's the protocol, you need to record every key twice. Once I get back to development on this, it will be fixed. No inter-key delay in the second version of Flirc. Don't hit 'start' on the GUI. Essentially press the button in the GUI you desire to record. Press the remote button you want paired. Do the immediate action again. Every time you hit the same button on your remote, an alternating pattern is sent out. If you press another button before the same button again, some remotes just sound out the first button again. So it's critical you manually record each button twice and in a row.

Thanks for these, we are currently working on some fixes for these bugs.

It’s a binary table and I’ll turn it into JSON With the next major update. For now you can use this: https://flirc.io/config/ Upload it to that and you can read it. You wont be able to edit it though. But you can make sense of it.

Yes, my bad. The learning tab, sorry.

Enable the admin panel and go to the learning* tab. Then press and hold a button and paste those results here. Those fans use non standard protocols.

Can you save your config and post it here?

Thanks for reporting this, it should be fixed.

Links updated with build fixes

You beat me too it, I pushed the build last night and passed out. Thanks for letting me know.

Can you tell me what build you are running of the app, file->about generally, this is still a release candidate and the earliest versions were broken. If you get the one from here, it should be fixed Also, let’s keep feedback in that thread so I can better keep track of open issues. Please let me know there.

Also, if my suggestion above does nothing, enable advanced, and export the app log, throw it in a zip, and put it here.

Maybe it’s the button on your remote. Can you try one of the previous buttons on the remote that worked?

Sorry for the hassle. Can you tell me the version of the app and firmware

Thanks, I see the issue, and will get a fix posted.

Sorry, I mean from the 0.9.993 version

I didn't see this, can you save your config and post it?

awesome, thank you for reporting this and bringing it to our attention.

It's not stored in a file by default. It's in a react storage structure that can be found in the skipapp system directory. You can enable the admin panel and export the full app JSON file. Did you recently upgrade the app?

Thanks for letting me know. It seems the issue is with recording using the 'misc' device category. Here is a new version that should fix the issue: