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

@ksportz the ttl thing has been fixed and will be rolled out in the next firmware of the hub. The thing that only 36 packets could be sent should also be fixed and included in the next fw.

@ariel We are working on improving the hub sdk and have some bug fixes we are about to roll out. If you have a concrete example of sample code that doesn't work as it should, feel free to post it so that we can have a look.

The HTTP Request action does not go through any cloud. You can for example use local IP addresses in the URL.

I'm not sure if we can do anything regarding Homekit unfortunately since we have some quite strict rules from Apple that we need to follow.

@ariel we use Homekit in-field provisioning which means there is no QR code but instead credentials are transferred from the Flic hub through the Flic app to the Apple Home app.

For now there is no way to retrieve the setup code and thus you can't use any other Homekit controller except for Apple's own.

I suggest you to use alternative methods such as HTTP Request with a web hook in Home Assistant. I haven't tested this but feels like something like that should work. You could also use our hub sdk to implement something low level.

@oli could be something that broke inside. You could file a support case at https://flic.io/support.

@leralfonso the bluetooth version is irrelevant. What is relevant are the connection parameters. The default in our apps/sdks are balanced to get an acceptable delay vs. battery life. You haven't said exactly how you communicate with flic (our app, or sdks, something else) so can't give you more advise right now.

@ryan-0 have you looked at https://flic.io/alexa/setup? The important thing is to add the Alexa action in the Flic app to your button configuration.

@paul-j-houghton maybe it's running low on battery?

@Brooke generally we update the hub and apps at the same time when we have a new feature, so you can check the changelog in the apps.

@alces as you can see on https://superuser.com/questions/1581627/where-is-my-lan-hostname-stored, hostnames on the LAN is not really a "basic feature of networking" since there are like four different "standards" for that. Currently, the only thing you should rely on is that you use a FQDN that the DNS resolver the DHCP server gives the hub will resolve.

@alces with hostname, do you mean the computer name on the local network? In that case, it's not something we support currently so don't expect it to work.