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.

@rickard Yes! This will be possible, but note that we have not yet started to ship Flic Duo. We still need to finalize the Hub SDK events for the Duo so I can't give you an example right now. For MQTT itself, please see https://github.com/50ButtonsEach/flic-hub-sdk-mqtt-js.

@buckyswider @Emil Agree, would be nice if there was a for the hubs to synchronize the configurations across a single account.

Hello,

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.

@Emil Hey Emil, i‘d like to push this topic back on the table. There would be so many possibilities if all the functions triggered by a Button could also be launched via HomeKit. Especially functions of the ir blaster. I’d really appreciate if you guys implement this feature. Thank you all.

It was a brand new hub that had unfortunately not yet been processed from the factory logs. It is now done and you can go ahead updating the firmware.

@Emil said in Event Logs?:

@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

@Emil I can't find the video, but

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.

@beelzebomb well as it's powered by USB, then any kind of USB supply should work, per definition.

@willliam The Flic Hub can generally connect to servers that use Let's Encrypt certificates so there must be some other error.

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.

@dunderovic so it fails when you try to pair the button regardless if you try to pair it to a hub or phone?

Please attempt to pair to phone without hub, then go to settings in the app and press Submit Bluetooth log. Then we can have a look.

Remember to keep your flic pressed for at least 7 seconds while you pair it.

@szczepan-kuzniarz Thanks! The new ES version is more strict that "new" must be placed before a constructor. We have just released a new firmware update that is more relaxed regarding creations of new Sockets, as a workaround for users of that lib.

@bambi2000 hello , I have the same problem . All button works very well about 4 years and now it doesn’t works . Do you find a solution ?

@joacim-n-linder
Matter bridge on home assistant would bridge home assistant controllable devices as matter devices to Flic. But that is oppposite of what would be useful. I have hard time seeing Flic being used as the "center of the home automation" when you have Home Assistant. So Flic hub would need to be the matter bridge, not the controller.

Any news in that? We really can‘t use flic in our school wifi without this…

We have just released Matter support, which Wiz also supports. I suggest you to use Matter instead since that is local and hence has much lower latency. See https://faq.wizconnected.com/hc/en/3-wiz-legacy/faq/603-how-to-install-my-matter-ready-device-to-matter-hub/ how to generate a setup code which you can then use in the Flic app. Note that this is only supported when the button is connected to the Flic Hub (not directly to phone/tablet).