@bogaertsherman What phone model do you have? What actions do you have set up? Have you restricted background usage/battery optimisations or something?

Was out, but seemed to have been fixed some time yesterday afternoon or evening.

@Emil any ideas in such a case ( mentioned above) ?

@josef-held Hi, you can configure the Flic button as a Bluetooth keyboard with the help of the Flic app, then connect the button directly to the Go Button app.

See https://flic.io/applications/flic-universal.

@pascal-0

It's been... what, a year now since they came out (and the multiple years it was in development)? It's pretty obvious they have no intention of delivering on their promises.

Hi, @Emil
I have the same issue and it is annoying not to be able to differentiate between enabled and disabled flows or to filter them. But it may not be possible to get that information from Homey.

In addition to that I have found out that only the first 17 or so flows are listed (based on creation date) so I can not assign any of my recent flow to my flic button because I can't see them in the list 😞

@philippe-lux-67 Hi!
Sorry for not getting back, we did have a look at the logs but unfortunately there was nothing we could see that would spark an idea for a potential workaround. We do not have the ability to test or update old versions of our app, so I'm afraid there is not much we can do about this.

You can with smallish effort accomplish this using Home Assistant, I don't think Flic app nor IFTTT can do this as they would have to know what your Sonos is doing when you execute the action. If it doesn't matter what was happening before the button press, then IFTTT and for example Alexa can be used for this.

@Emil
People who have gone Home Assistant path want to use it for their home control, not Flic app. Other apps, such as Flic app, is something they want to get rid. Home Assistant is growing fast and there is a good reason for it - controlling your smart home has become way too spread out and complicated without something like HA.

People who have Alexa already have Matter controller there, they just want to see the buttons. People who have Google ecosystem already have a matter controller. They too just want to see the buttons. Same with Homekit. Needing anoother controller and app doesn't really work as reasoning as everyone having any kind of smart home setup already have them.

I can understand the Matter controller path regarding the Twist - it's a pain that Matter doesn't support these kind of products properly yet. But being your own controller is, in the end, a patch for promises made before. I don't think Alexa, Google, Homekit nor Home Assistant users are looking forward to having another ecosystem around to complicate what they want to simplify. And I think lack of enthusiasm for flic's Matter release tells the same story.

Could be wrong, maybe sales are up like crazy. But it doesn't look like that from stupid users point of view.

@Emil The permissions I enabled were "Show on Lock screen" and "Display pop-up windows while running in the background". These are shown on a picture here https://stackoverflow.com/questions/71449643/how-can-i-get-the-display-pop-up-windows-while-running-in-the-background-and

You were correct, there's an additional permission to start on boot. It worked similar how described here https://nine-faq.9folders.com/articles/8772-how-to-manage-autostart-service-on-the-xiaomi-devices

It seems a phone reboot helped.
Also, https://flic.io/support turns to have self-service troubleshooting which isn't bad.

@savedana have you solved this anyhow?

@daniel-silcock did you find any solution?

@scullracer Hi!

Sorry to hear about the hardware issues. Unfortunately it is not possible to create such action for Flic in iOS due to limitations in the API to trigger arbitrary Shortcuts.

@Emil Thanks for info, I've change my phone, could not, on other Android it works OK with permission for Phone and Location.

@dainova I would use a Google Pixel with "stock" Android instead of those asian brands which often like to introduce "power saving features" which kills apps every now and then, even though they are declared to stay alive by using a Foreground Service.

In any case, which action are you using and in what do you mean exactly with "more reliable"? Is something not working as expected, in that case, what exactly? Does the button stay connected to the phone (LED should flash green when you press it) or is it something wrong with the action you try to execute?

@Emil i received an update from Amazon Japan Alexa team. They said that Flic has found the problem and will fix this in the next release. Can you help share when the release will be so we can continue testing?