Posts made by Emil

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

@idoygr what is the serial number of your hub?

@benoit currently this is not possible, but we are considering adding that feature. In the meantime you would unfortunately in this case need to use the raw tcp api for communication.

@benoit so far we only support Ikea Trådfri. You might be able to implement support for Dirigera using the Hub Sdk, but it is not something we have explored.

@martinm When an incoming FIN packet is received from the remote endpoint, the socket is automatically properly closed unless the allowHalfOpen option is set. If that option is set, the socket is properly closed at the time when both an incoming FIN has been received and the local user has called the end method on the socket (in any order). Nothing is done at garbage collection time, so if you use the allowHalfOpen property, remember to close the socket by calling the end method. If the allowHalfOpen is not set, you can still use the end method to send your own FIN packet.

@Smurfhunter not sure if this is your issue but I've heard people saying the Home app is not intuitive. You need to manually go in under the hub icon in the Home app to list the associated buttons. Also make sure you have selected "add to homekit" slider in the flic app.

We are currently in contact with Samsung to see if this can be fixed asap.

Right now the http api is quite simplistic.

As written in the api documentation, both the request body and response body have the data type "String". For now if you don't find a workaround you have to use the raw TCP API.

It's likely this will be supported in a later version.

Sorry for the issue, it was an error at our side on our backend.
Please remove the buttons from the hub and add them back while the hub is connected to the internet.
Then assign the Alexa action in the app to the buttons, while you have internet.
Then they should appear in the Alexa app if you discover devices.

Hi again. Could you please give me the serial numbers of your buttons as well? (written under the battery)

@hal_bryan Hi. Can you please give us your hub serial number so that we can check if everything seems correctly set up in our backend?