@baobei Thanks. I got reply from flic team and it was replaced with new flic button. New button working perfectly.
My observation is, it can work with one app at a time. To make it work with other app, it require to forget from previous app. And couldn't find any method in SDK which can identify with which app it is workable currently.
@domas Thanks for that info. I just found that we created a bug when we refactored the app in the beginning of January that makes getName() always return null... We'll fix this in the next Flic app release.
Hi Emil, I don't know what platform mrwhale is using, but I would be interested in this for the linux platform. It would be good for the OpenHab binding that Patrick Fink is working on to be able to track battery life on the flic buttons and report when the battery needs changing, similar to other IoT devices.
Same as @alex, I am curious as to what state the flic - rpi environment is in today.
Is it easy to set up, or easy to work with using linux bluetooth api or abstractions of it through Python or similar? Is it possible at all without being online?
Coding skills is not an issue.
Sorry for late reply. We are currently not considering any other release channel than Google Play due to low demand. If you don't rely on 3rd party apk sites you can probably install the app on a Google Play-enabled device and extract the apk from it.
Hi, I am having the same problem running applescripts. The Shebang is present and on the first line. The script runs outside of HaxWithFlic just fine but I get the Shebang error when using the flic.
Does anyone know how to fix this?
Our current solution is that 3rd party apps depend on the Flic app to deliver the button events (easiest is through intents). There are multiple reasons for that:
We can provide a small simple open source library that is easy to integrate.
The 3rd party app does not need to run a service in foreground mode (BLE connection apps need that in order to not be terminated while in the background).
It simplifies when multiple apps wants to use the same button. Most important, the Flic doesn't need to have a pairing to each app (and force the user to run the pairing process).
If we find and fix bugs or do improvements in our BLE code those fixes can be rolled out directly so that each 3rd party app doesn't have to upgrade their Flic SDK version.
@jaime-fernandez The UUID parameter on Android is the same as the buttonPublicKey parameter on iOS. You can use that to identify buttons across different platforms. Although remember that you can not have the button connected to two different phones at the same time regardless, so I am not sure why you would want to do this.
@yuvalshu No, the 500 ms delay can not be changed. If you want something else then you would have to implement your own logic to distinguish between click/doubleClick/hold using the raw down/up events.