Integrations can be set up via the user interface by adding support for a config flow to create a config entry. Components that want to support config entries will need to define a Config Flow Handler. This handler will manage the creation of entries from user input, discovery or other sources (like Home Assistant OS).
Config Flow Handlers control the data that is stored in a config entry. This means that there is no need to validate that the config is correct when Home Assistant starts up. It will also prevent breaking changes, because we will be able to migrate configuration entries to new formats if the version changes.
When instantiating the handler, Home Assistant will make sure to load all dependencies and install the requirements of the component.
You need to update your integrations manifest to inform Home Assistant that your integration has a config flow. This is done by adding
config_flow: true to your manifest (docs).
Config entries uses the data flow entry framework to define their config flows. The config flow needs to be defined in the file
config_flow.py in your integration folder, extend
homeassistant.config_entries.ConfigFlow and pass a
domain key as part of inheriting
Once you have updated your manifest and created the
config_flow.py, you will need to run
python3 -m script.hassfest (one time only) for Home Assistant to activate the config entry for your integration.
Your config flow will need to define steps of your configuration flow. The docs for Data Entry Flow describe the different return values of a step. Here is an example on how to define the
There are a few step names reserved for system use:
|DEPRECATED Invoked if your integration has been discovered by the discovery integration.|
|Invoked if your integration has been discovered via DHCP as specified using |
|Invoked if your integration has been discovered via HomeKit as specified using |
|Invoked if your integration has been discovered via MQTT as specified using |
|Invoked if your integration has been discovered via SSDP/uPnP as specified using |
|Invoked when a user initiates a flow via the user interface.|
|Invoked if your integration has been discovered via Zeroconf/mDNS as specified using |
A config flow can attach a unique ID to a config flow to avoid the same device being set up twice. When a unique ID is set, it will immediately abort if another flow is in progress for this unique ID. You can also quickly abort if there is already an existing config entry for this ID. Config entries will get the unique ID of the flow that creates them.
Call inside a config flow step:
By setting a unique ID, users will have the option to ignore the discovery of your config entry. That way, they won't be bothered about it anymore. If the integration uses DHCP, HomeKit, Zeroconf/mDNS or SSDP/uPnP to be discovered, supplying a unique ID is required.
If a unique ID isn't available, alternatively, the
discovery steps can be omitted, even if they are configured in
the integration manifest. In that case, the
user step will be called when the item is discovered.
Alternatively, if an integration can't get a unique ID all the time (e.g., multiple devices, some have one, some don't), a helper is available that still allows for discovery, as long as there aren't any instances of the integrations configured yet.
Your configuration flow can add support to re-discover the previously ignored entry by implementing the unignore step in the config flow.
When an integration is discovered, their respective discovery step is invoked with the discovery information. The step will have to check the following things:
- Make sure there are no other instances of this config flow in progress of setting up the discovered device. This can happen if there are multiple ways of discovering that a device is on the network.
- Make sure that the device is not already set up.
- Invoking a discovery step should never result in a finished flow and a config entry. Always confirm with the user.
If your integration is discoverable without requiring any authentication, you'll be able to use the Discoverable Flow that is built-in. This flow offers the following features:
- Detect if devices/services can be discovered on the network before finishing the config flow.
- Support all manifest-based discovery protocols.
- Limit to only 1 config entry. It is up to the config entry to discover all available devices.
To get started, run
python3 -m script.scaffold config_flow_discovery and follow the instructions. This will create all the boilerplate necessary to configure your integration using discovery.
Home Assistant has built-in support for integrations that offer account linking using the OAuth2 authorization framework. To be able to leverage this, you will need to structure your Python API library in a way that allows Home Assistant to be responsible for refreshing tokens. See our API library guide on how to do this.
The built-in OAuth2 support works out of the box with locally configured client ID / secret and with the Home Assistant Cloud Account Linking service. This service allows users to link their account with a centrally managed client ID/secret. If you want your integration to be part of this service, reach out to us at [email protected].
To get started, run
python3 -m script.scaffold config_flow_oauth2 and follow the instructions. This will create all the boilerplate necessary to configure your integration using OAuth2.
Translations for the config flow handlers are defined under the
config key in the component translation file
strings.json. Example of the Hue component:
When the translations are merged into Home Assistant, they will be automatically uploaded to Lokalise where the translation team will help to translate them in other languages. While developing locally, you will need to run
python3 -m script.translations develop to see changes made to
strings.json More info on translating Home Assistant.
As mentioned above - each Config Entry has a version assigned to it. This is to be able to migrate Config Entry data to new formats when Config Entry schema changes.
Migration can be handled programatically by implementing function
async_migrate_entry in your component's
__init__.py file. The function should return
True if migration is successfull.
Gracefully handling authentication errors such as invalid, expired, or revoked tokens is needed to advance on the Integration Qualily Scale. This example of how to add reauth to the OAuth flow created by
script.scaffold following the pattern in Building a Python library.
This example catches an authentication exception in config entry setup in
__init__.py and instructs the user to visit the integrations page in order to reconfigure the integration.
The flow handler in
config_flow.py also needs to have some additional steps to support reauth which include showing a confirmation, starting the reauth flow, updating the existing config entry, and reloading to invoke setup again.
Depending on the details of the integration, there may be additional considerations such as ensuring the same account is used across reauth, or handling multiple config entries.
The reauth confirmation dialog needs additional definitions in
strings.json for the reauth confirmation and success diaglogs:
See Translations local development instructions.
Authentication failures (such as a revoked oauth token) can be a little tricky to manually test. One suggestion is to make a copy of
config/.storage/core.config_entries and manually change the values of
expires_at depending on the scenario you want to test. You can then walk advance through the reauth flow and confirm that the values get replaced with new valid tokens.
Automated tests should verify that the reauth flow updates the existing config entry and does not create additional entries.