Flame effect
Use this action to run the firmware-based Flame effect, which animates a flame across the device. This is a hardware effect, so it only works on LIFX matrix lights such as the Tile, Candle, Path, Spot, and Ceiling.
By default, the light is turned on when the effect starts. Turn off the power on option to leave a light that is off untouched.
Using this action from the user interface
If you prefer building automations and scripts visually, Home Assistant walks you through this action step by step. You pick what to target, tweak a few options, and save. No YAML knowledge required.
To run the flame effect from an automation or a script:
- Go to Settings > Automations & scenes.
- Open an existing automation or script, or select Create automation > Create new automation.
- If you’re setting up a new automation, add a trigger in the When section. Scripts don’t need a trigger. They run when something else calls them.
- In the Then do section, select Add action.
- Select what you want to control. Under By target (see Targets), select the LIFX matrix lights you want to animate.
- From the actions shown for that target, select Flame effect.
- Fill in the options you want to use.
- Select Save.
Options in the UI
How fast the flames move, as the number of seconds for the effect to travel the length of the device (1 to 25).
Using this action in YAML
If you work directly in YAML, or you want to know exactly what Home Assistant does under the hood, this section has the technical reference. It lists the field names you use in YAML, their types, and which ones are required.
In YAML, refer to this action as lifx.effect_flame. A basic example looks like this:
action: lifx.effect_flame
target:
entity_id: light.lifx_tile
data:
speed: 4
This starts the Flame effect on the LIFX Tile.
Options in YAML
Targets of the action
This action requires a target. The target is the object of the action. You can point the action at a single entityAn entity represents a sensor, actor, or function in Home Assistant. Entities are used to monitor physical properties or to control other entities. An entity is usually part of a device or a service. [Learn more], a device, an area, a floor, or a label, and Home Assistant will run the action on every matching light entity behind that target.
-
Entity: one specific light entity, such as
light.living_room. - Device: every light entity that belongs to a device.
- Area: every light entity in a room or area.
- Floor: every light entity on a floor.
- Label: every light entity that shares a label.
You can also select different target types in one action. For example, you can add a specific entity and an area as targets in the same action to run the action on both of them at once.
Try it yourself
Ready to test this? Open Developer tools > Actions, search for this action, fill in the fields, and select Perform action. You see what happens on your actual entitiesAn entity represents a sensor, actor, or function in Home Assistant. Entities are used to monitor physical properties or to control other entities. An entity is usually part of a device or a service. [Learn more] without writing a line of YAML.
Still stuck?
The Home Assistant community is quick to help: join Discord for real-time chat, post on the community forum with the action you’re calling and what you expected to happen, or share on our subreddit /r/homeassistant.
AI assistants like ChatGPT or Claude can also explain actions or suggest the right one when you describe what you want in plain language.
Related actions
These actions work well alongside this one:
-
Morph effect: Run the firmware-based Morph effect on LIFX matrix lights.
-
Stop effect: Stop any running software or hardware effect on LIFX lights.