Send command
The Send command action sends a custom command to your Lutron Homeworks controller. You can send a single command or a list of commands.
This action does not target an entity. Instead, you provide the controller to send to and the command to send.
In addition to the commands supported by the controller, the special command DELAY <ms> is supported, where <ms> is the number of milliseconds to wait before continuing.
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 send a command 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.
- From the search box, search for and select Lutron Homeworks: Send command.
- Enter the Controller ID and the Command to send.
- Select Save.
Options in the UI
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 homeworks.send_command. A basic example looks like this:
action: homeworks.send_command
data:
controller_id: "homeworks"
command: "KBP, [02:08:02:01], 1"
This sends a single command to the controller.
Options in YAML
Good to know
To send several commands in sequence, pass a list. The following example sends KBP, waits 0.5 seconds, then sends KBR to simulate a keypad button press that lasts half a second:
action: homeworks.send_command
data:
controller_id: "homeworks"
command:
- "KBP, [02:08:02:01], 1"
- "DELAY 500"
- "KBR, [02:08:02:01], 1"
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.
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.
Automation: Simulate a keypad press at sunset
This automation simulates a keypad button press on your Homeworks controller every day at sunset, which you can use to recall a scene programmed on the keypad.
- Trigger: the sun sets
-
Action: Lutron Homeworks: Send command (press and release the keypad button with a short delay in between)
-
Controller:
homeworks
-
Controller:
YAML example for recalling evening scene at sunset
alias: "Recall evening scene at sunset"
triggers:
- trigger: sun
event: sunset
actions:
- action: homeworks.send_command
data:
controller_id: "homeworks"
command:
- "KBP, [02:08:02:01], 1"
- "DELAY 500"
- "KBR, [02:08:02:01], 1"
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.