2026.6.4
Home ▸ Actions

Move effect

Use this action to run the firmware-based Move effect, which moves the current colors on the device in a direction you choose. This is a hardware effect for LIFX multizone lights such as the LIFX Z, Lightstrip, Beam, Neon, and String.

The effect is not visible if every LED on the device is set to the same color, and it is ignored by unsupported devices. While the effect runs, you can change its colors using the lifx.set_state action.

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 move effect from an automation or a script:

  1. Go to Settings > Automations & scenes.
  2. Open an existing automation or script, or select Create automation > Create new automation.
  3. 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.
  4. In the Then do section, select Add action.
  5. Select what you want to control. Under By target (see Targets), select the LIFX multizone lights you want to animate.
  6. From the actions shown for that target, select Move effect.
  7. Fill in the options you want to use.
  8. Select Save.

Options in the UI

Speed

How many seconds the effect takes to move across the length of the light (0.1 to 60).
Direction

The direction the effect moves across the device. One of: right or left.
Theme

A predefined color theme to set on the device before starting the effect.
Power on

Turn this off to keep a light that is off from being turned on before the effect starts.

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_move. A basic example looks like this:

ActionActions are used in several places in Home Assistant. As part of a script or automation, actions define what is going to happen once a trigger is activated. In scripts, an action is called *sequence*. [Learn more] 
action: lifx.effect_move
target:
  entity_id: light.lifx_beam
data:
  speed: 3
  direction: left

This moves the current colors on the LIFX Beam to the left.

Options in YAML

speed float

How many seconds the effect takes to move across the length of the light (0.1 to 60).

direction string

The direction the effect moves across the device. One of: right or left.

theme string

A predefined color theme to set on the device before starting the effect.

power_on boolean

Set to false to keep a light that is off from being turned on before the effect starts.

Available themes

The available themes are:

  • autumn
  • bias_lighting
  • blissful
  • calaveras
  • cheerful
  • christmas
  • dream
  • energizing
  • epic
  • evening
  • exciting
  • fantasy
  • focusing
  • gentle
  • halloween
  • hanukkah
  • holly
  • hygge
  • independence
  • intense
  • kwanzaa
  • love
  • mellow
  • party
  • peaceful
  • powerful
  • proud
  • pumpkin
  • relaxing
  • romance
  • santa
  • serene
  • shamrock
  • soothing
  • spacey
  • sports
  • spring
  • stardust
  • thanksgiving
  • tranquil
  • warming
  • zombie

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.

Tip

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:

  • Paint theme: Paint a predefined theme or a custom color palette across LIFX lights.

  • Stop effect: Stop any running software or hardware effect on LIFX lights.