@joacim I can only see a price difference for the same product? Setting up the normal flic is so easy so I feel no 'win' by buying the single ones. Personally then, I would always prefer options to do with the button. I could imagine buying a single for some use that seems useful but then never use it.

i did this once upon a time but i can't remember how. i seem to recall using my broadlink rm pro. i wanted to use the flic to pause/unpause qt video playback. flic was too unreliable. today, i'm using alexa/gh instead.

@adam-skelton87-1
Yeah, we did a full scale test last week and it worked REAL smooth. This idea could be adapted to be used in other similar situations, in many variations, for loved ones. Although my solution does incur an additional fee for using the Tropo service, for this solution it is only a small fee and easily affordable, much more so then say fancy subscription service, which makes it accessible to folks even on a budget. Of course, you can pick and choose what you use to make your own solution.

It seems you would benefit from using IFTTT "tags". That way you can assign many flic a single tag and then in IFTTT's interface you can create an applet when buttons with a specific tag is pressed.

Hi,

We haven't seen any issues with iBooks. Please email our support with details!

Hi! We don't have any research about, I'm afraid.

Hey! Please write to our support at support@shortcutlabs.com and explain which phone model you have and what it is that is not working.

Thanks! In fact, we just released a new iOS version that includes native page turning for forScore, Newzik and Setlists. See more here: https://flic.io/applications/composition

After a full day of the mysterious double red blink, this button suddenly started working normally again.

support@shortcutlabs.com did respond with some troubleshooting steps, but I never even got to them.

I'm not a fan of unexplained mysteries.

Seems like you need some community moderators... or a better way to block spam.

Can you compile it for El Capitan as well? :)

We haven't completed the IR feature yet so we are open to suggestions. Could you tell more in detail how you would like it to be? Like "decisions based on other environmental factors"?

@luis-reja Could you post the code you are using?
Basically, you should just be able to use the method on FlicManager that gets all known buttons (i.e. grabbed buttons) and then set an event listener.

No there are no plans for triple click. We want to keep it simple.

To workaround latencies in Bluetooth, it's the button's firmware that generates the different click events.

If you implement our sdk you could implement a triple click handler yourself by listening to the button down/up events and figure out when a triple click has occurred. But it might not be accurate due to latencies.