FlicTwist with FlicHub LR has bad latency every few presses

mosthated

While it's nice to finally be able to use the device after having it sit in a drawer for (years now?), there seems to be a somewhat repeatable and relatively huge latency spike in communication between the devices (happens exactly the same on both of my twist devices) that shows itself every 3-4 button presses.

The latency is between the physical device and the hub, from the time you actually press the button until there is any sort of communication received or shown via the hub SDK.

(Note, the FlicHub LR is hardwired, not using wifi. Though I don't think it would matter much for this particular issue either way.)

Ex:

Press button - response is milliseconds
Press button - response is milliseconds
Press button - response is milliseconds
Press button - response is 2.5 - 3 seconds from time of physical press until the very first log message appears.
Press button - response is milliseconds

... repeat this any number of times, the only difference is the issue might move to spot #2,3, but always happens after a few button presses.

The "very first log message" I am referring to is the following:

buttonManager.on("buttonSingleOrDoubleClickOrHold", function (obj) {
  log("Initial Press");

  // ... Rest of the code
}

This issue feels very much like it is firmware/connection between the device and flichub related, as I first noticed this when I initially received my flictwist/hub a few years ago when it came out. I just didn't bother to mention it at that point and put the twist in a drawer.

Now that the device has the potential to actually be useful, this random yet always present lag is annoying enough that I don't even want to use the device as I have had a lot of time to fine-tune the code for my Hue Tap Dials.

While they lack any sort of 'current rotation value' indication, they are always as close to instant as one could get and reliable. After a number of years building my smarthome, I have found those two qualities to be much more important than "neat and fancy".

That said, for additional context, I have tried every combination of resetting, reconnecting, reconfiguring that are available. It does not matter how close or far I am from the hub. I tested with the hub on my desk, button in my hand. I tried with the hub in a corner of the house farthest away from any other devices as I could be to ensure there wasn't any sort of interference from other signals, etc. The result is always the same.

I am guessing that this is just how it is, and that's that?

Edit: I captured some timestamps, generating a timestamp upon pressing a button on my keyboard and pressed the button and the keyboard at the same time:

Button Physical Press: 2025-06-19 14:32:31.705
Log Message In Hub:    2025-06-19 14:32:32.394 info: Initial Press

Button Physical Press: 2025-06-19 14:32:39.541
Log Message In Hub:    2025-06-19 14:32:40.045 info: Initial Press

Button Physical Press: 2025-06-19 14:32:46.322
Log Message In Hub:    2025-06-19 14:32:50.958 info: Initial Press

The last press had a latency of 4.636 seconds.

mosthated

Edit

Interestingly, when I went to go grab the LR to record the video, I left the cord I was using for power in the other room (the same cord I have been using since I first for it), and grabbed a different cord for power, I have done probably 150+ presses and have only seen the delay 2 times so far.

I had just recently moved it into another room, so I brought it back to my desk and plugged it in. I don't recall the issue being time-related (in that it's fine at first, but then later it starts acting up), so I will keep an eye on it throughout the rest of the day, testing now and then and report back tomorrow.

@Emil

I appreciate the reply. Yes, the delay is indeed reflected in the light flashing on the device itself.

I have the LR on my desk in front of me sitting on a little 5 port switch, so I am able to clearly see the light and the delay in the light flash coincides with the other findings I mentioned above.

I had opened and connected one of my Twist devices as soon as it arrived after the Kickstarter and the delay existed then (on whatever the LR firmware was at that time).

My second one, I only recently opened and connected the day you replied to my message in another thread about the SDK/feature update being available for Android. Both of these devices experience the same delay to the hub as of now (just tested again a few seconds ago with the 'newer'/just recently opened device) on firmware 4.4.2.

As for usage, I have a virtual light device setup on each, and rotation and press values are sent via mqtt, and there is a subscription setup to listen for current value to update the led. Prior to that (1 or two years ago, I can't say for sure), at some point I did setup the button press through the app to send an HTTP request. The delay happens the same no matter how I use the device, and seems to occur before any user code/actions are performed.

I was going to open the SDK console and using my phone, record a clip where the button, the hub itself (and light), as well as the console are all in frame so when I press it, the delay can be seen in realtime but wasn't sure how useful that would be.

Emil

@mosthated Hmm I just tried to reproduce this, but the latency is always instant for me. The LED on the hub should light up when the button is pressed. Does this have the same latency as well? Have you tried any other actions, like turning on some smart light? Just trying to figure out where the issue might be...