Best posts made by Emil

@bulk Yes we have made the submission.

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

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

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

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.

Have you followed the tutorial? Did you register the correct flags according to this?

Hi. You need to manually construct the Authorization header. See https://en.m.wikipedia.org/wiki/Basic_access_authentication.

Our runtime is not 100% compatible with node.js and you can't directly install npm modules. However you could try copy-paste the source code into our IDE and maybe it will work.

@aconrad2 Hi. You can use Flic Single just like any other Flic with the Linux SDK.

Hi. Please see https://community.flic.io/topic/17817/internet-request-with-user-name-and-password.

Hi. Not right now, since we now use Duktape (https://duktape.org) as the javascript engine, which does not support promises and async. Maybe we will change to JerryScript or something in the future if there is a demand for this. We could potentially add some polyfill for promises but in that case I think it's better to get something that supports async.

Hi!

Yes you need to add the Flic 2 SDK. Please prompt the user which Flic version they have so you can call the right API.

There are currently no plans for making a unified API.

Hi. This forum is meant to be a community forum rather than a support forum. For support you should send an email to support@shortcutlabs.com. For your Samsung phone, you could try reboot it in case Bluetooth has hung or similar.

@b-bech-l now

@simonwjorgensen We are actually finalizing the final pieces right now, so very soon

@tony Android's Bluetooth team messed up the update to Android 9. The cached GATT db structure is erased for bonded devices after the update, so the API gives an empty list of GATT services, making it impossible to communicate with the GATT characteristics. The only way to make it work again seems to be to unbond the Bluetooth device from the system and then bond again.

Hi. The intention with the Homekit integration is to be able to trigger Homekit actions using a Flic button. If there is a lot demand for this we might consider this in the future.

Hi. The only way to play custom commands right now is to use the Hub SDK. Use the method at https://hubsdk.flic.io/static/documentation/#37_play to play a raw signal.

In our iOS app HID keyboard is used for some actions such as trigger camera, page turner etc.

A more "raw" keyboard feature is in development and will come later.

If there is no pop-up in the flic app when you slide "add to homekit" to on, it means the homekit pairing protocol has been successful, from the flic hub's point of view. If Apple's homekit view in the phone hangs and it, from its point of view therefore fails to pair, the flic hub will then not be registered as paired. Now, according to the Homekit specification, the only allowed way for an accessory to accept a new pairing when already paired, is by factory resetting the accessory. To do that on the flic hub, simply hold the pin hole for exactly a time between 10-15 seconds. If successful, the LED will blink shortly and the device will reboot. You'll have to reconfigure it, but once complete, you can try again to add to homekit.