Sequence effect

The Sequence effect action plays a repeating sequence of colors on a TP-Link light strip. Unlike the random effect, you define the exact colors and the order they appear in, and the light steps through them in sequence.

This effect is available on devices that support light effects, such as bulbs and light strips, except for Kasa bulbs. Colors are expressed as HSV sequences, where each value is hue, saturation, and brightness.

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

  1. Go to Settings > Automations & scenes.
  2. Open an existing automation or script, or select Create to start a new one.
  3. If you’re setting up a new automation, add a trigger in the When section. Scripts don’t need a trigger.
  4. In the Then do section, select Add action.
  5. Select what you want to control. Under By target (see Targets), select the light strip you want to control.
  6. From the actions shown for that target, select Sequence effect.
  7. Set the options you want to use.
  8. Select Save.

Options in the UI

Sequence (Required)

The list of HSV sequences to step through, in order. Up to 16 entries.

Segments (Optional)

The list of segments to apply the effect to. Use 0 for all segments.

Brightness (Optional)

The initial brightness, from 1 to 100%.

Duration (Optional)

How long the effect runs, in milliseconds. Use 0 to run continuously.

Repetitions (Optional)

How many times to repeat the sequence. Use 0 for continuous.

Transition (Optional)

The transition time between colors, in milliseconds.

Spread (Optional)

The speed at which the effect spreads across the segments.

Direction (Optional)

The direction the effect moves in, from 1 to 4.

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 tplink.sequence_effect. 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: tplink.sequence_effect
target:
  entity_id: light.strip
data:
  sequence:
    - [340, 20, 50]
    - [20, 50, 50]
    - [0, 100, 50]
  segments: [0, 2, 4, 6, 8]
  brightness: 80
  transition: 2000
  spread: 1
  direction: 1

This plays the defined color sequence on light.strip.

Options in YAML

sequence list Required

The list of HSV sequences to step through, in order. Up to 16 entries.

segments list

The list of segments to apply the effect to. Use 0 for all segments.

brightness integer

The initial brightness, from 1 to 100%.

duration integer

How long the effect runs, in milliseconds, from 0 to 5000. Use 0 to run continuously.

repeat_times integer

How many times to repeat the sequence, from 0 to 10. Use 0 for continuous.

transition integer

The transition time between colors, in milliseconds, from 0 to 6000.

spread integer

The speed at which the effect spreads across the segments, from 0 to 16.

direction integer

The direction the effect moves in, from 1 to 4.

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.

Good to know

  • Light effects are only available on supported devices, such as bulbs and light strips. Kasa bulbs do not support them.
  • Colors use HSV sequences, where each value is hue, saturation, and brightness.

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.

More examples

Real scenarios where this action shows up in automations and scripts. Copy any example and adapt it to your setup.

Tip

You don’t need to edit YAML to use these examples. Copy a YAML snippet from this page, open the automation editor in Home Assistant, and press Ctrl+V (or Cmd+V on Mac). Home Assistant automatically converts the pasted YAML into the visual editor format, whether it’s a full automation, a single trigger, a condition, or an action.

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:

  • Random effect: Sets a random light effect on a TP-Link light strip.