Yes both flic 1 and flic 2 work on both the new hub and the old hub. The hub software treats both button types exactly the same since the button communication is abstracted away at a lower level. If you see that some actions don't always work it has nothing to do with button version, but rather that the http communication with the target device fails or something.
@schenkl Where did you read about the -v option? There is no such thing. See the official readme at https://github.com/50ButtonsEach/fliclib-linux-hci/blob/master/README.md#usage-of-flicd. You could also give an absolute path for the db file to avoid it ending up at a wrong place.
@schenkl I still don't follow. Flicd never initiates connections if you don't ask it to. You need to create a connection channel for a specific button in order to connect to it. Do you do this?
Do you erase the database file on every reboot?
How have you written your code? Do you extract the paired buttons when you connect to the flicd?
Some more info would be good.
Do you mean on the IR accessory or the hub itself? Do you have the old Hub or the new Hub LR?
I'm not exactly sure how I could help you, would you like a photo of how it should look like?
Could you post a photo of your broken jack?
Hi. In the Android app, when you configure an action there is a clock symbol at the top where you can set a delay. This feature is currently not available when using the iOS app.
@b-bech-l I honestly have no idea at all how long their certification process takes. I don't know if it takes one month or half a year. But hopefully near the former.
We have a working implementation that we are currently working with Apple to get it certified. I don't know how long this process will take, but the process is quite thorough.
So you don't have any actual problems with the Flics themselves nor the Flic connections, is that correct?
Is the issue that your Philips Hues / the Philips Hue integration don't work?
Does your Hue Bridge show up correctly?