@stevehooper yeah we should really try to add a direct Home Assistant integration from the Flic hub someday, since it is so popular...

In the meantime, can you use the Internet Request action in our app to send a simple http request to your device running Home Assistant maybe?

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:

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:

const flicapp = require("flicapp");

flicapp.on("virtualDeviceUpdate", (metaData, values) => {
    // The values object can contain hue, saturation, brightness, colorTemperature, volume, position (for blinds)
    console.log(`Twist ${metaData.buttonId} updated virtual device ${metaData.virtualDeviceId} of type ${metaData.dimmableType} with these values: ${JSON.stringify(values)}`);
});

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

flicapp.virtualDeviceUpdateState(dimmableType, virtualDeviceId, values);

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:

flicapp.virtualDeviceUpdateState("Light", "my_ceiling_light", {hue: 0.6, saturation: 0.7, brightness: 0.8});

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:

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

flicapp.on("actionMessage", message => console.log(`Got a message: ${message}`));

We'd love to hear your feedback!

We are slowly rolling this out in different regions. Stay tuned.

@bulk Yes we have made the submission.

@abboberg All our firmwarers are auto-updated. In some cases we have assigned a specific firmware to specific people on request. Please reach out to us if you want to go back to the public release track.

The current hub fw version is 4.2.11.

Usually when we update the hub firmware we also update the apps. In the apps you can see a Change log in the settings menu.

@steveff Our Matter integration is just around the corner. For the Twist this is probably most relevant for lights, as no speakers I know yet support Matter.

What we also have in the pipeline for Twist is e.g. more configurable steps (4 -> 12) for Advanced Dimming/Scene Blender so that you can trigger an action (e.g. Alexa) with higher resolution and before as well as Hub SDK features for the Twist so that you can build custom integrations.

Spotify has an API (over cloud) that we could potentially use for controlling the volume, but we are not sure if the latency will be low enough to make this action have a good user experience. We also don't like that they don't provide any means to "push out" the volume status when it is changed so that the LEDs on the Twist could update accordingly (https://community.spotify.com/t5/Spotify-for-Developers/Access-to-websockets/td-p/4955299).

@hello_marley the ball is moving according to plan. Please stay tuned

@giannis-yt I would guess at the moment the Raspberry Pi Zero Wireless is one of the cheapest options.

@mx5_94 Seems like a very powerful option. We'll definitely implement that!

What you should do is to first call bind, followed by setBroadcast(true) on the socket. Then you can send messages using send.
FYI, the API is made to be compatible with Node.js API https://nodejs.org/api/dgram.html.

@werner-kneile Did you press "Save & Disconnect"? This will disconnect your button as a Flic button. The Flic will instead advertise itself as a normal Bluetooth keyboard and you need to add it using the system's Bluetooth settings.

@hmmwhatsthisdo Could you elaborate what you did when you unregistered the hub from device manager? There should be a red trash can icon which will delete the hub. Make sure you are not just removing it from a group or similar but remove it completely.

@hmmwhatsthisdo Sorry, I was maybe too fast typing my reply or not clear enough. The hubs on the Device Manager path have slightly different firmware builds compared to firmwares for non-device manager. Therefore, the "latest stable" on Device Manager does not necessarily correspond to the same latest stable version for the normal consumer firmware as we require different testing for Device Manager hubs vs consumer hubs. The Device Manager firmwares might also lag a bit in regards to functionality compared to the consumer version.

That said, I now see that the Twist features have yet not reached the firmware used for Device Manager hubs. I will escalate this issue and try to get it resolved ASAP. In the meantime I suggest that you deactivate Device Manager for this hub if you want to try out the feature.

@hmmwhatsthisdo I see. That hub is registered with the Device Manager. With the Device Manager activated, you select yourself which firmware version you want it to have in the Device Manager portal. Try to select the latest version instead and then trigger a firmware update.

@hmmwhatsthisdo-flic Can you please try to update the firmware to the latest version (should be 4.4.2)?

@johan-0 The IR functionality in the Flic Hub is pretty simple. It just records an IR signal and then replays it. If the IR remote typically sends a dynamic signal (or something that is not static), the receiver might not accept a replayed signal. If you use the Hub SDK, you can both inspect recorded signals but also create your own signals by defining the "raw" data.

@gordon-0 If you use the Android app, then you can create a custom config using the "Configs" provider in the app. Then you can create a Task having the "Change Config" action which loads the settings of a specific Flic button with a precreated config. You can repeat this for every config you want. Then, execute the task when you want to change the config. If you hold on your phone's home screen, you can create a Flic widget, which will allow you to easily execute tasks.

@Astro We don't have a voting system unfortunately.

@Astro We have in the backlog to add the feature to play a Sonos Favourite. That way you can set a radio station as a favourite and then start that using Flic.

@stevehurcombe Hi. We will take a look at this when we are back from summer holidays.