@stefaan Without doubt that would be very useful. This is so normal in the Linux world that I am astonished they do not keep a log.

It occurred to me that I had hit the limit on the number of Bluetooth connections on my phone and that this was four.

I tested this by using the Nordic app nRF Connect. It detected all six buttons simultaneously, showing the advertising interval and showing that they were all bonded. From this I conclude that my phone can support at least six Bluetooth connections.

I then activated three iBeacons and these also were detected at the same time, bringing the number of simultaneous connections to nine.

@joacim thanks for your reply. What you say makes sense since the smartphone manufacturer normally will not expect many concurrent Bluetooth connections to the phone. The RPi can support 10 concurrent connections so I will be using that.

It occurred to me that I had hit the limit on the number of Bluetooth connections on my phone and that this was four.

I tested this by using the Nordic app nRF Connect. It detected all six buttons simultaneously, showing the advertising interval and showing that they were all bonded. From this I conclude that my phone can support at least six Bluetooth connections.

I then activated three iBeacons and these also were detected at the same time, bringing the number of simultaneous connections to nine.

I have six Flic Location Singles.

I can initially connect all six Flics to the Flic app but I can only ever use four at one time.
If I reset the Bluetooth subsystem all six Flics will show as disconnected, which is to be expected. When I press the button on a Flic it will connect, once again as expected. But once I have pressed the fourth button the remaining two Flics will not connect and their red light flashes twice.

This behaviour is independent of which Flics are used. It is always the first four Flics which are connected and the remaining two Flics cannot be connected.

It seems the Flic app has a limit of four Flics which can be enrolled at the same time. This is a severe limitation for me, considering the intended use. I intend to use them as panic buttons, positioned in various rooms and will need eight in total(for the time being). The Flic will send messages, via smartphones, through the Artik cloud to alarm devices, alarm monitors and security personnel. The smartphone will be running the Flic app and a custom app using the Flic SDK.

I can get around this problem by using more than one smartphone in the facility but this increases the complexity of administration.

It is really important, to me, to be able to enrol more than four Flic buttons.

I hope that there is something quite simple that I can do to fix this problem otherwise I urge you to remove this quite arbitrary limit as soon as possible.

Next I will try out using a Raspberry Pi as a hub for my buttons.

@proto732 A fourth measure that really works for me is to restart the Bluetooth subsystem.
I use this app:
https://play.google.com/store/apps/details?id=com.justinmockler.bluetoothreboot
and it invariably fixes the problem for me.

I want to make the provision of apps that use Flic buttons as simple as possible. It should work like this:

1. download only one app, written to use an expanded SDK communicating with the Flic service and containing the Flic service daemon.
2. on initial startup the app asks the user to press his button(s).
3. he presses his button(s) and the button image vibrates.
4. he taps the button image, confirming the selection and he is good to go.
5. the app completes the start up, remembering the initial selection.

In this way the user need never download two apps or unnecessarily interact with the rather confusing Flic app. That is just unneeded extra work. All I want him to do is download my app, register his button with a press and he is ready to use my app. Quick, clean and simple. which is very much in the spirit of the Flic buttons.

For this to happen the present Flic app should be stripped of its user interface and made available for bundling with developer apps. The SDK be expanded to supply the important functions provided by the Flic app.

I want to emphasise again that the whole spirit of the Flic buttons is to provide an interface that is quick, clean and simple. The developer's apps should reflect this spirit by taking away all the pain and confusion of setting up buttons. Put this under the control of the app developer who understands his target market. For example, a Flic panic button for the elderly must be capable of setup with a single button press and a single click. There must be no fuss, no bother, no uncertainty and no confusion.

Yes, I very much wish the sounds could be changed individually for each button.

Congratulations on having the sincerity and transparency to make this honest though painful admission.

@stefaan Without doubt that would be very useful. This is so normal in the Linux world that I am astonished they do not keep a log.

The double red blink means that the button thinks your phone is out of range. This means that your phone is not replying to the advertising packets broadcast at 1800 msec intervals by the button.

1. A likely cause is that a task killer app on Android shut down background tasks, disabling the Flic service. Once disabled it cannot reply to the button's advertising packets and so the button thinks it is all alone in the world! This is often done to conserve memory and save on battery life. The fix is to place flic in the app's whitelist so that it is not shut down.

2. Another, related, possible cause is that your version of Android is not allowing flic to run as a background task. The fix is to change the settings so that flic is allowed to run as a background task.

3. A third, possible cause is that you are using an ad blocker like Adguard. This prevents the flic service from reporting back to HQ(naughty boys!). The fix is to put flic.io in the ad blocker's white list.

I found it necessary to use all three fixes.

@Emil It is still not in the online javadoc