Even if I remove, reset, and add button back they seem to be placed randomly. Some in the first spot, some in the last, some in the middle.

Via the providers though its fine, didn't think to look there,

Thanks 🙂

If you use the device manager, you can manually assign a specific firmware version.

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.

Same problem here with the "Get contents of URL" action, works when tested via the Home app but not with the actual flic button. Was working fine before 18.2.

https://community.flic.io/topic/17290/can-t-connect-to-hub-how-do-i-reset-it-resolved/5

Oscar's post at the bottom was ANOTHER source that had me trying to wipe at 22 seconds.

The Wireshark tool cannot be run from within a web browser. You must download the software and run it. I'd appreciate if you could try this. After starting the program, you select "Capture" on your wifi or ethernet interface. Then it starts to log packets. At this time, either run the curl command as instructed in my previous post. Or, if your TLS server runs on the same computer as the one running Wireshark, please try to access the https server using the Flic Hub. Then stop the capture, save, and send me/upload the capture file.

@bytheedgeuk We will investigate this. I'll see if we can change to make it possible to omit the value entirely instead of sending an empty bytestring.

I noticed after the latest app update I can get this to work.

Thanks @Emil

Maybe, just maybe there is a way to get a flic hub to work using Homebridge, there is a plugin for HomeBridge, install this and then run it as a child bridge, it will show up in Homeassistant, the code for Flic in Home assistant can then be found in the Flic Homebridge plugin, click on the Child bridge icon in the plugin to retrieve the code.