FlicTeam

Hi,

We have just released a firmware update which should fix this (version 4.4.4).

While connected to a Flic Hub, go to settings and press "check for new firmware" in order to upgrade.

@knewe Thanks, I got your video.

After you have pressed Save & disconnect, and the configuration has been saved successfully, the button is now ready to be used as a keyboard on any Bluetooth compatible device such as a PC, tablet or phone. To use it as such a device, you must manually go into your system's Bluetooth settings and add it as such a device, even if you want to use the Flic button on the same device (i.e. the one that has the Flic app).

Note that after you have pressed Save & disconnect and have been taken back to the home screen of the app, you must NOT press the icon representing the button again, since that will reconnect the Flic button to the Flic app and hence change the mode of the Flic button from a keyboard to a normal Flic button. You should only do this when you for some reason want to reconfigure the Flic button again.

@knewe I don't really understand why it's not working for you. Maybe you can shoot a video or something from the point where you press save & disconnect and then try to pair the device "FLIC" that should appear in the system's bluetooth settings when you search for devices. (Note that you need to make a short press on the Flic button to make it advertising)

@knewe You need to follow this step where you click "Save & Disconnect". Otherwise it won't work:

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