Scripts in Home Assistant
script
part of Home Assistant since 0.7
The Scripts integration allows users to create and manage reusable sequences of actions within Home Assistant. It connects with various components to automate tasks like controlling devices, triggering automations, and managing scenes.
Typical uses
- Controlling smart home devices
- Triggering automations
- Managing scenes
- Executing complex tasks
Facts about this integration
- Compatible with Home Assistant
- yes, official integration
- Setup
- in configuration.yaml
- Kind
- Part of Home Assistant itself
- Quality scale
- Internal – Part of Home Assistant itself, not rated separately.
- Installations
- 536,607 (78.5 % of the installations that share statistics)
- Categories
- Automation
- Maintained by
- @home-assistant/core
Setup
- Nothing to install: this is part of Home Assistant and available as soon as it is running.
Blueprints that use this integration
- Automation Sensor Light
- Automation NSPanel Configuration
- Automation Bathroom Humidity Exhaust Fan
- Automation Smart Light
- Automation Ikea_bilresa_scroll_wheel
- Automation Sensor Light Add On
Known issues and fixes
3 open issues and 4 bug fixes in the last twelve months are recorded for Scripts in the Home Assistant issue tracker. If something does not work, update first: the most recent fix shipped with Home Assistant 2026.5.0.
Open
- open Renaming a script's entity ID does not work as expected.
- open Using the 'stop' action with 'error' set to true does not halt the parent script's execution.
- open A blocking call in a script's field schema causes unexpected behavior.
Fixed
- fixed in 2026.5.0 A race condition during script unloading caused inconsistent behavior.
Source: the issue tracker of Home Assistant, as of September 13, 2026. The sentences are written by a language model from the titles of the issues; the reports themselves are on GitHub.
Check a specific device for known problems in the product check →
Source of this entry: the official documentation of the integration
The description was written by a language model from the facts listed here, not taken from the documentation.
