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

@vesa
With the new Matter update, I'm in fact using a flic button as a doorbell button, together with Home assistant. It's working great with the Matterbridge addon, and a Boolean helper that's visible in the Flic app.

@bambi2000 hello , I have the same problem . All button works very well about 4 years and now it doesn’t works . Do you find a solution ?

@joacim-n-linder
Matter bridge on home assistant would bridge home assistant controllable devices as matter devices to Flic. But that is oppposite of what would be useful. I have hard time seeing Flic being used as the "center of the home automation" when you have Home Assistant. So Flic hub would need to be the matter bridge, not the controller.

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

We have a business solution that might have the functionality you are looking for: https://flic.io/business/device-manager.

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

@jakekapsandy here is an example:

var ir = require('ir'); var arr = [48256, 7029, 3405, 418, 445, 418, 445, 418, 445, 421, 445, 421, 448, 418, 445, 421, 445, 416, 445, 421, 445, 418, 445, 418, 445, 418, 445, 424, 1293, 418, 1296, 416, 448, 418, 445, 426, 445, 424, 1296, 421, 445, 416, 445, 421, 445, 424, 445, 418, 445, 421, 445, 418, 1293, 424, 445, 421, 1293, 416, 1293, 418, 1293, 424, 1293, 421, 1293, 418, 1293, 421, 34946, 7053, 1709, 421]; ir.play(new Uint32Array(arr), function(error) { console.log(error); });

We have just released Matter support, which Wiz also supports. I suggest you to use Matter instead since that is local and hence has much lower latency. See https://faq.wizconnected.com/hc/en/3-wiz-legacy/faq/603-how-to-install-my-matter-ready-device-to-matter-hub/ how to generate a setup code which you can then use in the Flic app. Note that this is only supported when the button is connected to the Flic Hub (not directly to phone/tablet).

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

See https://community.flic.io/topic/18460/button-name-23-characters

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.

@Y2K

41842fed-e3fc-4ef3-853e-7be9b5e9650e-image.png

729f7266-3441-4d10-a672-d5b0e3c8577f-image.png

34165d4f-cc2e-4a43-9f0c-a00312388077-image.png