Set manual override

Use this action to set or update a manual override on your OpenEVSE charger. You can specify whether charging should be active or disabled, adjust the target and maximum charge currents, set an energy or time limit for the override session, and choose whether to automatically clear the override when limits are reached or the vehicle disconnects.

This action requires OpenEVSE Wi-Fi firmware version 4.0.1 or later.

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 set a manual override from an automation or 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.
  4. In the Then do section, select Add action.
  5. Select what you want to control. Under By target (see Targets), select the OpenEVSE device or entity you want to manage.
  6. From the actions shown for that target, select Set manual override.
  7. Fill in the optional override settings you wish to apply.
  8. Select Save.

Options in the UI

State (Optional)

The override charging state (active or disabled).

Charge current (Optional)

Target charging current in amperes (6–80 A).

Maximum current (Optional)

Maximum allowed charging current in amperes (6–80 A).

Energy limit (Optional)

Energy limit for the override session in watt-hours.

Time limit (Optional)

Time limit duration for the override session.

Auto release (Optional)

Automatically clear the override when the session completes or limits are reached. If omitted, the existing value on the charger is retained.

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. For how an automation or a script is built in YAML, refer to Automations in YAML and Scripts.

In YAML, refer to this action as openevse.set_override.

ActionAn action makes Home Assistant do something, for example, turn on a light, send a notification, or activate a scene. Automations and scripts run a list of actions. [Learn more]
action: openevse.set_override
target:
  entity_id: switch.openevse_manual_override
data:
  state: active
  charge_current: 32
  auto_release: true

Options in YAML

state string (Optional)

The override charging state (active or disabled).

charge_current integer (Optional)

Target charging current in amperes (6–80 A).

max_current integer (Optional)

Maximum allowed charging current in amperes (6–80 A).

energy_limit integer (Optional)

Energy limit for the override session in watt-hours.

time_limit map (Optional)

Time limit duration for the override session, specified as a mapping, for example {hours: 1, minutes: 30}.

auto_release boolean (Optional)

Automatically clear the override when the session completes or limits are reached.

Default:

Existing value on the charger

Targets of the action

Target an OpenEVSE device or one of its entities, such as switch.openevse_manual_override. The action is applied once per targeted charger, even if multiple selected entities belong to it.

Try it yourself

Ready to test this? Open Settings > 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?

To test the action on its own, run it in the automation editor with Run action, and check the message that it shows. To see what the action did when the automation ran, open the trace of that run. For details, refer to Testing automations. For common problems and their solutions, refer to Troubleshooting automations.

If that doesn’t help, 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.