Same problem here.
The Flic2 buttons are much less reliable then the Flic1.
Something to do with the hardware switch bouncing?
Some buttons works some other don't repsonde correctly to the 3 form of click.

I agree to this.
Would be nice a Flic wereable version, like a Fit wrist band (3 buttons?)

On a iOS implementation, scanning for a Flic2 Btn, I sometime receive this error:
Operation couldn't be completed. (com.shortcutlabs.flic2lib.buttonscanner error7.)

• the button is unpaired and is not on the bluetooth prefs of the device
• usually happens trying to pair another button, after the first that paired fine (after starting the SDK)

Supposing that this is not introduced by my developer, that implemented the SDK, what is error code 7?

There should be somewhere an easy to find "numbered" list of Flic error, so that we can take care of problems.
Is there?
Thanks

I am receiving this error, trying to pair a Flic2 button on iOS 13.5.1 using the sdk:
"The operation couldn't be completed. (com.shortcutlabs.flic2lib.buttonscanner error 1)"
Is there any way to find out what's wrong?

As of two days ago I was using, on a iOS 9.3 iPad, the flic1 buttons and the Flic App 2.2.16. Everything worked fine.
Yesterday there was no trace of my Flic1 button anymore on the Flic App and I am not able to pair the button anymore:
error code f8: "There was an error trying to connect to our servers. Please check your internet connection...".

• Internet connection is fine
• the button pairs fine with FlicApp 4.0.5 on iPhone iOS 13.5.1
• before trying on the iPAD I am sure that the the button is not paired with any another device
• the button glow red on first click but then the pairing stops half way trough

While I think the metal clip developed for the Flic 2 buttons is not in my opinion a great improvement (it hides the led light, for example), we find it problematic to use it because of the adhesive back of the button, that it is also not removable.
Often, trying to clip the button to a shirt, the protection plastic gets peeled away.
Are you planning any improvement on this?

Is there a reason why the Flic2 framework ask on Android (not on iOS) to authorise position location?

Our developer, that is implementing the Flic2 library for our App, told us that in your API there is no way to detect, on opening the library, if the system bluetooth is on or off and, consequently, advise the User.

While we solved that on iOS, I would like to know if there is a way, in the Android API, to do this.

As you can image, having the bluetooth off without knowing it, the user may think that is the App that doesn’t work and we have no mean of how to advise him of this fact.

Thanks

I think that when on mobile an App (with the Flic library) goes to background, while background clicks are not enabled, there should be a way to disconnect buttons or close the library after a while, so that they save batteries level.
The typical user behaviour, once done, is to go to another App or close the cover of a tablet and forget about it. Rarely they quit an App.

That said, while i think there is a time-out on Android, I am not sure how to manage this on iOS.
Can someone please explain?
Thanks

Flic2Lib.
iOS: The callback on is not sent when I manually disconnect a Btn. Works fine when going out of range.
Android: works fine on both cases.

iOS 13.3.1 Android 5.0