Posts made by Emil

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

@HSDK Do you mean that the Sonos integration works as follows:

• Android: Yes
• iOS: No
• Flic Hub: No

?

@rickard the hub sdk will now emit duo events. There is no documentation written yet but if you print the events json serialised you will see how it works.

@gamhacked00 said in Spotify Web Connect on iOS is really unreliable:

Reopening the app fixes the problem

Do you mean the flic app or the Spotify app?

We have noticed this as well, but it is simply how the Spotify API works.

See https://github.com/50ButtonsEach/flic2-documentation/issues/5#issuecomment-3693331760

@sgemmen The hub firmware with Hub SDK support for Flic Duo is pushed out now (version 4.6.0). The documentation is not yet out but you can see an example event here that includes button number, orientation and gesture:

buttonUp {"bdaddr":"90:88:a9:5b:10:62","wasQueued":false,"buttonNumber":1,"orientation":{"x":-1.530368,"y":0.109312,"z":1.952},"gesture":"right","age":0}

@sgemmen

1. We have just finished implementing the Flic Duo support for the Flic Hub SDK. This week we will push both a new firmware as well as update the documentation.
2. There should be a metal plate (magnetic) attached to every Duo, together with a sticker so you can attach it to a wall. Didn't you get this?
3. Haven't tested Copilot. Our ChatGPT integration is extremely simple actually. We have more or less just taken the Hub SDK API documentation and fed that as a context into their template. I guess you should be able to do something similar with Copilot.

@HSDK Do you possibly have an Android phone or tablet device? I would like to know if it can be controlled by the Flic app on that platform if possible (without involving any Flic Hub).

May I ask what kind of sonos device it is, and if it is a rather new or an old one? (model type)

If only the IP address gets listed with the generic name "Sonos", it means that it found the device during a network scan, but communication with it later failed.

I guess you have tried to log out from your Sonos account and log back in again (in case your access token for some reason has become invalid)? Also tried to reboot your flic hub?

Could you please give me the text output that you can see in a browser if you go to http://sonos-ip-address:1400/info ?

I don't understand. You say: "When I setup Sonos provider on the hub, all my speakers are just listed as “Sonos” with different ip’s." but also "( or the hub), there I see the correct speaker names". So do you see the correct name when connected to a Flic hub or not?

@gabriel_g Hi, when you have a Hold & Twist function active, a Swipe action must be performed within 0.5 seconds.