Pulse effect

Use this action to run a software-based flash effect on LIFX lights. The light changes to a color and then back to its original color, which is useful for getting your attention, like a notification flash.

You can start this effect with default options using the effect option of the regular light.turn_on action. To fully control the effect, use this dedicated action instead.

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 pulse 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 lights you want to flash.
  6. From the actions shown for that target, select Pulse effect.
  7. Fill in the options you want to use.
  8. Select Save.

Options in the UI

Mode

How colors change during the effect. One of: blink (direct switch to the new color), breathe (fade to the new color and back), ping (a short pulse of the new color), strobe (the light turns off between color changes), or solid (the light does not return to its original color between cycles).

Brightness value

A number from 1 to 255 for how bright the temporary color should be.

Brightness

An alternative to the brightness value, as a percentage from 1 to 100.

Color name

A human-readable color name, such as red or green.

RGB color

The temporary color in RGB format, as a list of three integers.

Period

The duration of a single pulse, in seconds.

Cycles

The total number of pulses to run.

Power on

Turn this off to skip the effect on lights that are turned off.

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_pulse. 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_pulse
target:
  entity_id: light.office
data:
  color_name: red
  mode: breathe
  cycles: 3

This makes the office light breathe red three times before returning to its original color.

Options in YAML

mode string

How colors change during the effect. One of: blink (direct switch to the new color), breathe (fade to the new color and back), ping (a short pulse of the new color), strobe (the light turns off between color changes), or solid (the light does not return to its original color between cycles).

brightness integer

A number from 1 to 255 for how bright the temporary color should be.

brightness_pct integer

An alternative to brightness, as a percentage from 1 to 100.

color_name string

A human-readable color name, such as red or green.

rgb_color list

The temporary color in RGB format, as a list of three integers.

period float

The duration of a single pulse, in seconds.

cycles integer

The total number of pulses to run.

power_on boolean

Set to false to skip the effect on lights that are turned off.

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:

  • Color loop effect: Run a software-based effect on LIFX lights that loops colors around the color wheel.

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