12/19/2023 0 Comments Flic button hubShortcut says that many customers wanted HomeKit support, but it wasn’t easy to achieve. You can supplement with additional button packs to a maximum of 63 buttons per home. Things get better if you know you want a bunch of buttons, a 6-button pack with hub coming in at $220 and bringing the cost down to $38 each, while the Mega Kit of hub plus 15 buttons for $400 makes them $27 each. The original Flic buttons from Shortcut Labs could control a reasonably wide range of devices – including Ikea, Nanoleaf, Lifx, Lightify, Philips Hue, Sonos, Spotify, and WeMo – but HomeKit support now makes them suitable for a much wider range of smart home products …įlic 2 Smart Buttons require a hub a starter kit of the hub plus four buttons costs $160, meaning $40 per button if you don’t buy more. This is the App ID for the Maker API in my Hubitat.Second-generation Flic smart home buttons now have HomeKit compatibility, along with multi-color LEDs to indicate the status of the device they control. Note that the number 81 will be different for you. This is the URL that you paste into the Flic app as an Internet Request action. Mine looks like //?access_token=abcdefghĬopy this URL, then edit it with the Device ID of you virtual button device, the Command (push/doubleTap/held), and Secondary Value (physical button). Once you specified your devices in Maker API, look for the URL near the bottom, which says "Send Device Command (replace with actual subscribed device id and with a supported command. I did not use the "Allowed Hosts" section. Doorbell Flic Button) in the "Allow Endpoint to Control These Devices." The Maker API just exposes a device to API commands. Now, I'm not sure what you mean about creating 1 action per Maker API? You don't create any actions there. I have one Flic button that I'm using as a doorbell, so I created a Virtual Button device in Hubitat called "Doorbell Flic Button", and specified that it has 1 physical button. Sorry for the delay, I was travelling and didn't get a chance to read your post.įirst of all, did you read the updated part of my post, where I recommended creating one Virtual Button device for each button? This makes things a little simpler. 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. So this is a no brainer for me, as I already own this button that was previously pretty useless to me. 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. And it was laughable that I would every spend over $100 US for their hub to serve a single $35 flic button. 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. For me personally, this make quite a lot of sense. So I was quite pleased to discover their Mac app. 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. 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. Just wanted to circle back to this thread and mention the Flic for Mac app.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |