Command

Use this action to send a generic command to your LG webOS TV. This is handy when you want to control something that doesn’t have its own action, for example to open an app or call a specific endpoint on the TV.

You provide the endpoint of the command and, when needed, a payload with extra details. The full list of known endpoints is available in the aiowebostv endpoints reference.

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:

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 TV you want to control.
6. From the actions shown for that target, select Command.
7. Set the Command and, if needed, a Payload.
8. 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 webostv.command. A basic example that opens a web page looks like this:

action: webostv.command
target:
  entity_id: media_player.lg_webos_tv
data:
  command: "system.launcher/open"
  payload:
    target: "https://www.google.com"

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

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

Response data

This action can return the raw response from the TV. The contents depend on the command you send, so the fields vary from one endpoint to another. To capture the response, set a response_variable and use it in a later step.

Good to know

• The available endpoints and their payloads are defined by the TV, not by Home Assistant. See the aiowebostv endpoints reference for known endpoints.
• To simulate a remote button press instead of sending an endpoint, use the Button 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.

Related actions

These actions work well alongside this one:

• Button: Simulates a button press on the remote of an LG webOS TV.

• Select sound output: Changes the active sound output of an LG webOS TV.