Good afternoon all,
@Emil i am also eagerly anticipating HK compatibility since it was promised at the launch of Flic 1 hub, which I bought, and promised for the Flic 2 hub, which I also bought... So although sadly I am used to non-delivery of promises by now, I remain an optimist.
Yet as 2020 is drawing to a close, now is definitely the promised "Late 2020" - unless you're planning a Christmas special.
So, Any progress on Homekit developments?
Davy
@emil You guys did keep it exciting, waiting till December to pull the rabbit out of the hat. My sincere congratulations, it must be a big milestone achieved for the team.
Reading the instructions this morning, one worry starting niggling me, and @isolating just confirmed it.
Is it true that the homekit integration is an either/or choice, so either a flic gets HK options but none of Flic's current platform, or the other way around?
I had hoped that HK triggers would be added to the Flic platform and its current offering of options, but its indeed a homekit adaption, not integration.
If the Flic button gets adopted by HK, I assume it will be unlinked from the Flichub and become an ordinary (but cool) Bluetooth button, e.g. like Logitech's pop?
Does that mean you have to buy a Flic hub LR for a one-time adoption per flic and becomes obsolete?
Good afternoon all,
@Emil i am also eagerly anticipating HK compatibility since it was promised at the launch of Flic 1 hub, which I bought, and promised for the Flic 2 hub, which I also bought... So although sadly I am used to non-delivery of promises by now, I remain an optimist.
Yet as 2020 is drawing to a close, now is definitely the promised "Late 2020" - unless you're planning a Christmas special.
So, Any progress on Homekit developments?
Davy
@Emil I was wondering whether the issue of migrating buttons between Flics has made any progress? Also still keen to understand what the barrier is, as asked below.
@Emil good evening,
Could I ask why? What technical barrier can’t be broken to meet this basic user need? I’m no computer scientist, but I am an electronics engineer - close enough to by puzzled by this lack of functionality.
Already the app connects to the hub and can read the configuration of the buttons. That app is also used to configure buttons via other hubs.
If the same app can read and write configurations of the buttons, then why can't the app:
A solution would be appreciated by many, as this question is so frequently posed to Flicteam.
In my case, having two hubs and not being able to migrate buttons was plain annoying in the beginning. But when I bought the hub LR to replace an old hub, it became a real irritation. Every button has to be reconfigured by hand, action-by-action. It means that my hub and new buttons are in the drawer since autumn 2019, since it's too mind-numbing a task to start.
Davy
@oskar good morning, 8 months have passed and there is still no integration with IFTT and / or stringify? Their services are growing every day and I'm losing interest in even using flic.
I like the buttons but the options I want are only controllable via IFTT or Stringify. If they're integrated in can bridge them together.
Do you have an update?
Davy