Hi all,

I bought my Flirc back in February where the long key press feature was "coming soon". As far as i know it still is "coming soon" - Do any of you know when this feature is planned to be implemented?

I haven't put together a blog post in a while. But will do so soon.

https://flirc.tv/status_board

I'm trying to be as open as possible with what I'm working on. I've started both long presses and macros. I hope to have a release before the end of the year.

Feature has been published: http://blog.flirc.tv/index.php/2017/12/25/flirc-just-got-a-shit-load-cooler/

No gui support, it's in the commandline app: https://flirc.gitbooks.io/flirc-instructions/content/command-line-interface-guide/macros.html

I think I might be able to whip up some GUI support, it'll be crude, but should do the trick.

Happy Holidays.

 

 

On 26.12.2017 at 2:40 AM, jason said:

Feature has been published: http://blog.flirc.tv/index.php/2017/12/25/flirc-just-got-a-shit-load-cooler/

I have an issue with Kodi - if there is a fast sequence of press/release actions for a  button, Kodi sometimes treats it as a long-press action and does something that I don't need.
Can it be a consequence of that new feature?

On 2/3/2018 at 4:21 PM, arabesc said:

I have an issue with Kodi - if there is a fast sequence of press/release actions for a  button, Kodi sometimes treats it as a long-press action and does something that I don't need.
Can it be a consequence of that new feature?

Only if the button you are using is recorded as a long press. Otherwise, because Kodi also supports long press, you can try increasing their long press hold time requirement.

2 hours ago, jason said:

Only if the button you are using is recorded as a long press. Otherwise, because Kodi also supports long press, you can try increasing their long press hold time requirement.

Do you mean that Kodi interprets fast successive key-presses as a long-press action? I don't understand where that long-press action comes from.

kodi supports a second function assigned to the same key

flirc also supports this feature

The two can conflict.

Have you specifically recorded a long press with flirc?

10 hours ago, jason said:

Have you specifically recorded a long press with flirc?

No, there is standard Kodi layout in Flirc and standard key layout in Kodi, nothing special. There should be no long-press actions (e.g., for navigation keys) but they are.

@arabesc I have few questions regarding your setup:

1. Which Flirc model do you have?
2. What remote are you using? Is it an universal remote? If yes, what profile have you selected?
3. If you have new Flirc model (the metal one), please open Flirc GUI and open Device Log in File menu. Then select enable IR debugging and press few buttons on your remote which you're using with Flirc. Please save it to a file and attach it here.
4. Save your configuration and attach it here.

1. It's a FLIRC-SE.
2. One For All URC 6440, it's an universal remote, and I've selected a profile for some LG TV that uses all of the keys and doesn't use alternate codes for successive presses.
3. I don't think that it's a new model.
4. it will be done later.

Edited February 8, 20188 yr by arabesc

If it's Flirc-SE then it's a 1st gen model. You can try changing the interkey delay value in advanced settings. Try decreasing it by 1 and do some tests. If not enough, then lower it again. This controls the time window within which the next received signal is treated as a repeat signal instead of releasing and pressing again. This value will also affect the ability to detect actual signal repeats.

The new, 2nd gen model doesn't have that setting anymore as it records the actual signal delay value for each recorded button.