in YOUR_SELECTOR you should write the selector of the light/lights you want to run the effect on. Selector is the equivalent to entity_id in HA. Example:
In YOUR_LIFX_TOKEN you must put your lifx token :).
In order to call the effect in automations/scripts:
- service: rest_command.flame
In the payload section you can toy around with the parameters: period, duration, power_on and fast. All the information can be found in the LIFX HTTP API documentation:
Because it supports the API’s waveform feature, it can do any effect you want. The challenge is to configure a waveform so that it performs an existing effect like flame. The API documentation doesn’t offer any examples on how to do that.
As for flame and morph, apparently those are firmware effects baked into certain types of LIFX products.
LIFX’s LAN protocol defines how data should be packaged within a UDP packet. The easiest way to experiment with it is to use the Node-Red node I described above. If you’re unfamiliar with Node-Red, this is a perfect opportunity to learn it.
EDIT
The other option is to use Linux’s netcat command to send UDP packets. The challenge will be to learn how to piece together the LIFX commands that must sent to the LIFX bulb.