2026.6.3
Home ▸ Actions

Request area preset

Use this action to send a command on the Dynalite network asking an area to report its currently selected preset. Normally, channel 1 is used, but some installations need a different channel for specific areas.

Note

This action does not return the preset. It sends a network command asking the area to report its preset. When the area reports back, the system catches and handles that report.

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 request an area preset 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. From the search box, search for and select Philips Dynalite: Request area preset.
  6. Enter the Area, and optionally the Host and Channel.
  7. Select Save.

This action does not support targets. In the UI, you enter the Dynalite area number (and optionally a channel) instead of selecting an entity.

Options in the UI

Host (Optional)

The IP address of the gateway to send the command to. When left empty, the command is sent to all configured gateways.
Area (Required)

The Dynalite area to request the preset for.
Channel (Optional)

The channel to request the preset from. When left empty, channel 1 is used.

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 dynalite.request_area_preset. 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: dynalite.request_area_preset
data:
  area: 2

Options in YAML

host string

The IP address of the gateway to send the command to. When left empty, the command is sent to all configured gateways.

area integer Required

The Dynalite area to request the preset for.

channel integer

The channel to request the preset from. When left empty, channel 1 is used.

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: