TEMPO

I have the Tempo and tempo app which you can use the air turn pedal to control.

I cannot seem to assign a flic button to control the metronome in the app like you can do in OnSong.

Has anyone resolved this issue?

Is it possible, or suggested, to use more than one Flic hub, maybe for greater coverage area?

For example, I'm wondering if I could use a Flic Hub LR AND a Flic Hub Mini.

How exactly does Flic Universal's "Alternative keymap" work? Has anything about it changed with newer versions of iOS 18?

We program our Flic button for Flic Universal, configured to send the Enter key when clicked. We enable the "Alternative keymap" feature so iOS still shows the on-screen keyboard. It's used with a web application to trigger web page buttons. At some point between iOS 16 and iOS 18.3.2, this stopped working: the web page no longer responds to the Flic button. If we pair a regular Bluetooth keyboard along with the Flic button, then the Flic button works as expected. If we disable Flic's "Alternative keymap" feature, then the Flic button works as expected (but we lose the on-screen keyboard). This leads me to believe that something recently changed in iOS regarding how it handles Flic's "Alternative keymap" feature.

We are today announcing a Beta release of some new features in the Hub SDK that can be used together with Flic Twist.

In order to seamlessly continue to work with the rest of your smart home devices that you might have assigned to other triggers on the Flic Twist, we introduce the concept of Virtual Devices. A Virtual Device is handled by the Flic Hub firmware just like any other supported real device, but its functionality is implemented by the user in the Hub SDK, typically by writing some kind of bridge software that sends commands and receives update events over the LAN to/from the real device. If for example the brightness of a (real) light is changed by some external means, it is possible to tell the Flic Hub firmware from javascript about the new brightness level, which the hub then forwards to the Flic Twist, so that the LED status can update accordingly. That way when you twist it, it will start from the correct position.

We are also adding a "message" action that can be used to send arbitrary strings to your scripts whenever the action is triggered. The intended use case is to be able to trigger custom code also for Push/Double Push in the Selector feature or perform some action when a specific point is reached in Advanced Dimming or Scene Blender.

The virtual devices can be created in the Flic App and be set to be controlled by a Flic Twist as follows:

IMG_9799.png

IMG_9797.png

Using this piece of code, updates are received in your javascript code after configuring a virtual device to be triggered in the Flic App for a specific Flic Twist:

When a device is modified externally, we use this function to inform the system of the change:

The dimmableType can be either "Light", "Speaker" or "Blind". The values is an object containing at least one of the fields mentioned above that is appropriate for the corresponding dimmableType. For example:

The values themselves are always floating point numbers between 0 and 1.

Configure an action message to be triggered by assigning the following action in the Flic app:

IMG_9798.png

The action messages are easy to receive, just register a listener as follows:

We'd love to hear your feedback!