To find out how the request the Flic hub makes, you can use a service such as requestb.in or postman.

We are slowly rolling this out in different regions. Stay tuned.

I, too, am a new flic button/hub user and want to use the button to send myself an SMS. I couldn't get it to work on IFTTT, though that service seems to think it's possible and everything is properly connected. I WAS able to get it work fine on Zapier, however. Unfortunately, ideally I'd like the button to trigger an SMS to two different numbers (same message, though). While Zapier supports this, and I got it to work, it will cost me $240/year after the trial period, and that's too much for me, so I'm still looking around for another solution (maybe Microsoft Flow). Zapier supports a single SMS/button press for free, however.

@anton Hello! I just wanted to update you and let you know that so far, everything you have helped me with on this project has worked quite well. I still don't have any clue how to autostart terminal, but so far it has not been hard to just restart it when I need. What I'm wondering about now is this - I've bought six more flic buttons to add (these will complete what I've planned on the virtual organ), and need to add them to the hub. I've got enough keystrokes left to assign to them, but am now wondering if I need to do anything to the python program to allow it to recognize them and send the internet request. Could you advise? I'm adding to this thread instead of starting a new one, in order for you to place it in context. Thanks! Diane

We are aware of this. Before we have competed support for these new devices, you can use flic with Homekit to control them.

I know your post is old, but I've been struggling too with connecting Flic 2 and Home Assistant. Using Flicd addon didn't give a stable integration, but this is a workaround I've found was quite stable. Works only with a Flic Hub and Apple Homekit running! In Home Assistant, set up an input boolean for single, double and hold for each Flic button. That's three input booleans for each button. Then expose Home Assistant to Homekit via the Homekit integration. You should now be able to control Home Assistant entities in Homekit, including your new input booleans. In the Flic app, set up your Flic button to run through Homekit In Homekit app, set up the button to turn on the input booleans corresponding to single, double and hold press. You can now create automations in Home Assistant, that fires when the states for your input booleans turn on. Also make an automation that turns off the input booleans again.

@Emil yes they do, thanks a lot Emil.

Hi. Flic's responsibility stops when reaching IFTTT's servers, so if you have any issues with Yeelight through IFTTT, you'd better take that up with IFTTT or Yeelight.

@Emil yes, I think SmartLife is back on IFTTT but I imagine most users won't want to buy an expensive subscription to go beyond their free IFTTT account limit of creating 3 personal applets so they will be reliant on other IFTTTers publishing a relevant working applet for general use. Perhaps the Flic Team could tell Flic users about an alternative to IFTTT - set up a sequematic.com account with appropriate automations and program Flic to send an internet request to run the automation.

Oh easy! Thank you

You can use a tablet also.

@Emil Hi Emil, thanks for the reply. To be honest I think it should simply mimic the keyboard when the universal keyboard is selected. So the user would click On Hold for the button option, then select Keyboard under Universal, and under this setting, it repeats on hold like a keyboard, (repeating the keypress until released. I really like the way the Universal app works currently. It's very self-explanatory and super easy to set up. This function is also massively for the Discord app, (push to talk where you hold the button to talk and it mutes the mic once release. I genuinely think if you did the above and unlocked it the sale would rocket in the gaming world.

Thank you for the swift answer! Ok, always active is good news. But a scan interval of 1.28 seconds sounds a bit worrying. Does that mean that a) the latency is always 1.28 seconds or b) that the latency is at least 1.28, but can vary depending on how long from an interval I happen to press the button? This is important. If a), then I can learn to compensate for this, to always time the sound effects 1.28 seconds from the press of the button. Not fun, but doable. If b), how long could the variable times be? This makes a huge difference for the usage I had in mind. Also worth mentioning is that this is a Flic 1. Are there any differences for Flic 2.0?

A foreground service should be enough (at least according to Android's official documentation). A wake lock should not be used/needed. This works perfectly fine on "original" Android devices such as Google Pixel devices. Some chinese phone manufacturers might neglect the intended behaviour for a foreground service and kills the process anyway though after some undocumented rules, unless the app is white listed or similar. The sample application at https://github.com/50ButtonsEach/flic2lib-android-sample uses a foreground service. You can check that out.

Two short red lights means the battery is under 2.65 Volt.

Is it possible to achieve this with the Flic 2 Hub somehow? It would be a very nice feature to have one (1) button to find multiple phones in the house.

Hi. For these kinds of questions, reach out to https://flic.io/support so that we can help you diagnose the issue.