Delete remote command

The Delete remote command action deletes one command or a list of commands from a supported remote 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]. Use it when you want to remove learned commands that are no longer needed or that should be learned again.

Deleting support depends on the remote integration and the selected remote entity.

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 delete a remote command 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. 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), pick the remote entity, device, area, floor, or label that should delete the command.
6. From the actions shown for that target, select Delete remote command.
7. In Command, enter the command to delete.
8. Optional: In Device, enter the device ID that contains the command.
9. 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 remote.delete_command. A basic example looks like this:

action: remote.delete_command
target:
  entity_id: remote.living_room
data:
  device: television
  command: mute

This deletes the mute command for television from remote.living_room.

Options in YAML

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 remote entity behind that target.

• Entity: one specific remote entity, such as remote.living_room.
• Device: every remote entity that belongs to a device.
• Area: every remote entity in a room or area.
• Floor: every remote entity on a floor.
• Label: every remote 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

• The action targets remote entities that support deleting commands.
• Deleting a command removes it from the remote integration’s command database. Learn the command again before sending it later.
• The exact device IDs and command names depend on the remote integration.
• To add a command again, use Learn remote command.

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.

Automation: delete a learned command from a helper button

When a user-created helperA helper is a virtual entity you create inside Home Assistant. It is not backed by a physical device. Helpers store values, track state, or do calculations that your automations and dashboards need. [Learn more] button, created separately, is pressed, delete a learned mute command.

• Trigger: State
  • Entity: Delete mute (input_button.delete_mute)
• Action: Delete remote command
  • Target: Living room remote
  • Device: television
  • Command: mute

alias: "Delete TV mute command"
triggers:
  - trigger: state
    entity_id: input_button.delete_mute
actions:
  - action: remote.delete_command
    target:
      entity_id: remote.living_room
    data:
      device: television
      command: mute

Automation: delete several commands from a helper button

When a user-created helperA helper is a virtual entity you create inside Home Assistant. It is not backed by a physical device. Helpers store values, track state, or do calculations that your automations and dashboards need. [Learn more] button, created separately, is pressed, delete several TV commands that you want to learn again.

• Trigger: State
  • Entity: Delete TV commands (input_button.delete_tv_commands)
• Action: Delete remote command
  • Target: Living room remote
  • Device: television
  • Command: power, input_hdmi_1

alias: "Delete TV commands"
triggers:
  - trigger: state
    entity_id: input_button.delete_tv_commands
actions:
  - action: remote.delete_command
    target:
      entity_id: remote.living_room
    data:
      device: television
      command:
        - power
        - input_hdmi_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.

Related actions

These actions work well alongside this one:

• Learn remote command: Teaches a supported remote entity one or more commands.

• Send remote command: Sends one or more commands through a remote entity.