FlicTeam

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

@andy-henderson We have seen a lot of error responses in our requests to Alexa's servers today and yesterday like "service unavailable" and "INTERNAL_SERVICE_EXCEPTION". I suggest you wait until tomorrow and see if they have fixed the issue. If it doesn't work by tomorrow, in case some kind of state or similar has got broken on their end, I suggest you to first remove the Alexa action from all your buttons in the Flic app, then delete the Flic skill in the Alexa app. Then re-enable the skill and add back the Alexa actions in the Flic app to your triggers. What I just mentioned should be done in that exact order.

Hi and thanks for your report. We must have missed this when we upgraded the UI of our app. A new app version with a fix for this is now sent in to review to Google Play (4.0.11). Hopefully it is released within 24 hours.

@mx5_94 Hi, if you mean the "predefined set of products that can quickly be selected by name" that you can find under Settings -> Groups, then I can't find any such thing in their API. The thing called "groups" in the API is the live grouping of devices, which is a totally different thing.

Would you like to be able to change the current grouping of devices so that you can e.g. start a playlist/favourite on a particular set of speakers (by using checkboxes in our app), i.e. immediately make them a group if they are not already constituting a group?