The new app is now live!

Hi. Each Android device has both a hardware limitation and a software limitation which unfortunately sometimes is lower than the hardware limitation. You will usually see the limit between 7 and 15 devices. See https://stackoverflow.com/questions/41365009/what-is-the-max-concurrent-ble-connections-android-m-can-have.

If you integrate your Android app with Flic, you will only get access to the Flics that are connected to the same device. You will not get access to the buttons that might run on a nearby hub (since that kind of doesn't make sense).

May I know which use case you have, since you say you want to use both the Hub and the Android API? I guess most developers use the HTTP Request feature of the Hub and set up a server somewhere if they want some custom feature.

Hi. Have you tried to set up http://postb.in and use such an URL instead? Then you can inspect what the hub sends. We have plans to improve the error handling of HTTP Request but aren't quite there yet.

Sorry but I don't follow. What is the restriction? Have you tried simply to assign all the actions you want to a single button? All actions will then be triggered in sequence.

"Tasks" in the phone app is primarily meant to be used as shortcuts in the notification bar as "virtual flics".

We found it to be the easiest solution. The hub is most likely in Bluetooth range when you want to configure it, it always works regardless if your phone is on Mobile Internet or on WiFi (and the same network as the hub). We also find Bluetooth to be fast enough for configuring the hub. Do you see any problems using Bluetooth?

We could of course add a IP layer and configure the hub through that in case the phone and the hub both are on the same network, but it takes resources and we haven't found any reason for doing so yet.

We think our method is far more superior than WiFi-based devices. They tend to be quite annoying if you want to reconfigure the WiFi SSID/password settings for example, if the device is on a network you can't reach/connect to from your phone.

It should be fixed now.

Hi. Thanks for the issue report. We'll fix that in the next version.

We have the following SDKs for computers:
https://github.com/50ButtonsEach/fliclib-linux-hci
https://github.com/50ButtonsEach/flic-service-osx
https://github.com/50ButtonsEach/fliclib-windows

For Macintosh we also have a user-friendly app: https://github.com/50ButtonsEach/hax-with-flic-osx.

For the Mac app the user must configure it, I'm not sure how easy it is.

For the SDK/daemon variant, the solution is that we have a daemon executable running that implements a TCP server. Then we have client libraries for a couple of languages you can use to connect to the server. Usually the server runs at localhost so you can only connect to it from the same computer. You would need to implement a client application that connects to the server, implements the pairing process in a user-friendly way and listens to Flic button events. When you receive an event, you can start a browser process with the web page URL as program argument.

The user need to download both the Flic daemon and your application (you can bundle it in one zip file for example, or even make an installer). Without the software, it will be impossible to connect the button to the computer (or technically yes through some system Bluetooth settings maybe but that won't be much use since there is no software that can interact with it).

@gwpcasey I think we will probably not add that. Why not simply use a power bank or similar if you want it portable?

Hi. Please after trying to add a button, go to the app's Settings -> Help & Feedback -> Send BT-log so we can take a look at it.