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.