@tonsit We still have the plans to release it, it's just that we got quite busy right now with the new products.

Maybe you can use grabExclusivity() to block the Flic app from executing actions instead?

You can pair the button to multiple devices and assign the same config. But the button itself can only be connected to one device at a time. So if you have two paired devices nearby and the button has gone to sleep, when you then press the button, it will connect to the device that responds quickest.

@matt-0 Not sure if you already did this, but you need to assign the IFTTT action to the Flic in the Flic app so the app actually sends the events to the cloud.

@JoeJoe unfortunately not. We have HID on iOS but it didn't work out well on Android due to a huge amount of bugs in the Android Bluetooth stack. Also the onscreen keyboard is hidden when a HID device is connected which is quite bad for the user experience.

Passive mode is the way to go. It basically means setting the "auto disconnect timeout" to something other that infinity, for example 15 seconds. It means the button will disconnect 15 seconds after inactivity. When you later press it, it will connect again. This might result in slightly higher delay, so it's not good for games, but should be ok for light switches and similar.

It's obviously a bug in either the OS or the Bluetooth chip in the phone. Can you post a hci snoop log that records from the phone boots until it doesn't work?

It generally means the battery has a too low voltage for the Flic to operate. Did you try a new battery?

@JoeJoe the pdf app must in that case support intents for changing page. I doubt many apps do that.

Yes, yellow is also valid. See the documentation at https://github.com/50ButtonsEach/fliclib-linux-hci/blob/master/ProtocolDocumentation.md#evtgetbuttoninforesponse.