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

@woolfie Sonos's API actually doesn't allow third party apps (like Flic) to start playlists from third party providers like Spotify. The way we do it on Android is a bit hacky.

The solution is to instead use Sonos playlists, which can be controlled by third party apps. A Sonos playlist can be created in the Sonos app and can contain music tracks not only from Spotify, but from for example Soundcloud as well. Once you have created your playlists in the Sonos app, they will be visible in the Flic app under the Playlist option when configuring the Sonos action. You will then be able to use Flic as a trigger to start such a playlist.

@aman Could you please try again now? It should work now.

We simply use the protocol described at https://lan.developer.lifx.com/docs/communicating-with-device over UDP.

We have some LIFX lights at the office and sporadically have noticed they stop responding to UDP packets, but still respond to packets from their cloud (probably TCP). In that case they start working again after "rebooting" the light, i.e. toggling the power.

For more information, please read https://stackoverflow.com/questions/2678551/when-should-space-be-encoded-to-plus-or-20.

In the current firmware version, a + in a query string is translated to %20 before the request is being sent. So, your device will receive the query string 1%20PowerOn, which should be interpreted exactly the same as 1+PowerOn.

In the next firmware version, we will no longer translate + to %20 anymore.

@joerg-pressel plus is usually space. Do you want an actual plus sign or space?

@vc52rac Please try again once more. It should work now.

@vc52rac Hi. What is the serial number of your hub?

@ColCustard we are aware of this and are about to release an update to fix this

@house2uk IFTTT had an issue on their end. After we reached out to them, they have fixed the issue. Could you please test again now to see if it works?

@idoygr It seems you have a super old beta hub. You should try to upgrade the firmware to the latest version. You must do that in two steps, first to version 1.0.0 and then to the latest one. To upgrade, make sure the hub is connected to Ethernet which provides internet connectivity. Then (after powered up, and at least two minutes after booted) press and hold the pin hole button for exactly 3-5 seconds (in that range) and release. It should start to blink then.