Hi!

A quick update on this, we discovered a minor difference in how the LIFX buld acts depending on model, which created this issue.

We have now fixed this so we will soon release a new firmware update which makes this work!

@kortenkamp said in Flic Midi - How to set it up?:

". Are you still workin

Hi!

I can only say that it is coming "very soon".

@anolma Hi! This has now been released for the iOS app. Now you can select "Real-time" when adding Keyboard Command to Push trigger to make the key correspond to the actual button down and up event!

@kurtangus Hi! This has now been released for the iOS app. Now you can select "Real-time" when adding Keyboard Command to Push trigger to make the key correspond to the actual button down and up event!

@KP Hi! Sorry about this, it seems we had a memory leak which we have now fixed. If you want to try out the fix, please PM me your Hub serial number and I can assign you the new beta firmware. Sorry for the inconvenience!

@kurtangus Hi!

This will be released in the next update of the Flic app for iOS, scheduled for next week. I will let you know when it's out!

@kurtangus Hi!

So sorry to say but it seems this has somehow fallen between two chairs. I definitely see the use case for this and I will try to get this feature added as soon as possible.

Thank you for bringing this to our attention!

@robarammisc said in Using HUB with OSC,MIDI,KEY Commands:

MIDI

Hi! Just wanted to let you know that OSC is now released for the Flic Hub SDK:

https://community.flic.io/topic/18239/open-sound-control-osc-script-for-flic-hub-sdk?_=1675685771460

Hi!

We have released a script to make it possible to send OSC messages from the Flic Hub SDK.

The script can be found here: https://github.com/50ButtonsEach/flic-hub-sdk-osc-js

OSC is a communication protocol made for live performances and is often used to communicate with the popular application https://qlab.app .

With this script you can easily trigger workflows in QLab (or other OSC enabled applications) with a push of a button.

Hope you find this useful!

@pbw Hi!

Sorry for the late reply! We have not seen any issues related to connectivity with iOS 16.2 so I'm not sure why this happens.

However, there is a workaround that can fix these instabilities and that is to "Enable Location Services" in the Settings. What this does is it is registering the Flic app to be woken up on what iOS calls a "Significant location change". This is a good way to kick the service back into a working state.

It should not really be needed but it has proven to solve these kinds of rare issues before.

One side note is that this will deliver your approximate location to our app and iOS will show you a warning about this but I can assure you that we do not upload this location anywhere, it is purely as a workaround for getting back into a running state.

Hope this helps!

@simonbrohus794
Hi!

Yes, there is!

You can use Flic Universal to configure the Flic button to act as a Bluetooth keyboard and program different key combinations to be triggered when you press it.

You can read more here:
https://flic.io/flic-universal

@MagAa Hi!

I think there should be a way to solve the issue you are having, but yes it would require some programming, but if I know more about the specific scenario maybe I can help!

The main question is what you would like to use instead of a computer to connect the button to, are you thinking a phone or a Flic Hub?

In the case of the Flic Hub, it will probably be possible to write a script using our Flic Hub SDK (https://flic.io/flic-hub-sdk) that will send a specific OSC command to a host.

If you want to use a phone, you will have to use the approach suggested by emil and run an HTTP server on a computer somewhere that translates the messages to OSC. This will probably be a bit more complicated.