Flichub and Android API



  • How about, good afternoon from Mexico.

    I am currently working on an Android application with integration with its API, I found the problem that I can not have more than 7 buttons connected simultaneously. For my project I require about 15 buttons connected at the same time, I just ordered the hub, waiting for me to arrive, my question is: the integration of my application along with the Android api will work the same or the game with the hub is already different?

    I hope to be clear with my question and apologies for my not so good English.
    Greetings from Mexico.


  • FlicTeam

    @restauraid-mx The hub supports up to 63 buttons to be connected at the same time. But as I wrote earlier, the buttons are then connected to the hub and not to the Android device. So that's why I wondered what you want should happen with the button events when the buttons are pressed.



  • What I want to do is to detect the clicks of about 20 buttons connected to my Android application, but currently I can only do it with 7 at the same time, so my question of whether with the hub it is possible to achieve this



  • This post is deleted!

  • FlicTeam

    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.


Log in to reply
 

Looks like your connection to Community was lost, please wait while we try to reconnect.