Ok, I assume that channel.auto_disconnect_time unit is seconds.

But I think that I eventually found out what was draining the batteries, in the python scan wizard exemple in the is_private case, the scanner is never removed. I suspect this forces all the buttons to stay active if no-one press on the foreign button for 7 sec. Since I fixed that with a timeout, batteries are felling much better :-)

@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.

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

If you cannot record the audio on your device, please check the microphone and the sound settings firstly. Then, try another audio recorder app. When you tend to record the audio on your computer, you should find the app, like FonePaw Screen Recorder, supporting microphone and system sound.

Hi, the Android app is missing. Not sure if still, or again. Do you know the reason and workaround?

I cannot seem to get a valid batterystatus from my old flic buttons.

Please see issue the issue I reported on github: https://github.com/50ButtonsEach/fliclib-linux-hci/issues/84

Does the batterystatus require an firmware update of the buttons?

I know this is a little old, but here is one way to approach this.

Create a webhook endpoint on the server, then use a websocket to push messages to the frontend.

Register the buttons with the database, giving them a UUID.

Split the API route based on button actions, passing the button's UUID as the parameter.

Assign the URL as an action to the botton, i.e. ".../button/action/uuid

Hope that helps

@emil
Thank you for your help!
I got a syntax error but I managed to repair it with this code:

def got_button(bd_addr): cc = fliclib.ButtonConnectionChannel(bd_addr) cc.on_button_single_or_double_click = \ lambda channel, click_type, was_queued, time_diff: \ keyboard.press(Key.right) if click_type == fliclib.ClickType.ButtonSingleClick else keyboard.press(Key.left) cc.on_connection_status_changed = \ lambda channel, connection_status, disconnect_reason: \ print(channel.bd_addr + " " + str(connection_status) + (" " + str(disconnect_reason) if connection_status == fliclib.ConnectionStatus.Disconnected else "")) client.add_connection_channel(cc)

It works perfectly and it seems I don't need to release the key.

But it seems Windows Universal Apps don't recognize key presses sent by Python... Key presses are recognized everywhere else. Anybody knows why or how to get around it?

The next step to have a fully functional Windows integration would be to make the script work with Eventghost. I will try either by capturing the keystroke event and by sending http requests to it's built-in webserver. I will let you know!

Hi,
I am facing the same issue with Samsung S8 and i am using the latest app from Android Play store. The button which is brand new is not getting discovered. Pls help,

Regards
JK

Hello.

Thank you for the fast feedback. We will have to show our users a message of this feature since they might be looking in our settings and/or inform our support team to handle the issues.

Well this is what im searching for too... I would love the flip to emulate/simulate a touchscreen press in the middel of my iOS screen.

@shawn-james-c Hello, this is possible using flic > ifttt > pushbullet. I tested it with Google Chrome and the pushbullet addon in the browser. When a URL is pushed, you set google chrome to open the url as default action.

I just found this.
I will try it out.
https://www.home-assistant.io/components/binary_sensor.flic/