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

@Emil Bummer. Maybe one for the sprint list?? 🙂 Thanks for the quick reply.

I still have a conundrum in my hub I'm trying to resolve. It's telling me I can't remove the dead device since it's not online. Catch-22!

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

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