Any progress about the Flic integration into ST?
I was so excited about flic until i saw this question.
They’re Bluetooth. I have an always-plugged in tablet which is my home automation control center. so my Flics at home will be tied to that, not my phone.
Flic works well as an add-on to a home automation system that already has some bluetooth device to control them, but not if they have to be tied to your phone always
Edit: Unless you like to have buttons al over your body and be touching yourself all day
I received 6 Flics. Using IFTTT to control Smartthings things, I am successfully controlling lighting (On/Off) with the attendant delay of using IFTTT (about 8 seconds on my end).
Got mine, really like it. My delay is shorter, more like about two seconds using IFTTT. They can also be used to start a Harmony activity.
The peel off adhesive seems to work really well, but if you have little kids you’re going to want to secure it because they will definitely want to put this in their mouth.
I wrote more details about it in the supported buttons and remotes topic
This one can solve a lot of use cases very simply. But you may have to stalk Amazon to get one sooner than an eight week delivery time .
JD, I have to be missing something. These buttons connect to your phone over Bluetooth right? If your phone is off or out of range these buttons do absolutely nothing. Do they have a hub or WiFi connection? If they are WiFi wonder how the battery life is. I’m sure I’m missing something I haven’t paid too much attention to them.
Yes, they have to be paired to a device that has both Bluetooth and Wi-Fi in order to use IFTTT, and that device has to be present. There’s no bridge device. The flic itself is Bluetooth only and battery life should be good, comparable to an IBeacon.
At my house, I have two tablets, one on each side of the house, which serve as home automation control centers. We use the dashboard to display, but we have all our apps that need to run in the background running on them as well. The house isn’t that big, about 1500 ft.², and, as we’ve discovered for iBeacons and HomeKit, we are getting full Bluetooth coverage, but divided into two zones.
So my flic is paired to the tablet, not my phone. And the tablet always lives in the same place at the house, so any flics being used as buttons for the home automation devices installed there will work just fine.
People who are pairing the flic to a phone have to have the phone within Bluetooth range of the flic or the flic just won’t work. That will meet some of these cases, but not others.
Ever see the Satechi bluetooth buttons? Im wondering if these can be used with IFTTT?
They have to have their own IFTTT channel. I don’t think I’ve seen them there. But it’s easy to check the channel list. www.ifttt.com
Or use tasker on android?
So first test today with my service dog. Flic worked great! The single press is a much lighter touch than I expected, so it was easy for him. This gives us a lot of good options.
I must of have missed something @JDRoberts. What are you having your service dog do?
My experience with Flic has been sporadic. I’m using it as a switch to control a couple of lamps. Using IFTTT i’m getting response times of anywhere from 3 seconds to 2 minutes. Hard for me to deal with anything beyond 5 seconds really.
I noticed one of the actions available in the Flic app is an HTTP request. Screenshot below. I imagine this may be a gateway to an ST integration. I also imagine that you’d be able to get quicker and more reliable results going this route over IFTTT.
My own coding knowledge doesn’t go beyond Apple Automator, so I’m a bit stuck here. Anyone want to take a closer look at this or at least let us know where to start?
I mostly use echo to control lights and other things that need to happen very quickly. The button is a backup plan for something, particularly if for whatever reason I want something done quietly. Or if the room is so noisy that echo can’t hear. Or if it’s one of those days when my own voice is very slurred, which happens sometimes.
Right now, the plan for the first button is just to turn the entertainment center on and off. So it doesn’t have to be as quick as a light would be. I’m getting a pretty consistent eight second response time from the flic via IFTTT which is just fine for this.
The yellow button on the left side of the entertainment center is a flic. I can push it with my knee from the wheelchair and the dog can push it with his nose.
I also plan to eventually have a flic that will activate an automatic door opener.
As far as the HTTP method, sure, that should work. That’s how Dave glass originally set up IBeacons/SmartThings integration.
Instructions for getting Flic to send GET requests to SmartThings endpoints:
Copy a URL for either On,Off, or Toggle from the website that you are
brought to after installing the smartapp.
- Paste the URL into the Flic app, select “GET”, and Show Response > No
You will have to do this for each on/off command that you want to have a Flic send.
I’m still waiting for my Flic’s to be delivered, but I’ve tried this with a virtual Flic and it works fine.
Excellent!! That works great. 1.5-2 seconds every time. I was going to spend the day learning how to write a smartapp, but looks like I don’t have to just yet.
Thanks for the tip @nelemansc!
So in case anyone was looking for other buttons, take a look at these:
I installed these at both ends of my cabinets for my wife.
This example is all well and good, but ideally I’d like to be able to install a similar application that would provide FULL REST endpoint functionality for all smartthings device types, not just switches.
Anybody have any thoughts on that?
Or can someone from SmartThings chime in on if you’re actively working with Flic to get support going?
Have you had a chance to look at the developer docs? Or the forum section of this community for developers? It might be of interest. For example:
@JDRoberts, nice find. If i can pass the access token via a “get” command, then Flic would work… that’s what I was sturggling with, since their GET / PUT commands didn’t allow header parameters.
I’ll play with it now, awesome find!