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

@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
Since version 2.1 of Matterbridge the dimmers should show up as 0x0101. Unfortunately I don't have the twist but for example my tuya dimmer is now shown correctly.

It has been stable after locking it to a single access point in my router network settings

@rccotnoir Not currently. We thought that would be confusing because these keys are very differently mapped depending on the keyboard layout and we don't know what keyboard layout the user has on the target device the flic is going to be used.

This is something we could consider though in the future but it would require the user to specify keyboard layout first.

@siobhanellis That is correct. You can see at https://flic.io/applications/ that "analog rotation" support for Nanoleaf is not available for Twist.

But the Push function for the Twist can be used to control Nanoleaf lights.

However, using the Advanced dimming option, you can setup the Push & Twist to a certain trigger point and have the push action to trigger a brightness level set for the Nanoleaf light.

Note that Nanoleaf devices that support Matter can be used with the rotation feature in our app though using the Matter functionality.

@siobhanellis correct. Only the Hub LR of our hubs support Homekit, but all our hubs support Matter (as a controller).

The button name is stored on the button itself, so that you can see the same name when you connect the button to another device or app.

As mentioned here: https://github.com/50ButtonsEach/flic2-documentation/wiki/Flic-2-Protocol-Specification#get-and-set-name, the name is maximum 23 bytes.

This has been the case for a few years. Before the name was only stored locally in the phone (or hub) and then this restriction was not in place.

I suggest you to use a shorter name, e.g. prefix it with "s:/" and then add the IP address of your soundbar.

@alayton On/Off, hue, saturation, brightness.

@jamoiholland @Emil I second this; very interested in tying flic to Google home.

@jdfetterly do you use the iOS app or Android app? Are you connected to a Flic hub? Exactly what do you mean when you say "Flic app just seems to want to use my old credentials and won’t let me update them."?