@sgemmen The hub firmware with Hub SDK support for Flic Duo is pushed out now (version 4.6.0). The documentation is not yet out but you can see an example event here that includes button number, orientation and gesture:

buttonUp {"bdaddr":"90:88:a9:5b:10:62","wasQueued":false,"buttonNumber":1,"orientation":{"x":-1.530368,"y":0.109312,"z":1.952},"gesture":"right","age":0}

@gabriel_g Hi, when you have a Hold & Twist function active, a Swipe action must be performed within 0.5 seconds.

@Emil Thanks!

@chachee35 thanks, we will investigate

Any news...?

@fmg80s said in Flic Twist and Nanoleaf:

Unfortunately, it doesn’t dim the Shapes lights.

Take a look at this topic.

Brightness not working for Twist and Nanoleaf Skylight

@Emil Sorry. Didn't write that it's when I'm in my car on my way home.😉

@edziu-konczewski The reason is indeed due to technical limitations.
Android does not expose any way for third party apps to answer an incoming phone call, at least not using publicly defined APIs. It might be the case that Tasker uses some internal hidden private API in Android, but such use is discouraged by Google and might stop working at any time. In every Android release, Google blocks more and more internal APIs.

That said, if you are happy with Tasker, you can simply use the Flic integration inside Tasker to trigger whatever you want in Tasker by the click of a Flic button.

The Flic Twist was delivered today and I tested it right away.
The MusicCast volume control works perfectly with it.
@rob.loosx Thank you very much for the script 😉

2.jpg

@buckyswider You can remove a non-responding Matter device, but in that case the Flic hub pairing will not be removed from the Matter device in question.

@wes I would look into the Matter libraries for Arduino. However the Flic hub Mini IS in fact a ESP32 S3. Access to the bootloader/flash etc. is literally cut off. Who would have known 😆

I have the new app installed and have successfully setup flic twists to control the volumes in 3 different Biamp Cambridge Zones. Thank you for the feature!

@wpjvanderven this is fixed in version 4.0.13 which should now be available on Google Play. If not, please wait for Google to roll out the new version.

@alexgooz92fs Nice to hear that!

It seems the issue doesn't affect all users. I my self can for example use the Alexa actions I set up previously, before their outage, successfully today without the need to re-enable the skill or re-setup anything.

Note that the http request containing the button press event that is sent to Alexa's server when a Flic button is pressed, sent from us, looks the same both before and after their outage, so if it suddenly doesn't work after their outage, it seems at least to me something has been broken on their end for you it doesn't work for. However, if you added an additional Alexa action during the time they had an outage, that action might not have been synced correctly so in that case you might need to remove the Alexa action and add it back in the Flic app.

@tomtec Flic uses Bluetooth Low Energy. BLE uses frequency hopping and may thus jump between different channels in the whole allocated spectrum.

thank you. it works good for me 🙂

@garryjoss @andy-henderson Depending on when you purchased your Flics we did have an adhesive a while which became quite soft over time which made it a bit more difficult to open the battery hatch.

All Flic adhesives have always been washable, so you can carefully clean them with water to freshen up the adhesion. You can rub them with water and maybe even some dishsoap and let it air dry. Don't hold it under water as water may enter and damage the electronics.

Other alternatives are as Andy mentioned, you could use a scissor if you're careful.

We have since changed the adhesive, the latest version is much better than the previous. The adhesives are available separately on our shop.

Feel free to contact our support and we're happy to help you further if none of the above works!