@stevehurcombe Hi. We will take a look at this when we are back from summer holidays.

@Emil the app was the solution, it needed an update, now I can see the login button and it works again. Thank you very much!

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.

@mosthated The Android app with this functionality has now been released!

@sfmclaugh said in Looking for Smart Plugs that have "Toggle" in Alexa routines:

Want to control my lights w/flic2 plugged into smart plugs using one-button press. No clue what to buy. Current plugs only have "On" and "Off". Any tips?

Is that an Alexa routines thing or a device thing? My Leviton smart plugs have a "toggle" to control them via Matter, but the routines in Alexa offer only on, off, and brightness. I suppose you could use multiple actions in your Flic Hub configuration for that button- use Matter to do the desired toggle, then an Alexa routine to control the other actions you wish this routine to perform?

Well, I'm learning more now! Leviton did tell me that yes, in fact, their 4 device switch/controller advertises itself and functions as a "light" endpoint, and also 3 "Generic Switch" endpoints. So my hope here is that I would be able to add my 3 "Generic" switches to my Flic Hub, and then control my other matter lights/outlets/etc. with the switch, without having to add another Matter controller to the mix.

Is this in the future for my FLIC hub??

@sgemmen Thanks for this, finally got around to setting it up. It wasn't working at first but realised I needed to add the two helpers (boolean and number) for the targets of the service.

Now I need to work on using it to adjust all the lights in a room while keeping the relative brightness of them the same.

EDIT: Found this add-on which seems to work - https://community.home-assistant.io/t/relative-brightness-light-group/695450 - brightness changes are a bit jerky (not sure if this related to flic, the add-on, or something else) but it does the job for now.

@Emil This is getting ridiculous. The problem still has not been resolved and your support email team are NOT replying me.

If this product DOES NOT WORK OVERSEAS the. you should not be promoting it outside of the regions without proper testing.

This is not a cheap product and have been patiently waiting for the team to work with me to get this working for a year now. If there is NO INTENTION for this to work outside of the US via Alexa then this should be highlighted or else this is FALSE MARKETING.

To all users considering buying this for use (at least in Japan). This product DOES NOT WORK with Alexa.

@buckyswider Hi @Emil ! So I installed that beta Matter code on my Leviton plugs and switches...and VIOLA! They are now all advertising the proper tcp service all the time. (At least for the first 24 hours or so). So it seems like we are good. Presumably now the FLIC hub will never show these as "offline" again. Thanks for your counseling!

I do have another Matter related question that came up dealing with Leviton support. But I don't want to be guilty of "thread drift", so I'll start a new thread.

Thanks again!

@pianosimon Hi! Are you using Flic Universal or the Flic app for macOS?

@pico We currently use QuickJS and it seems like that js engine does not support that Intl feature.

We might add the feature to set time zone, it can be useful for a few other purposes as well, e.g. in timestamp header for our Internet Request action. But right now I suggest to use the workaround I suggested.

@djadin14 maybe you got a defect unit. You should contact support at https://flic.io/support and see if you are eligible for a replacement.

@kerry-thacher Hi!

Unfortunately, no. At least not from what we have found.

You can use the "alternative keymap" in the Universal Keyboard action to prevent the on-screen keyboard from hiding while the Flic is connected, however, this also limits what we can do with keyboard commands.

(Note that you need to "Forget" the Flic from iOS Bluetooth device list if you change the keymap for it to have effect).

So Apple requires the device to identify as a keyboard to be able to do certain things, like trigger system wide keyboard commands (which is what this video suggests as a trigger for Shortcuts), and this enforces the behaviour that the on screen keyboard disappears.

Sorry about this, it would certainly be a neat feature to be able to trigger iOS Shortcuts without affecting the on screen keyboard.

@j that is the simplest way to get automatic access to your flows. You can probably set up your manual web hooks if you want, using the http request action, but you need to manually enter the url.

@gabrielmgrossman Please file your issue to https://flic.io/support.