I'd also like to second Ron request for native Flic Hub integration. Unfortunately nobody had mentioned one the unique feature of the Flic buttons, which no other buttons, as far as I know, have. They are waterproof and they can be placed in the shower, outdoor, etc. I'm currently using them to control Spotify player in the shower and it is very convenient.
3 Likes
I believe they are water resistant, not waterproof, but still that is a cool feature. Agreed.
I didn't know that. I think one or more are going in my shower now 
That's for sure, you can't dive with them. But I can see how they would work in the shower based on the design. Perhaps not in direct line with the water spray but a wet finger should be no problem.
I'd also like to second Ron's request for native Flic Hub integration.
1 Like
I'd like to add a +1 for native Flic Hub integration please.
3 Likes
In case anybody's still looking for how to integrate the Flic Hub with Hubitat, I just managed to get this working quite easily using Hubitat's in-built API. I'm assuming that the Maker API wasn't available at the time this thread was started, but now that it is, this integration is actually quite easy.
I created a virtual button in Hubitat, and I specified that it has 4 physical buttons, because I have 4 Flic buttons. I then configured the Maker API to expose control of the virtual button device, and then formed the appropriate URLs for the Flic Hub to use for its HTTP GET request.
The general format looks like this:
http://192.168.x.x/apps/api/81/devices/[Device ID]/[Command]/[Secondary value]?access_token=abcdefgh
In the case of Flic buttons, the Command can be push/doubleTap/held
The Secondary Value is the virtual physical button that I want to target (Remember I specified that my virtual button has 4 physical buttons)
eg. If my virtual button's device ID is 99, and I want the Flic Hub to send a double tap event for button 2:
http://192.168.xx.xx/apps/api/81/devices/99/doubleTap/2?access_token=abcdefgh
I'm quite happy with the results. The reaction time is great, and the range between buttons and hub is quite reasonable.
The Xiaomi buttons mentioned above look like nice options, but I already had my Flic Hub and Buttons, so I was really interested in getting them working with Hubitat 
[UPDATE 2019-05-09]
I've made a slight change to the way I've set up my Flic buttons. In my original guide above, I created one single Virtual Button device, and then specified 4 physical buttons. I've since decided that this makes some things unnecessarily complicated, because you can't change the name/label of each of the buttons. eg. When I write a rule in Rule Machine, I had to remember which number each Flic was assigned to. So I found it much better to just create a separate Virtual Button device for each Flic.
5 Likes
I did the exact same thing. The best part is that the Maker API and Flic hub work over LAN so the results are instantaneous!
thx @jason-lane, that sorted me out with a new doorbell button
I didn't realise that the White Flic buttons glow in the dark a little so now I've got a Glow in the Dark Doorbell button !!
Very nice.
1 Like
Cool!! I've also used one as my doorbell Thought I didn't realize (or forgot) that the white ones glow. Good to know!!
GREAT write up! I've got one button all setup and working perfect. Now to find a use for the other 5 buttons I got with the flic hub. 
2 Likes
Same.
I wondered if I could train my dog to press one when he wants out 
I was reading the top of the thread and the first thing I thought was the same thing, funny I saw your comment when I got to the bottom of the thread
1 Like
you have to have the Flic hub, right? I've only got buttons...
Hey Jason,
Is there any way you could help me out? I'm new to all of this, and have a Flic Hub that I'd like to use. This is what I've done so far.
Using the Flic Hub, I assigned a click to do an Internet Request. I put "http://[HubitatIP]/apps/api/23/devices/[thedeviceID]/push/?access_token=[theaccesstoken]"
Then on Hubitat, I added the Maker API. I created a virtual button called Flic and selected it in the preferences of the Maker API.
Then I used the Rule engine to create an action. When the Flic virtual button is pushed, then something will happen. Not sure what else to do. I noticed you used 81 in between the api and devices slashes in the HTTP GET request, but in my Maker API it was saying 23. Not sure what that number represents anyway.
Any ideas or ways you could help me? I am a teacher and I'm trying to integrate the Flic buttons in my classroom. Thanks in advance for any help you can offer!
Dan
Hi Dan. I believe the 81 (for me) and 23 (for you) are the app ID of the Maker API on our installations. You should stick to whatever the Maker API shows in the generated URLs.
It looks like you may have left out the button number, also known as the 'Secondary Value' for the command. It's the last parameter, just before the "?access_token"
Try adding the button number and see how you go.
Sorry for the slow reply. I haven't tried it without the Hub, and I'm away from home now, so can't really test this out, but you could see if the Flic app on your phone will also allow Internet Requests to be triggered by Flic Buttons without a Hub.
Of course, these buttons will only work if the phone is within Bluetooth range of the buttons.
Looks like you've missed the button number from your Flic string.
My strings look like this:
http://HUB IP ADDRESSS/apps/api/615/devices/1314/push/1?access_token=3c80987e-c91b-49ba-b785-74dde0541978
note the " push/1? "
Give that a go.
My Flic Doorbell (with Flic Hub) works great.
Just wanted to circle back to this thread and mention the Flic for Mac app. It's been publicly available since September of last year, but I have not been up to speed on what they were doing, since I am so over my love of their ridiculously expensive button, in favor of mesh capable Xiaomi Zigbee buttons, or even a Samsung SmartThings button.
However, when I was about to order another Xiaomi button last night, it occurred to me to find out what was happing in the Flic world. So I was quite pleased to discover their Mac app. For me personally, this make quite a lot of sense. I hated the Idea that I needed to either kill a perfectly good battery on a spare iPhone by leaving it plugged in all the time. And it was laughable that I would every spend over $100 US for their hub to serve a single $35 flic button.
To my delight, there is now a Mac app which can run in the background of my MacBook Pro, which is always running anyway to serve Homebridge, Google Home Assistant, Castweb API and Insteon Server for HE Insteon support. So this is a no brainer for me, as I already own this button that was previously pretty useless to me. Just as the iOS app and their hub does, the Mac app works perfectly with HE local end points! Much faster and more reliable than was previously possible with cloud end points.
thanks, very helpful 
1 Like
@jason-lane Hi Jason, I'm very new with hubitat and also has got flic hub.
I've read your instructions, but since I'm very new with hubitat, I'm slightly confused with the Maker API bit.
I've created the virtual button as you have put in you instruction. I put 2 because I only have 2 buttons.
but this is where I'm slightly lost....Is it correct that I can only create 1 action per Maker API? because I can only enter 1 url (for 1 action)
If you can send me some of screenshots, then that'll be much appreciated.
Edited:
Do I then enter the same URL in both Maker API and the button?
Do I leave the Allowed Hosts (for CORS) blank?
Do I still need to select the delivery for the "Allow Endpoint to Control These Devices" section?
sorry for the many questions
