FlicTeam

@pico Currently we use this condition to determine "on wall":

x >= -0.19 && x <= 0.19 && y >= 0.93 && y <= 1.25 && z >= -0.19 && z <= 0.19

If you want to get the RSSI value on a connected button, we must send a HCI command to the Bluetooth controller and ask to get the latest value. Do you have a suggestion for how such an API should look like from the client side?

@soulbarn2 Only the Flic Hub LR can be added to Homekit as a bridge accessory, exposing its added Flics. In this case you should, in Homekit, press each Govee device and share it (by obtaining a Matter passkey), then enter this passkey into the Flic app while connected to the Flic Hub in the Matter provider. That will pair the Flic Hub with the Govee light, so you can control it from the Flic Hub. Repeat this process for each light. There is unfortunately no way to share groupings of devices across different Matter fabrics.

Another way would be to use e.g. the flic lib without using the hub to listen to events from button presses, and then generate and send the OSC messages yourself.

@chriscam85

1. You can pair all our controllers (Flic Button, Flic Twist, Flic Duo) to multiple receivers (Flic Hubs, phones, tablets etc.). Flic Twist can however only be connected to Flic Hubs currently. The controllers can however only have one simultaneous connection active. If there is no active connection when the button is pressed, it starts advertising and the first receiver to respond will initiate the connection. Which actions will be performed thus depend on what actions have been set up on that receiver, to be triggered when the controller in question is pressed. So if you have a Flic Button paired to both a phone and a hub, where you have for the phone assigned an action when the button is double clicked (only), but on the hub you have set up an action to be performed when the button is held (only), then no action will be performed upon holding the button down, if the button currently has an active connection to the phone.
2. There is now not really a way to switch the device the button is connected to. There is also currently no way in the Flic app to make use of the "push-twist" feature. You can however use the Volume Control action to increase or decrease the volume in discrete steps.
3. We have struggled to find time to implement the Change Config action with the new UI we have made. May I know in what way you find it useful or how you would like to use it? For every action, you can use the timer icon in the upper corner to select a delay between pressing the button and performing the action. The explicit "delay" action, on the other hand, is to be used in Flic Universal mode, and can be inserted between e.g. keyboard key presses to add a delay between these two presses. And yes, the purpose of Flic Universal is to configure the button as a generic keyboard/mouse/midi bluetooth device and then connect it to any other device supporting one of these protocols over bluetooth.
4. With the twist feature for Flic Twist and Flic Duo, you configure which lights/speakers should be controlled. To integrate with Hub SDK, we have also added "virtual devices" which is a virtual device implemented in the Hub SDK with javascript, that can be added among physical lights/speakers to a Rotate action. Your virtual device implemented in the Hub SDK can for example send commands over a proprietary protocol to a real light when you get the virtualDeviceUpdate event. If your goal is to be able to get twist updates for every Flic Duo you have, then you should create a virtual device per Flic Duo and assign each to a Rotate action for the corresponding Flic Duo.

@mullz Right, I could reproduce this. I'll report internally and make sure it gets fixed in the next app version!

@mullz Now I get it. There is another bug in both the code from @oskaremilsson as well as the code from @jitmo. By using the .on method on the IR object, you add a new listener (i.e. append it to the list of listeners). You never remove the listeners, however. That's why all the registered listeners get called on every recordComplete event. You can for example use the .once method instead. Just remember to also manually remove the listener when you cancel the recording process using for example the .removeAllListeners method.

@mullz I couldn't reproduce the issue. Seems to work as intended for me with oskaremilsson's code.
One thing I noticed is that the conversion to string might not always work correctly the way the encoding is done. The string that is to be saved needs to be stored in proper UTF-16 format; now you could theoretically accidentally create invalid surrogate pairs.

@sam What do you mean with "I can't remove it"? If you press the item there should be a menu appearing where you can select "Delete".

@nathan-scofield If you press the item there should be the option to Delete it?