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

@editdave yeah we are discussing internally a new mode for the twist that would make this possible. It needs to be a "free" movement so not tied to 0-100% as each mode is currently.

@Y2K I believe I can now, I have a SonOff iHost Hub, it connects with HomeKit, I also have a Flic2 LR Hub. the hub bridges to Homekit, and so does the SonOff so my SonOff devices can be triggered via a pass thru in scene controls and basic basic basic automation.

@pontus The button's firmware won't boot if it detects that the voltage is below 2.2 Volt, resulting in that the LED stays on since that is the default hardware state. If you are sure the battery is good, please try inserting it again.