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.

@Emil thanks for getting this to work. Much appreciated ?? Is this a running problem for anyone purchasing a new kit? Not ideal for those who are not familiar with forums. But its all working as intended now. Thanks

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.

@jf Hi!
Could you describe at which step it failed? Did the RPi discover the Flic at all?

I don't have a RPi at hand but just tried with Kubuntu and did not see any issues.

Also to make sure, did you add it by going to System Settings -> Hardware -> Bluetooth -> Add new device?