@tcbeatie Cool! Good that you solved it. Regarding the triggers, as you see we do provide the "raw" buttonUp and buttonDown events. This means that you should be able to create a script in which you can define your own click types. Also, have a look at flic-service-osx if you ever feel like making something even more complex ;)
I saw references to that, but not sure how to implement. Easiest might be a triple click?
My current use case is a button in the kitchen that controls the mac next door; volume up/down/pause|play is easy.. A triple click to do something cool like speak the weather would be awesome :)
@bambi2000 Thanks. I did manage to get the basics working (as well as find the streams for P3 and P4 :-) ). I also managed to group players by setting CurrentURI of the "slave" IP to the UUID of the "master".
I am also unable to setup my flics to control my wemo bulbs, the app does not find the wemo devices when I search for them. The bulbs are on the same LAN and other third party apps (for example, wemoleds) can find them.
No - no luck, its very annoying, its the reason I bought the flics - works great with Hue bulbs but not with wemo bulbs.
I was thinking about how the newer Flic buttons allow for firmware updates. Since I'm assuming these would normally be done through the Android or iOS app, how would we handle these if we've got our buttons paired with a bunch of Raspberry Pis?
Is it possible to set an alarm? I'm looking to set a 6am alarm with one click, a 8am with 2 clicks, and another with a hold. But as far as I can tell the android app does not support a "set" alarm function. The wake up command only lets you dismiss or snooze pre-set alarms.
@Emil unfortunatelly not much better. I tried now with Nexus 5x, and to tell you the truth, things are getting even worse:
Yesterday I set up my old phone: Nexus 5 and my Flic account and my 4 Flics. I set the turquoise to call the gate's number on click and call my wife on double-click.
Today I connected the the turquoise Flic to my wife's Meizu phone (it worked after a few restarts of the app and clear data). Note: She uses a different Flic account! I set up that Click calls a phone number (with Hebrew characters in the contact's name in her phone's contact list), Double Click calls ME!
Just now I logged in to MY Flic account (the one I used previously in my old Nexus 5) from my new phone (Nexus 5X). I do see my 4 Flics, and there's an icon on each of them teling me that they're locked (makes sense, 3 of them are locked to my old phone, and the turquoise is locked to both to my old phone and my wife's phone) I pressed the flic for 7 seconds and clicked DOWNLOAD (doesn't make sense, the Try again I had in the other phone was more logical to me) BUT when I enter the configuration of the turquoise Flic I was shocked! I saw that Double Click's action is to call ME! This is an enormous BUG, as in all places it was stated that the actions are saved in the phone/account and not "in the flic". How come that when I logged in with my flic account I get the settings of my wife's flic account/phone???? I also saw that the Click action has ???????????? in the name instead of the Hebrew characters....
Look, I am a programmer myself, and I like to help, but I don't feel I am getting much for my money here. The reaction time is way to slow, and doesn't address the problems. The bugs I just posted now... they are so huge, I can't possibly imagine how can it be that you never tried the 1 flic 2 phones, 1 flic 2 accounts scenarios!!!! Or if you never tried them then at least don't write in the forum that it works!
I am seriously considering returning my 4 flics, I paid $110 for them and the time I am investing in debugging and waiting for days to get a response doesn't worth the money. For $25 I can get a Raspberry PI that works and knows a bit more than a flic....
@joacim I have made one more happy discovery. In January, when I bought my six Flic singles I found that every time the button was moved out of range of the phone the bonding was broken. To re-establish a connection it was necessary to do a seven second button press. This was also a killer disadvantage for my intended use.
Now I find that no longer happens. When the button comes back withing range of the phone it automatically re-establishes its connection and a seven second button press is no longer necessary.
This has removed the last major barrier for my intended usage of the buttons and it makes me very happy indeed.
Congratulations to Flic for listening to their customers, being responsive, attending to issues and progressively refining the product. This puts you head and shoulders above the rest.
Since I'd been having a lot of trouble getting this working, and I assume others will as well, the issue with the 10 second press to reset is the device it's currently paired to cannot be connected to it.
In my case, I have Flic buttons paired with Raspberry Pi devices. To unpair it, I had to turn off the service that was listening for Flic button presses. Once I did that, the button lit up red when clicked. This is the indication I needed so I could reset it. At that point, I was able to pair it to another device the same way as a fresh button.
Thanks for the update and I have now further investigated the changes and the 300 ms input lag is gone in active mode as suspected. Very appreciated! The reaction times are now more or less correct when compared to other applications. Maybe still a little slower in measuring reaction times using these buttons together with the Unity Engine. It's however hard to say where the bottleneck is, if it is in the button detecting and sending the presses to the Android OS, or in Unity Engine detecting the press events etc.
Thank you for the feedback provided in this tread.