FlicTeam

@rick-0 Is this on Android on iOS? Can you send a screenshot? Are you connected to a Flic Hub or not?

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

@perege If you have a Flic hub, you can use our Smartthings integration. If you set up a scene in Smartthings that does what you want, you can trigger that from flic.

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

@andreas-lorentsen The reason we don't have any cloud-based integrations for the Twist is that we think the latency could be too high and thus not a good customer experience. That said, how do you perceive the latency for updating the volume by rotating the Twist in this case?

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

@jayst84 That's a different issue; however we found the cause for this and a fix has now been submitted to Google Play for review. ETA new app out tomorrow.

@buckyswider Unfortunately a new Matter device counts as a new device, regardless if you happen to give it the same name, and we have unfortunately no way currently to streamline the process of instantly replacing all references to an old device to a new one. You must thus assign it to the actions in which you want to use it.

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